- Project Management
- Google Drive
- Standard Meetings
- Course Readiness / Pre-Flight Semester Checks / First Day of Classes Checks
- UAF eCampus/iTeach/iTeachU logos and Graphics
- Google Calendar
- Off-Site (OS) Time
- Black-out Dates for Annual Leave
- Professional Development/Conference Requests
- Equipment/software check-outs/loans, email and software license access (requires a secure log in with UA id)
- File Naming Conventions
- Teaching Tips
- Annual Reviews and Step Increase Requests
Design Team Processes
There are various processes that occur within the Design team, leave requests, outside eCampus projects, annual reviews, etc.
As of 2017, we moved projects and processes to Airtable. Contact Madara to get access.
Most of our meeting notes and shared documents are created and stored in Google Drive in either a shard drive or regular drive. Weekly meeting notes, iTeach planning documents, preflight, teaching tips, and other documents that involve sharing with another user should be stored and shared through google drive.
- Weekly meetings for catching up on stuff, except for the week we have a staff meeting
- Course dev meeting (the same week as Staff meeting)
- Brown Bags sessions to hear about conference proceedings or cool stuff
- Tool Palooza Work Jam Session
- Three times a year OKR (Objectives and Key Results) meetings
- Monthly or Semi-monthly check-in with Associate Director of Teaching and Learning
Course Readiness / Pre-Flight Semester Checks / First Day of Classes Checks
Each semester, all online classes are checked for updates. You’ll be given around 20 to 30 courses to review. If you find things missing or that need updating, the instructor should be contacted to fix. If it is something simple like a typo or a broken link, and you have access, please fix. We usE AirTable to manage course assignments. Airtable is a spreadsheet-database hybrid, with the features of a database but applied to a spreadsheet.
Contact Brant email@example.com to get access.
ORION – all of the UAF eCampus’s information/projects — create your own directory for file ex-change/backup in DESIGN directory. This is one option. You’re also welcome to back up to Google Drive.
Commdev – community dev site – you have to be on UA network to access. If you think you need access, get with Brant
Community.uaf.edu – Community installation of WordPress that houses most of our projects, training materials, IDT, course, student and faculty blogs, and open courses. Contact any Instructional Designer to get access and create your own blog.
iteachu.uaf.edu – online faculty development/training site – update this site every iTeach. Teaching tips also go on iTeachU.
UAF eCampus/iTeach/iTeachU logos and Graphics
Located in eCampus Marking shared drive
Google Calendar is part of UA Google Apps and is serving a function of group scheduling for Design Team and UAF eCampus. Please share your calendar at the “See All Event Details” with all member of the Design Team, the UAF eCampus Admin group (Owen Guthrie Donna Oyen ), and anyone else who you regularly meet with. You can access these settings under Calendar > Calendar Settings > Calendars > Edit Settings > Share with Specific People for the calendar you are sharing. Use the “Private” option on appointments/events that you want to keep the title/details of the event private, though this should not apply to most UAF eCampus related activities.
Ask Madara to give you access to UAF eCampus Faculty Development so you can add events related to faculty development.
Ask Donna to give you access to UAF eCampus Leave (view)
Please keep your calendar up to date including appointments, lunch, or anytime you are away from the office. If you get invited to a meeting be sure to accept or deny the invitation so the inviter knows who to expect and we don’t run around the office looking for you.
Block out appropriate time on your calendar. The first place we should all look–if someone’s not at their desk and we need them–is their calendar (which, it should be needless to say, should always be up to date). Remember we have simple labels for times you will be gone:
- OS or off-site when you are away, but working, make sure you change the setting from busy to available and that you are available by chat or are regularly checking your email. See off-site information below.
- LEAVE for annual/sick leave when you are on annual leave or when you are taking sick leave
- UT or unicorn time
- If you are away from the office but in a work-related meeting, that is not OS, the details in the calendar event should list you as meeting on campus (or other location)
- DELAYED if you are just marking that you are late coming or returning to the office
If you are getting your hair cut, nails done, shopping for new underwear…we’re glad that you’re taking care of business, but we really don’t need to know the details. “Leave” or “Out of Office” or “Errand” is good enough.
If you are gone for all-day events of whatever kind, please BLOCK OUT THE ENTIRE DAY with an actual block, in addition to using the all-day event banner option. The problem with the all-day event is that it isn’t obvious when scheduling meetings that the person isn’t actually there because the calendar doesn’t include events from at the banner.
Off-Site (OS) Time
Black-out Dates for Annual Leave
Please plan to available during these peak times. If you need to take leave, it is probable that we’ll grant it during these times, but it isn’t guaranteed.
- two weeks before and one week after a semester begins (Jan, May, July, August)
Professional Development/Conference Requests
Professional development and conference attendance is very important for keeping actively engaged and inspired in our positions on the Instructional Design Team. Consider a yearly opportunity that pertains to enriching your skills. The DT has a google calendar called “ID Related Conferences/Events” that any of the DT can add new IDers. Follow the directions for Travel.
Opportunities, where you’re accepted to present, are given more priority and may not be limited to once a year. Upon returning to the office, plan some kind of presentation about your experience to be delivered to the IDT/eCampus Staff.
Equipment/software check-outs/loans, email and software license access (requires a secure log in with UA id)
- Design Team Accounts – team accounts for a variety of applications, software and services.
- Tech Loan Library (airtable) – connect faculty with Karina or Brant for help with this
- eCampus email accounts – various email accounts used for team activities
File Naming Conventions
iTeach+ include workshops, hands-on events, discussions or anything that falls outside of an iTeach. A semester schedule is created in advance, but additional iTeach+ may be added as demand or necessity warrants.
Three times a year , you’ll get together with Madara and Heidi and develop and discuss your OKR plan. How Google Sets goals: OKRs and This is the internal grading system Google uses for its employees.
Annual Reviews and Step Increase Requests
Instructional Designers will receive an annual review on their anniversary date, based on University of Alaska HR regulations. Supervisors and designers will get a chance to current job duties as well as performance. *Merit bonuses, paid time off, and other merit-based awards may be awarded at the discretion of Heidi and Madara. Instructional Designers may request their own step-increases based on the following criteria. (note: UAF HR requirements only allow for one increase per year.)
Extraordinary Performance consists of activities that show initiative beyond that which has been assigned by immediate supervisors, which have a dramatic impact on the way eCampus is seen by other units and upper administration and/or the public, and which contribute to and include other members of the Design Team.
Innovations include creativity and experimentation into current emerging technologies and their application to education, sharing emerging tech with faculty and providing best practices to the UAF as a whole.
Skills Mastery resulting in performance improvements, innovation, and/or benefits to faculty courses/faculty development activities.
Volunteering for activities organization-wide, contributing to the effectiveness of eCampus as a unit.
Team Morale: includes high levels of teamwork; positive, strategic approaches to activities that include other members of the Design Team; and overall positive contributions to the eCampus workplace.
Exceptional Faculty/University Relationships: foster and create interactions with university entities to gain positive relationships and provide exceptional customer service.