Dos:
• Run v9 on a test server
• Focus staff on specific tasks – don’t let them play freely, because they wont
• Give them Bb assignments to complete on the new features
• Use lists of things that have been complained about in the past and show how they have been fixed – a good way of making them aware of the new features
• Dont run large training events – people don’t come. Short tutorial training sessions via Jing (5 minute long videos). Focus on short, specific things. One-to-one.
• Use school administrators to spread the word; get the upgrade announced at as many meetings as possible
• Get feedback from staff the beginning – generate tip sheets from this e.g. FAQs to prepare workshops (if you run them)
• offer free lunches
• Establish faculty mentors
Don’ts
• Assume they will come to the test server – students will, but staff wont. Find a core group of early adopters
• Don’t assume that silence is golden – be proactive and ask if it’s working
Some caveats with v9
- The new interface can be a little overwhelming? – The edit mode and content browser is different – even confident v8/7 users, who won’t come to training, get stuck.
- More than the interface, staff finf the Gradecentre overwhelmingly different.
- Respondus in v9 requires a new version. Learning Objects, Wimba, Elluminate all seem to be ok. Bb ran a building block programme where the bigger vendors developed and released updates; smaller building blocks MAY NOT WORK.
- Find out which staff members are using the old tools and make them aware of the changes.
No comments:
Post a Comment