Like Phil we go straight to the prototyping. I'm looking forward to reading more ideas from all of you! I convert it to my layout/design aesthetic, switch out images, customize as needed, but frequently the majority (if not ALL) of the interaction build has already been done.Īll that being said, I'd say I tweak my process every single project. Sometimes it gives me ideas, more often than not, I find one that I can use as the base of my interaction.

I'm looking at concept only- what action is happening. Then - and this isn't really part of this conversation but it's become a huge part of the 'rapid' in my prototyping - I look through my library of interactions already created by Articulate and community members. Once I am ready to develop them, the SMEs have already signed off on the content. When I plug in the content, media and interactions are largely just placeholders. My first pass (iteration) in the dev tool is largely when I lay down the overall look and feel. Once I have everything that will go IN the course, I start working in the rapid development tool. If they do want to talk about it, I'm going to show them an example of something existing instead of creating something. Sometimes I have an idea already of what the interaction will be but for the most part I just mark it as a potential interaction and focus on talking to the SMEs about what goes in it - not what it will look like. I do have a section to capture design ideas and elements along the way, but the most I do with interactions is identify where they will likely add the most value. So we're basically rapid prototyping the content and flow at this stage. I'll collaborate with SMEs and take many passes thru the storyboard before ever touching the development tool.

Instead I'll use it as a reference to pull out the relevant material. I do NOT want to work from inside their deck. If they've already given me content in a ppt deck or other format, I'll still do it this way. Once I have an outline, I plug that in and work with the SMEs to build out the content. In some ways, my storyboard is part of my rapid prototyping. I would really like to know how you approach e-Learning design,Īnd what are your ideas on the Storyboard vs. And, well, yes I can still plan the course, it's navigationĪnd sequencing, but doesn't that end up being a mix of the two approaches? It's a lot more effective in conveying the ideaīehind the interaction. On the other hand, it lacks the planning specs a The client can almost try them for himself, instead of reading anĮxplanatory note about it.

Having a course prototype is great when I want to show Interaction works than to explain it in words. Have them reviewed by someone else (like the client) is easier to show how the Understand the interactions because I'm the planning them. Outcomes), and can also give a feel on the course design. However, it does It gives a good view on how navigation will work,Ĭontent sequencing (especially when you have learning activities with multiple Lately, I've debating myself about whether is the best approach for planning and designing anīoth approaches have their ups and downs, and I can't really

Storyboard quick format