I recently finished teaching a course called EDTEC 700 - eLearning Development Tools. It was an instructor led course with two 8 hour sessions. I’ve linked to silent versions of 3 of my presentations as well as the prototypes and tutorials that the students created using Adobe Captivate and the Articulate Studio.
- Here’s the slides from our first class.
- Here is a brief look at 3 ways to track eLearning without an LMS
- Slides for our second class.
Here are links to your classmate’s prototypes
These projects were created during our 6 hour development workshop.
Professor Karl’s Final Words of Wisdom
You may remember we started this class with a look at ADDIE. I wanted to close this session with a look back at the first question you all answered for me.
“Are you an instructional designer?”
This class was deliberately designed to take you out of the ID role. You’ve had (or will have) plenty of opportunities to do ID work in the other courses in our program. eLearning Development Tools was a class on development.
That’s all we did during our workshop session. Develop. There wasn’t any time to rewrite the text you were given. You weren’t able to design meaningful exercises that enhance a transfer to performance. You were too busy. This course was designed to prevent you from acting an instructional designer. I did my best to force you to work almost exclusively as an eLearning Developer.
And from what I’m seeing in your projects so far, you’re good ones. It really is an impressive group of work. As brand new users, you were able to develop a SCORM-compliant course in less than 6 hours.
I hope that you continue using these tools. I look forward to hearing about Articulate and Captivate presentations in our other classes, and seeing them in your portfolios.
Several of you mentioned that you wish there was enough time to polish these tutorials so they could become a part of your portfolio. Seeing the results of your 6 hours or work on Saturday, I can only imagine how professional these could look with another intense session like that. Or even a half-day like that.
I’ll close this by saying that even though I’m trying to distinguish between your role as a developer and your role as a designer, I don’t think you should choose between one or the other. You should be both. Combine your expertise as an ID with your skills as a developer and double your own value.