Action Mapping: How to Design Training That Changes What People Do
Most courses are built around information. Action mapping builds them around behavior. Here is the four-step process I use to cut bloated content and design practice that moves a real business metric.
Action mapping is a training design method that starts with a measurable business goal, identifies what people need to do to reach it, and only then decides what practice activities and information are required. It was popularized by learning designer Cathy Moore, and it is the single most useful habit I've picked up as an instructional designer.
The reason is simple: most training requests arrive as content requests. "We need a course on the new expense policy." "Can you turn these 80 slides into eLearning?" Action mapping turns that conversation around, from what should people know to what should people do differently, and why aren't they doing it already?
Step 1: Write a measurable business goal
The goal sits at the center of the map. It should describe a change the organization can see, with a number and a date. "Employees will understand data privacy" is not a goal. "Reduce privacy incidents reported by the support team by 30% within two quarters" is.
A good goal does two jobs. It tells stakeholders why the project exists, and it gives you a filter for every later decision. If a piece of content doesn't help anyone move that number, it doesn't belong in the course.
Step 2: List what people need to do
Next, brainstorm the observable actions that would achieve the goal. Be concrete. "Be careful with customer data" is too vague to practice. "Verify a caller's identity using the two-question check before discussing account details" is something a person can actually do, and something you can watch them do.
I usually run this step as a workshop with two or three subject matter experts and, ideally, someone who does the job today. Sticky notes or a shared whiteboard work fine. Expect 10 to 30 actions, then prioritize the handful that have the biggest impact on the goal.
Step 3: Ask why they aren't doing it already
This is the step that separates action mapping from ordinary course design. For each high-priority action, ask: what makes this hard? The answers usually fall into four buckets:
- Knowledge or skill: they genuinely don't know how. Training can help.
- Environment: the tool is clunky, the form is confusing, the process has an extra step nobody can find.
- Motivation or incentives: the right behavior is slower and nobody is rewarded for it.
- Communication: they were never told the expectation changed.
Only the first bucket is a training problem. The others need a job aid, a process fix, a manager conversation or a system change. Saying this out loud to stakeholders can feel risky, but it is often the most valuable thing an instructional designer contributes. A course cannot fix a broken form.
Step 4: Design practice before content
For the actions that do need training, design practice activities that mirror the real decision. In practice this usually means scenario-based questions: a realistic situation, a choice with plausible options, and consequences that show what happens next.
Only after the practice exists do you ask what information learners need to succeed in it. That information can often live in a job aid they reference during the activity, rather than in ten screens of explanation they click through first. This is how action mapping cuts content. You stop teaching everything that's true and start teaching what's needed.
What an action map looks like in a real project
When I built Cyber Shield Academy, the original brief was a broad "cybersecurity awareness course." Mapping it out shifted the focus to a short list of actions: pause and verify before acting on urgent payment or credential requests, report suspicious messages through one channel, and check unusual voice or video requests through a second channel. Each action became a branching scenario rather than a lecture on threat types.
The same approach shaped the Onboarding Accelerator learning path. Instead of covering every tool a new hire would ever touch, we mapped the tasks they needed to complete in their first week and built the path around those.
Common objections, and how I answer them
"But they need to know the background." Maybe. Put it in a reference they can open when the practice calls for it. If no practice activity ever needs it, ask whether it needs to be in the course at all.
"Compliance requires us to cover everything." Compliance usually requires that the content is available and that completion is recorded. A short, practice-heavy course plus a linked policy document often satisfies both.
"We don't have time for a workshop." A 60-minute call with one expert using the four questions above will still beat starting from the slide deck.
Where to start
Take the next training request you receive and, before opening an authoring tool, write three things on a single page: the business goal with a number, the five most important actions, and the reason each action isn't happening today. That page will change the conversation, and usually the course. If you want to go further, my guide to writing measurable learning objectives picks up where this one leaves off.
Sources
- Cathy Moore, Action mapping: A visual approach to training design
- Cathy Moore, Map It: The hands-on guide to strategic training design (Montesa Press, 2017)