Learning Ninjas

Everyone deserves a chance to learn.

Resources

By Leave a Comment

Prototyping in Elearning

Prototyping is a vital step in the design process in many other industries. So, why don’t we use prototypes when we develop new content? Is it a lack of time? Is it that we are just converting existing material and we think we do not need it? Maybe, in some cases, we think we already know what the learner needs. Even if all that were true, we should follow other industry best practices and create prototypes for our content.

What is a prototype?

Prototypes can be created in many different ways. Create physical prototypes (also called paper prototypes) with simple office supplies to show the end user an approximate facsimile of the interface. The user interacts with the interface and the designer/developer is able to watch the interactions. The paper prototype gives feedback about mouse movement and the general layout. Since it is early in the design process, this feedback comes when you can easily change layout and element placement.

A second type of prototype is the digital prototype. Build digital prototypes with tools like Balsamiq or Moqups, tools web designers use to create wireframes. eLearning rapid development tools such as Captivate or Storyline could also be used to setup the digital prototype, though it’s often faster to prototype in standard presentation tools like PowerPoint or Keynote. Use the digital prototype in conjunction with the physical prototype as an added layer of fidelity. The physical prototype is somewhat abstract in that you are just trying to get the placement of elements down. Start to add real content to the digital prototype to achieve a more refined edition. A benefit of the digital prototype is the ability to share it with a wider audience since it does not require users to be in the same physical location.

Why are prototypes so important?

The primary goal of prototyping is feedback. When we receive feedback early in the design process, we can change things more easily and rapidly. It takes only a few minutes to alter the entire layout of a physical prototype. Prototyping also allows you to quickly test ideas with your audience rather than spending extra hours in the development phase. Once the physical prototype is set, create a digital prototype and refine it as you go forward. Then, when development starts , you have a clear path forward with the design. Use prototypes to get sign-off from stakeholders throughout the design process to reduce conflict and surprises when development begins.

Take the time to create prototypes during your design process. It will save you valuable time during the development process. Web design and app design have showed us that these methodologies are worth the effort.

Happy prototyping!

Related:

Learning from the Web World: Paper Prototyping

Workshops

By 3 Comments

Learning from the Web World: Paper Prototyping

I thought it might be useful to do a few posts on usability testing, with a discussion on how each method of testing contributes to the e-learning world. Whenever you’re testing, it’s best to have testers that approximate (or, better yet, who are part of) the intended users of the learning. The beauty of this type of testing is that you can find most of the issues with testing only 5 users or less (see http://www.measuringusability.com/five-users.php). This week, I’m going to cover the basics of paper prototyping for e-learning.

Paper prototyping is a common method utilized in the human-computer interface world – but how often do we use this method for testing learning designs with real users? I recommend paper prototyping as a cheap, easy-to-implement way to detect usability problems, scope issues, and any issues with information architecture. So how do you get started with paper prototype testing?

Paper prototyping isn’t difficult, but you do have to do some preparatory steps.

  1. First, you will need a list of the common tasks users may need to “do” in your interface. This might include finding information, passing a quiz, or completing an activity. If you have actual users, you may also ask them what other tasks they might expect to complete with the interface.
  2. Next, you have paper versions (these can be sketches) of what you expect the learning module or course to look like. It should include a menu and any buttons that are going to be part of the interface. Each piece of paper should have a rough sketch of where you would go if you clicked any button. Thus, if you have a “Next” button, then you would have another piece of paper that has the interface if the “Next” button were pressed.

    A rough sketch of an interface
    A rough sketch of an interface
  3. Prototype of a mobile interface
    A paper prototype of a mobile interface

    Finally, you give the users the task they are supposed to complete, such as “Find the information about when the next training is to take place” and hand them the home screen. The user should point to where they would click, and then you replace the first paper with whatever they might see if that button/link were pressed.  This process continues, while the tester notes issues or other difficulties with the interface. The user is also asked for feedback.

This kind of collaborative testing doesn’t take long, is cost-effective, and can find some obvious issues with interfaces. In addition, it offers the designer and developer the opportunity to hear from the users regarding what they prefer in the interface they may be using. Why not try it for your next project?

More information on paper prototyping: http://www.alistapart.com/articles/paperprototyping/

Next post, we’ll take a look at the different ways to use card sorts to organize content for e-learning. I hope you’ll plan to stop by!