3. Evaluation and Selection
Very basic criteria as a key driver in our
tool selection
(simplicity and affordability)
Centralize? What if someone (college or
dept) is already doing it?
Your mileage may vary: Culture, budgets,
support, enthusiasm…
4. Piloting and Implementation
Very briefly, what did it take to get going?
Recognizing the selling point (50 minute
sessions), but getting users to think in
terms of granularity:
Learning objects / modules / resources
5. Faculty Development I
Tools: How to use what the software
provides
Tricks: How to turn these tools to your
advantage
(or, “So what if you can’t edit?”)
6. Faculty Development II:
Pedagogy – Why use these tools in the
first place?
Looking at the forest: Changing the way
you teach
Replication vs Redesign:
Thinking in terms of directly (and succinctly)
supporting your learning objectives
7. Lessons Learned
Simple tools mean support is not always simple
Start slowly – small numbers, limited options
Emphasize “appropriate” applications
Location doesn’t matter if you can link to it. Duh.
Find your risk takers, limit your risk
“Foolproof” is only a concept
Why not use YouTube?
(Spoiler alert: Faculty and student feedback is
overwhelmingly positive)
Next steps:
User management and self service
8. Thanks….
J. Ritchie Boyd
Teaching and Learning Technology Support Specialist
Office of the Provost
Montana State University
jrboyd@montana.edu
http://jrboyd.posterous.com