Have you ever heard the term affordance? If you haven’t, you’re not alone, but it’s an important design principle that e-learning designers need to understand. Affordances are an object’s characteristics or aspects of their design that provide clues and suggestions for interaction. Affordance can be explicit, meaning made obvious by an object’s physical appearance, and also perceived, meaning influenced by past experiences and interactions.

For example, not only does the handle on a mug physically represent something we can slide our fingers into and hold onto, but our past interactions with objects that have handles also clue us in as to its use.

Affordance is an important concept in e-learning design, particularly explicit affordance. When we design training we include buttons, hyperlinks, data entry fields, and other elements. By understanding affordances and how they influence the course-taker, we can help learners navigate our training more easily.

Look at the following buttons to see how affordance makes one button stand out more than the others:

Take a look at the following text entry fields. Which one provides the clearest explicit affordance?

These are a few examples of how affordance can impact a learner’s ability to get through your course. Providing explicit affordance makes e-learning content more intuitive and easier to follow. When learners are distracted trying to figure out what they’re supposed to do next, they can’t focus on what really matters, which is the course content.

Here are a few things you can do to provide learners with clear, explicit affordance:

Follow established design standards

As you design your courses, follow established design standards that are used in the web and design industry. These design standards are constantly changing and evolving, but e-learning design takes a lot of its cues from the standards in these industries. Keep an eye on trends and designs to make sure your courses look and feel up to date.

Use direct and concise text

It’s crucial to use concise language and clear instructions. Be ruthless in your text editing and get rid of every word you don’t need. Edit out any information that is nice-to-know (as opposed to need-to-know) and make your text as to the point as possible. Keep in mind that using action verbs will help ensure your learners know what to do.

Do thorough user testing

The best way to know if your learners are getting the explicit affordance cues you’ve included is by doing thorough user testing. This is a critical part of development, and one that you should not skip. You can gather information by observing or recording your learners as they complete the module and also by gathering their feedback during and after the course. Ask them questions about where they got stuck, whether they ever felt lost, whether the navigation was clear, etc.

Next time you design a course, be aware of affordance and how it’s influencing your course design. Follow the three tips listed above to make sure you’re always clear about what you want learners to do. If you have any tips of your own, I’d love for you to share them in the comments below.

Follow us on Twitter and come back to E-Learning Heroes regularly for more helpful advice on everything related to e-learning. If you have any questions, please share them in the comments.

4 Comments
Przemysław Hubisz
Ray Cole

The advice to follow standards is good, but one has be be thoughtful about which standards. A recent example I encountered was a remote control that came with a new TV I got for my father. Both of us were baffled about how to raise or lower the volume from the remote, because the normal Volume Up/Down buttons were not present. Turns out the designer of the remote control put the volume control buttons on the side of the remote, instead of the front. That *does* follow a design standard, but it's the *wrong* design standard. Tiny little Volume Up/Down buttons are on the sides of many cell phones. But my father and I both have a lifetime of experience using television remote controls, and it is *not* a common practice in remote control design to have the volume controls on the side like that... Expand