Strategy Map

A strategy map is a one-page diagram, drawn from the Balanced Scorecard framework of Robert Kaplan and David Norton, that shows how an organization's strategic objectives connect and reinforce one another. It arranges those objectives across the Scorecard's four perspectives, usually stacked from bottom to top: learning and growth (people, skills, culture, systems), internal processes (the activities the organization must excel at), customer (the value delivered to customers), and financial (the results owners care about). The map then draws cause-and-effect arrows between objectives, so you can read a chain upward — better-trained staff improve a key process, which raises customer satisfaction, which lifts revenue. The point is to make strategy visible and coherent on a single page, showing not just a list of goals but how they are meant to drive one another toward the financial outcomes at the top.

A strategy map matters because strategy usually lives as a scattered set of goals, initiatives, and metrics that few people can hold in their heads at once. By laying the objectives out across the four perspectives and linking them with explicit cause-and-effect logic, the map turns that scatter into a story anyone can follow — and can therefore challenge. It forces leaders to state their assumptions: if we improve this capability, we believe it will lift that customer outcome, which will produce that financial result. Those links can be tested against reality, which is more than a bullet list allows. It also aligns the organization, because everyone can see how their objective feeds the ones above it and where their work fits in the whole. Used with the Balanced Scorecard's measures and targets, the map is the picture that gives the numbers meaning.

A strategy map is easily confused with a roadmap, but they organize different things. A strategy map is about cause and effect: it shows why objectives matter by linking them across the four perspectives, arguing that improving one thing drives another. It is essentially timeless in structure — a logic of how value is created, not a schedule. A roadmap is about sequence and time: it lays out what will be done and when, ordering initiatives, milestones, and deliverables along a timeline. One answers how our goals connect to produce results; the other answers in what order and by when we will do the work. A strategy map explains the theory of the strategy. A roadmap plans its execution over time, and the two should not be swapped for each other.

The two are complements, and the confusion causes real problems when they are substituted for each other. Treat a roadmap as a strategy and you get a well-sequenced list of activities with no explanation of why they add up to a winning position — motion without a theory of value. Treat a strategy map as a plan and you get a compelling logic with no dates, owners, or order of execution — a theory no one is scheduled to deliver. Good practice uses both: the strategy map to agree on the cause-and-effect logic and the objectives that matter, then a roadmap to sequence the initiatives that will move those objectives over time. The map sets the destination and the reasoning; the roadmap sets the route and the calendar. Keeping them distinct keeps each one sharp.

Using a strategy map well means treating the cause-and-effect links as real hypotheses, not decoration. Each arrow claims that improving one objective will lift another, and that claim should be plausible, testable, and later checked against the Balanced Scorecard measures attached to the objectives. Keep the map focused — a page crowded with dozens of objectives and a tangle of arrows communicates nothing, while a clear map of the handful of objectives that truly matter, linked in a readable chain from learning and growth up to financial results, tells the strategy at a glance. Tie every objective to a measure and a target so the map connects to the Scorecard's numbers, and revisit it as the strategy evolves, since a map that no longer matches what the organization is actually pursuing quietly misleads everyone who reads it.

The failures are mostly about rigor and upkeep. Drawing cause-and-effect arrows the organization does not actually believe, or cannot test, turns the map into a decorative diagram rather than a strategic argument. Overloading it with objectives destroys the clarity that is the whole reason to draw one. Building a map with no linked measures leaves it disconnected from the Scorecard it belongs to, so it never gets validated against results. And letting the map go stale as strategy shifts leaves a confident-looking picture of a strategy no longer being followed. The discipline is to keep the map lean, make its links genuine and testable, tie each objective to a measure and target, and update it as the strategy changes — so it stays an honest, legible account of how the organization intends to create value.

The strategy map was introduced by Robert Kaplan and David Norton as the visual companion to their Balanced Scorecard, developed through the 1990s and early 2000s.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where strategy map is a core concern: