Storyboard vs. Rapid Prototype
Lately, I've debating myself about whether is the best approach for planning and designing an e-Learning course: Storyboard or Rapid Prototype.
Both approaches have their ups and downs, and I can't really decide for one of them, but keep falling somewhere in the middle.
Storyboard is a good way to plan the course. It gives a good view on how navigation will work, content sequencing (especially when you have learning activities with multiple outcomes), and can also give a feel on the course design. However, it does not help when it comes to interaction. Of course, for me it's easy to understand the interactions because I'm the planning them. But when it comes to have them reviewed by someone else (like the client) is easier to show how the interaction works than to explain it in words.
This is where I believe rapid prototyping pitches in.
Having a course prototype is great when I want to show interactions. The client can almost try them for himself, instead of reading an explanatory note about it. It's a lot more effective in conveying the idea behind the interaction. On the other hand, it lacks the planning specs a storyboard offers. And, well, yes I can still plan the course, it's navigation and sequencing, but doesn't that end up being a mix of the two approaches?
I would really like to know how you approach e-Learning design, and what are your ideas on the Storyboard vs. Rapid Prototype duel.
Thanks for your input!