Action mapping is a streamlined approach to instructional design that focuses on changing what people do on the job, not just delivering information. Created by instructional designer Cathy Moore, it’s a visual, four-step process that works backward from a measurable business problem to determine what training (if any) is actually needed. The core idea: most workplace training fails because it dumps information on learners instead of helping them practice real decisions.
The Problem Action Mapping Solves
When organizations identify a performance problem, the default instinct is to gather as much information as possible and turn it into a presentation or an online course. Maybe the designer chunks the content into modules, adds engaging graphics, or wraps it in a story. Cathy Moore calls this approach an “information dump,” and it’s the standard operating mode for most corporate training. The result is courses packed with content that learners forget within days, with no measurable change in how they do their work.
Action mapping exists to break that cycle. Instead of asking “what do people need to know?” it asks “what do people need to do differently, and what’s stopping them?” This shift in starting point changes everything downstream: the training gets shorter, more focused, and built around practice rather than presentation. In many cases, the process reveals that training isn’t even the right solution, saving organizations from building courses that were never going to fix the real problem.
The Four Steps
Action mapping follows a specific sequence. Each step feeds the next, and skipping ahead (especially jumping straight to content creation) undermines the whole approach.
Step 1: Identify a Measurable Business Goal
The process starts with a simple question: what are we currently measuring that tells us we have a problem? Rather than accepting a vague request like “we need a course on customer service,” action mapping pushes you to define the specific metric you’re trying to move. That might be a reduction in customer complaints, faster resolution times, or fewer compliance violations. This goal becomes the anchor for every decision that follows. If an activity or piece of content doesn’t connect back to this goal, it doesn’t belong in the training.
Step 2: Identify What People Need to Do
With the goal defined, the next step is listing the on-the-job behaviors people need to perform to reach it. These aren’t learning objectives in the traditional sense. They’re visible, specific actions that someone with a clipboard could observe and check off. “Understand the refund policy” doesn’t qualify. “Offer the correct refund option based on the customer’s purchase date” does.
This is where action mapping diverges most sharply from traditional instructional design. Moore emphasizes focusing on what people need to do, not what they need to know. A conventional learning objective might say “identify the three types of customer complaints.” An action mapping behavior would describe what someone actually does when a customer complains. The distinction matters because knowledge-focused objectives lead to information-heavy courses, while behavior-focused ones lead to practice.
Once you’ve listed the key behaviors, you examine each one to identify barriers to good performance. Sometimes the barrier is a genuine skill gap that training can address. Other times, the barrier is a confusing process, a poorly designed tool, or a lack of motivation. Those problems need different solutions, not a course.
Step 3: Design Realistic Practice Activities
For the behaviors that genuinely require training, the next step is brainstorming activities that let people practice making the same decisions they make on the job. These aren’t quizzes or knowledge checks. They’re simulations, scenarios, or exercises that mimic real situations as closely as possible.
If an employee regularly faces a specific type of customer complaint, for example, the activity puts them in that situation and asks them to choose how to respond. They get to work through the decision, see the consequences, and try again. This kind of practice builds the judgment and confidence that information alone can’t provide. The activities should feel like a realistic preview of the job, not a test of memorized facts.
Step 4: Add Only the Minimum Necessary Information
This is the step that makes action mapping feel counterintuitive for most designers. Instead of front-loading content and then testing on it, you work backward: what’s the absolute minimum someone needs to know to complete the practice activity? That information gets included. Everything else gets cut or moved to a job aid that people can reference while working.
The key question is whether something needs to be memorized or can be looked up. Background context, historical details, and nice-to-know facts almost always fall into the “look it up” category. What remains is a lean, focused set of information directly tied to the decisions learners are practicing. This step ensures the training stays streamlined and free from the filler content that buries the important stuff.
How Action Mapping Differs From Traditional Models
The most widely known instructional design framework is ADDIE (Analyze, Design, Develop, Implement, Evaluate), which provides a broad process for building any kind of training. Action mapping isn’t a full replacement for ADDIE or similar models. It zooms in on the front-end analysis and design decisions that traditional models leave relatively open-ended. Where ADDIE tells you to analyze and then design, action mapping tells you exactly how to analyze and what your design priorities should be.
The practical difference is where you spend your time. In a traditional ADDIE workflow, designers often spend the bulk of their effort gathering content from subject matter experts, organizing it into a logical structure, and making it presentable. In action mapping, the bulk of effort goes into defining the right goal, identifying the right behaviors, and designing the right practice activities. Content creation comes last and gets the lightest treatment. This reallocation of effort is what makes action mapping particularly effective for corporate and organizational training, where the ultimate measure of success is job performance, not test scores.
The Visual Map
Action mapping gets its name partly from the visual diagram at the center of the process. A typical action map places the business goal in the middle, with the target behaviors radiating outward like spokes. Each behavior then connects to its practice activities and supporting information. This layout makes it easy to see whether every element in the training ties back to the goal, and it gives stakeholders a clear, non-technical way to review and approve the training plan before development begins.
The visual format also helps during conversations with subject matter experts, who naturally want to include everything they know about a topic. When you can point to the map and ask “which behavior does this information support?”, it becomes much easier to negotiate what stays in and what gets cut. The map serves as both a planning tool and a communication tool, keeping everyone focused on performance outcomes rather than content volume.
When Action Mapping Works Best
Action mapping is strongest in situations where there’s a clear, measurable performance problem tied to specific job behaviors. Corporate compliance training, sales skills, customer service procedures, software workflows, and safety protocols are all natural fits. Any time you can point to a metric that needs to improve and trace it back to things people are or aren’t doing, action mapping gives you a disciplined way to build training that targets exactly those behaviors.
It’s less naturally suited to academic education or situations where the goal is broad knowledge acquisition rather than specific behavior change. Some educators have adapted the approach for classroom settings, but Moore herself notes that the adaptation often drifts back toward knowledge-transfer objectives, which works against the method’s core purpose. If your goal is to help someone pass a test by identifying or describing concepts, you’re solving a different problem than the one action mapping was designed for.