What Is Action Mapping? – Training That Changes What People Do
Picture the usual request: "We need a course on the new returns policy." A subject matter expert sends a 40-slide deck, the designer turns it into screens and a quiz, and everyone moves on. Months later, the same returns mistakes keep happening. The course delivered information, but nothing in it asked people to practice the decisions they get wrong. Action mapping was created to break that pattern. What is action mapping, and how does it lead to training that changes what people actually do?
Action mapping is a training design method, developed by Cathy Moore, that starts with a measurable business goal, identifies the specific actions people need to take on the job to reach it, and then designs realistic practice for those actions, adding only the information people need to complete that practice. It flips the usual content-first approach. Instead of asking "What do they need to know?" it asks "What do they need to do, and why aren't they doing it?" That second question often reveals problems training can't fix, such as unclear processes or missing tools. The result is usually a shorter, more practical course, or sometimes no course at all.
How Does Action Mapping Work, Step by Step?
Action mapping follows a short sequence. Moore describes it as a visual map, with the goal in the center and actions, practice activities and information branching outward. Her original post on action mapping as a visual approach to training design is still a good primer.
- Write a measurable business goal. Name a metric the organization already cares about. "Reduce returns caused by incorrect setup" is a goal. "Help staff understand the product" is not.
- List what people need to do. Identify the specific, observable actions on the job that would move that metric. Focus on behaviors, not knowledge.
- Ask why they aren't doing it. For each important action, look at the barriers. Is it knowledge or skill? Or is it the environment, such as a confusing tool, a conflicting incentive or a lack of time?
- Design practice for the actions training can help. Create realistic activities, often scenarios, where people make the same decisions they face on the job.
- Add only the information needed. Provide the facts and references people need to complete the practice, ideally as optional help or job aids rather than mandatory presentations.
Step three is what sets action mapping apart. It turns the designer from an order-taker into a consultant who helps the client find the real cause of a performance problem.
How Is Action Mapping Different from Traditional Course Design?
The difference is the starting point. Traditional, content-first design starts with the information and asks how to present it. Action mapping starts with performance and treats information as a supporting resource.
| Aspect | Content-first design | Action mapping |
|---|---|---|
| Starting question | What do they need to know? | What do they need to do? |
| Main activity | Presenting information, then a quiz | Realistic decision-making practice |
| Role of information | The core of the course | Available when needed for practice |
| Success measure | Completions and quiz scores | Change in a business metric |
| Possible outcome | Always a course | A course, a job aid, a process fix or a mix |
What Does an Action Map Look Like in Practice?
Here is a simplified example. Say a company sells home internet equipment, and too many customers return routers that actually work because they couldn't set them up.
The goal is to reduce returns of working routers caused by setup problems, measured through return reason codes. The team then lists actions for support agents: ask which lights are showing on the device, walk the customer through a restart in the correct order, recognize when the problem is the customer's provider account rather than the router and offer a callback instead of a return when setup stalls.
Next, the team asks why agents aren't doing these things. Interviews show that agents are measured on short call times, so they rush to approve returns. They also lack a quick way to check a customer's provider account status. Neither problem is about knowledge.
The final map has three branches. Managers adjust how call time is weighed for setup calls. The support tool gets a status lookup. And agents get a short set of practice scenarios on diagnosing setup problems from what the customer describes, with a short diagnostic job aid. The training piece is smaller than the original request, and far more likely to move the metric.
What Makes a Good Practice Activity in Action Mapping?
A good activity puts learners in a realistic situation and asks them to make the same decision they make at work, with realistic consequences. It is not a quiz about the decision. It is the decision.
Compare two questions about the router example. A knowledge check asks, "Which light indicates a provider connection problem?" A practice activity says, "A customer says the light on the left is blinking orange and she has already restarted twice. What do you say next?" The second one requires the agent to notice, interpret and act, which is the actual job.
Strong activities share a few traits:
- They are built from real situations, often gathered by asking experienced staff about tricky cases.
- The wrong options are mistakes real people make, so learners see their own habits reflected.
- Feedback shows the consequence first ("The customer returns the router; the real problem is unsolved") and then explains.
- Helpful information is available on demand, so learners pull it in when they need it instead of sitting through it first.
That last trait changes how a course feels. Learners who already know the material can move straight to practice, while newer staff can open the reference and learn in context.
Why Does Action Mapping Work So Well?
It works because it lines up with several well-supported ideas about learning and performance.
First, people tend to get better at what they practice, in conditions that resemble where they will use it. Transfer of learning is far more likely when practice mirrors the real decision. Action mapping builds the course around those decisions.
Second, cutting non-essential information reduces mental overload. Working memory can only handle a few new elements at once, and courses stuffed with "nice to know" content compete with the important material. Cognitive load theory explains why lean, focused instruction tends to beat comprehensive coverage, especially for beginners.
Third, it respects the reality that many performance problems are not training problems. Performance researchers such as Thomas Gilbert argued decades ago that environmental factors, including information, tools and incentives, often explain more of a performance gap than individual knowledge does. Action mapping builds that check into every project.
When Is Action Mapping Not the Best Fit?
I'm a big fan of action mapping, but it's not a universal answer. It fits less well in a few situations:
- Pure awareness requirements. Some regulations require that people receive specific information, whatever the behavior goal. You can still add practice, but some content is mandatory.
- Foundational knowledge for complete beginners. New entrants to a technical field may need structured conceptual grounding before realistic practice makes sense.
- No access to the business. If you can't talk to managers or see performance data, you can't define a meaningful goal or find the real barriers.
- Very small, simple tasks. A two-minute how-to video for a software feature doesn't need a full map.
Even in these cases, the habit of asking "What should people do differently?" improves the result.
How Do You Handle Stakeholders Who Want More Content?
This is the most common obstacle. SMEs and sponsors often equate thoroughness with quality, and a lean, practice-heavy course can look thin to them.
A few approaches help. Bring the business goal into every conversation, so content decisions get judged against it. Offer to put the extra information in a reference or job aid instead of deleting it. Show a sample scenario early, because stakeholders usually warm to realistic practice once they see it. And ask the question Moore recommends in different forms: if people already knew all this content, would the problem go away? Often the honest answer is no.
Action Mapping Turns Training Requests into Performance Solutions
Action mapping, then, is a way of designing training that starts with a business goal, defines the actions people need to take, checks why those actions aren't happening, and builds realistic practice with just enough information to support it. It keeps the focus on behavior and treats information as a tool rather than the point.
The reason it works is that it targets what actually changes performance: practice on real decisions, less clutter and fixes to the environment when the environment is the problem.
The easiest way to see the difference is to map a request you already have. Before you open any slide deck, write the business goal in one sentence and list five things people need to do. You'll likely find the project gets smaller and sharper, and much easier to justify to the people paying for it.