Traditionally elearning courses have been storyboarded so the instructional designer can plan the content and activities and get feedback before starting to build the course. Storyboarding allows you to check your design is on target with expectations before investing time in developing.
However, sometimes it makes even more sense to rapid prototype rather than storyboard. Rapid prototyping is where all or some parts of an elearning course or activity are roughly built i.e. it’s a working model that’s not in the finished polished state. Rapid prototyping shows what you intend to do – whereas storyboarding tells what you intend to do.
So when does it make more sense to rapid prototype rather than storyboard. Put simply – when it is more useful to show how it works rather than tell how it will work. Here are some situations when I choose to rapid prototype rather than storyboard:
Working with SMEs or clients new to elearning
If I’m working with clients that have little or no prior experience of elearning I will prototype parts of elearning interactions (or show them a similar elearning interaction) so they can see exactly what a drag and drop, system demo, contextual feedback, or a branching scenario looks like.
When look and feel is important
Look and feel is always important but sometimes you might need to show rather than tell look and feel. This could be an advantage when a client’s preferences are to see how it works. It could also be wise to prototype part of a course if you are investing a lot of time and energy into the look and feel of a theme, or if you’re a developing a series of modules that will all have the same look and feel. Better to have solid agreement at the beginning rather than developing 10 modules, only for the client to ask you to change the look and feel afterwards!
When rapid prototyping will save or not add any more time
Sometimes I’ve actually found it quicker to skip the storyboard stage altogether and go straight into rapid prototyping an elearning interaction. For example, I usually go straight to prototyping for software simulations. I do this as I find it more useful/quicker/easier to get feedback from a prototype (working model) than from a storyboard presented on paper. Even though it may take slightly longer to rapid prototype it saves me time as it’s part drafted in the tool already and it results in a clearer vision of what the final product will be.
For a complicated interaction
If the interaction is complicated it can be useful to roughly prototype and get feedback from stakeholders before investing the extra time in perfecting the interaction and graphics. It’s also useful when it’s difficult to explain a type of interaction. For example, I’m currently prototyping an interaction in Articulate Storyline where the learner will receive individualised feedback based on their previous choices. It’s hard to explain what I’m doing in text, but I’ll show you the rapid prototype once I’m done – push the follow button to subscribe and get notified of when this is ready for you to view.
What do you think about rapid prototyping? Are there times when you choose to rapid prototype rather than storyboard? I’d love to hear your thoughts – follow me to hear more of mine.