Subscribe via Email!

Your email:

More from Allen Interactions:

10 Ways to Ruin


[Kit Download]

10 Ways to Ruin
Your e-Learning
Download Now ▶

ASTD


ASTD e-Learning Instructional Design Workshops
Learn More ▶

Connect with Us!

Allen Interactions - LinkedIn - Connect with Us!  Allen Interactions - Twitter   Allen Interactions - Facebook

Posts by category

e-Learning Leadership Blog

Current Articles | RSS Feed RSS Feed

Prototypes Are Essential to e-Learning Design

 

Richard Sitesby , vice president - client services | @rhillsites

As many of my colleagues are at ASTD TechKnowledge 2013 enjoying the California weather, I am stuck here in the Atlanta airport – dodging tornadoes and dealing with weather delays.  For those of you at the conference, I hope you have been able to attend some of the Allen Interactions and ZebraZapps demonstrations, workshops and sessions.   We are sharing the new features of ZebraZapps Professional and the first day-long workshop about SAM, the iterative design and development process that Michael Allen and I co-authored a book about in September.

I admit I am a bit envious of those of you who, like my co-workers, are enjoying northern California in winter while participating in sessions and roundtables, engaging in conversations about building instruction and training, debating about the best tools to create high quality e-learning, or even spending time with old friends reminiscing about the old days.

I figured since I wasn't able to attend the conference and engage in some of those debates and conversations, I would share a topic that has been coming up a lot for me lately - the role of prototyping.

Designing effective and engaging e-learning can be a challenging endeavor. There are many expectations by many people in the organization – all needing to be recognized and accounted for before any course goes live. Couple those expectations with the requirements of budget and timelines, and it is easy to understand how designing quality learning events can be overwhelming.

So sadly, more often than not, we fall back on designs which made it through the approval process in the past – they are safe and reasonably effective. We fear rocking the boat with crazy notions of interactivity and settle for a fancy page-turner preceding an assessment. And why not? This has produced good results for us in the past, surely it will again. But has it produced the results you are looking for, or has it simply put a pretty course in front of a learner? Are learners engaged? Are they transferring their training to their work environment? Or, are they simply completing the course only to forget the content within minutes of exiting?

Perhaps it is time to try and push your design a step further - to avoid the trap of playing it safe. One way to make this effort more effective is through the use of prototypes. Prototypes are powerful because they provide clear insight into the design while assuring alignment of expectations of everyone involved.

Understanding what prototypes are, how they are built and their role in design is the biggest hurdle.  So what exactly is a prototype? I have seen people create semi-functional prototypes only to use them as screen captures in a storyboard. Others build prototypes which only demonstrate simple designs for assessment, like drag-and-drop or multi-select. And others simply sketch out where components will be on the screen.

Each of these may help show the elements of the proposed solution, but they do little to further the discussion of what works, what doesn’t and what more can (or should) be done to support the learning experience.

ScreenCapProtoA prototype is a tangible idea or concept in the form of a roughly constructed interactive component with few words and either no media, stand-in media or sketches. This definition leaves a lot of room for what might be included, and that’s ok! The idea is that it functions enough to interactively demonstrate the design idea or concept.

You can build a prototype in PowerPoint, Captivate, Articulate Storyline, Flash and especially ZebraZapps! My only suggestion is that you use a tool which allows you to build quickly. Prototypes, at their core, are meant to be disposable. If you can’t throw it away, then you can’t really critically evaluate its effectiveness.

Why is this important? Let me highlight some reasons why we believe prototypes are essential to e-learning design.

  1. Even the slightest ambiguities in the beginning will result in serious problems in later iterations – especially the final product.
    Every designer knows the impact of late changes to a design. Prototypes allow for the involvement of stakeholders early in the design discussion by allowing everyone to see and react - long before the final deliverable.
     
  2. Words can’t adequately describe media-rich interaction.
    While many feel confident that storyboards are effective at conveying design, it’s just too difficult – and risky – to assume everyone is able to interpret media-rich interactions from written documents.
     
  3. e-Learning interactivity needs to be witnessed and experienced for effective evaluation.
    How the interaction will react and respond to learner decisions and choices is the critical part of the design. This must be witnessed in order to effectively evaluate the appropriateness of the interaction.
     
  4. Working with prototypes can point out deficiencies and reveal unseen opportunities that are not apparent in sketches and specification documents.
    “Ah-ha!” moments are either wonderful or challenging depending on when they occur in the process. The late ones cause project overruns while early ones can provide inspiration for improved design. Prototypes create early and inexpensive opportunities for “ah-ha!” moments.

There are a lot of debates which may occur during the development of an e-learning project, but none more important than the critical discussions that occur from experiencing the course itself. Prototypes provide the opportunity to promote these discussions to the beginning rather than the end of the development process.

I am sure that there are some really good discussions happening right now at TechKnowledge about prototypes…and if there are not, someone start one! 

Comments

I've been inspired by the rapid prototyping that Allen does that I decided to take the plunge and do this for a course I'm developing. 
 
The business team thought - let's just take the ILT course we developed in PPT and just slap it into our LMS. Anyone else ever have this happen?  
 
I pushed back and asked them to look at some alternatives before we went ahead with dumping > 100 PPT slides into our LMS. We had a series of prototyping meetings to discuss this. 
 
They didn't like my first prototype but were wowed by the second one that was developed based on their feedback to the first prototype. 
 
My solution won't be as engaging as I'd like. I did, though, get the page count to < 70 pages. It sure beats the page turner that the business initally thought would be our final learning solution. And, best of all, it saves my learners some time and gives them a better learning experience.
Posted @ Thursday, January 31, 2013 3:48 PM by Joanne
Focusing on interactivity is spot on. While pictures are better than just words, and a video can be richer than still images, with interaction there's a huge difference between talking about it and doing it. Surprisingly, making a prototype is often faster than trying to explain something still, especially if you have to argue at a later phase.
Posted @ Thursday, January 31, 2013 5:26 PM by Jason Durkee
Joanne, 
 
What a wonderful result from your first attempt at prototyping. This is a great example of the power of prototyping! 
 
Thanks for sharing your story! 
 
Best of luck, 
Richard
Posted @ Friday, February 01, 2013 8:56 AM by Richard Sites
Jason, 
 
Exactly! You have nailed the essence of prototyping perfectly! 
 
Thanks for your comment. 
 
Richard 
Posted @ Friday, February 01, 2013 9:00 AM by Richard Sites
My experience with rapid prototyping isn't good. One issue I have is that though clients demand it they seem to require the sample to be a fairly exact representation of what they might see. That wouldn't be so troublesome if clients were flexible. But no matter what you tell them they are often of the mind to "sign off" on the design right away satisfied that you've rapidly found the solution. It's that persistence once they find something they like. Meanwhile you may find the design won't work. Adhering to the proven may well be boring, however, if you add new layers of complexity you run the risk of disappointing a client, no matter how much your experience with a given set of authoring tools.
Posted @ Wednesday, February 06, 2013 3:31 PM by Kevin Handy
Comments have been closed for this article.