Among the professional groups I belong to on LinkedIn, one of my favorites is the E-Learning 2.0 group.
Recently group member asked a very interesting question of the group in a quest for solving the always challenging issue of how to add e-learning to an existing training or educational program.
For reasons completely unfathomable to me, I have a lot to say on this subject. (Maybe its because this is how I’ve been making my living for the last 20 years.) Ha, ha!!!
But seriously, my company FutureU was launched back in 1998 specifically to answer this question and we’ve been at it ever sense with clients ranging from the American Hospital Association to the NASA Astrobiology Institute, from Pacific Bell to Fujitsu America, from Dominican University of California to Missouri State University, from Universidad Interamericana de Puerto Rico to King Abdul-aziz University in Saudi Arabia, to name a few.
So I decided to post my suggestions to my “Build Your Course Online” blog then share a link to it with the group. That gives me double the traction for half the work (I know it may be seen by some as cheating, but I don’t have a marketing staff, so I must get as much function as I can out of everything I do, to keep up with the demands of maintaining a social media presence).
I’m not the only one with some good ideas about this though, so if you have a LinkedIn account, jump on over to the e-learning 2.0 group to see what other people have to say.
My first caution is to take an organized approach. Use a simplified design cycle model to start with. I prefer the simple 4D’s model I developed for working with my own clients:
1. Discovery (learn everything you can about the initiative your planning; what’s gone on before; what are the features you think you’ll need; and so forth.)
2. Design (run some pilot testing of “bench models” you design that you think will meet your needs. For LMSs that could include actual pilot courses within the software. Many vendors will support this.).
3. Development (with everthing you learned up to this point, prepare for roll out. get the hardware and software into place or finalize the arrangements with the hosting partner. have some volunteers do real work in the environment to make sure evrything seems to be working)
3. Delivery (hold a launch event for the benefit of both your people and your customers, keep track of any problems that arise, collect feed back on how things are going on a regular basis, after a sufficient time period, conduct an evaluation and identify what needs to be dropped, changed or added).
Next post: Let’s talk a bit about IT resistence.
Recent Comments