A strategy map is a one-page diagram of how an organization intends to create value, arranged in four connected layers: financial results, customers, internal processes, and learning and growth. The boxes hold objectives. The arrows between them are claims about cause and effect. Robert Kaplan and David Norton introduced the format in 2000 as the missing link between a balanced scorecard and action.
That is the definition every guide on this term will give you, and most of them stop there and hand you a template. The template is the easy part. The hard part is that a strategy map is a set of falsifiable claims, and almost no organization ever tests one.
Where the strategy map came from
Kaplan and Norton published Having Trouble with Your Strategy? Then Map It in Harvard Business Review in 2000, several years after the balanced scorecard itself. Their argument was that the scorecard gave executives a balanced set of measures but did not show anyone the logic connecting them. The key to execution, they wrote, is people understanding the processes by which intangible assets get converted into tangible outcomes.
The map has four layers, read from the bottom up:
- Learning and growth: the capabilities the organization has to build. Skills, data, systems, culture.
- Internal process: what the organization does differently once it has those capabilities.
- Customer: what changes for the buyer as a result, in their behavior and their experience.
- Financial: the business result that follows. Revenue, margin, growth, cost position.
Public-sector and nonprofit versions reorder the top two layers, since the mission sits above the money. The structure is otherwise the same.
The arrows are the strategy
Look at any finished strategy map and notice which parts caused an argument in the room. It is rarely the boxes. Almost every large organization will agree that it should improve engineering capability, shorten lead times, raise customer retention and grow margin. Those objectives are close to universal, which is why strategy maps from unrelated companies look so similar.
The arrows are where the actual strategy lives. An arrow from "reduce quote turnaround time" to "increase share of wallet with existing accounts" is a claim: we believe faster quoting is what makes these customers buy more from us, rather than price, product range or account coverage. That claim can be wrong. A competitor in the same market might have drawn an arrow from a completely different process box to the same customer box, and one of you is mistaken.
This is the same logic as a leading indicator, which is a hypothesis in the form "if we improve this, that will follow." The difference between leading and lagging indicators is not really about timing. It is about which measures carry a prediction and which only carry a record. Every arrow on a strategy map asserts a prediction, and a prediction you never check is decoration.
Why most strategy maps stop steering by February
The failure is not that the map is wrong. It is that nothing in the operating model is set up to find out.
ClearPoint Strategy analyzed 20,582 strategic plans and published the results in November 2025. In that set, 74% of strategic goals had no owner and 71% of measures were unassigned. Of the owners who had been assigned, 86% had made no update in 90 days or more. Only 12.5% of strategic projects were ever completed.
Read those numbers against the map. If seven measures in ten have nobody attached to them, then most of the arrows on the diagram have no one whose job it is to notice whether they hold. The map is a picture of a theory that no one is testing. It stays on the intranet, accurate as a description of intent and inert as an instrument, until the next planning cycle produces a slightly different picture of a slightly different theory.
This is a specific and diagnosable pattern, not general neglect. A measure that appears on a dashboard with no owner cannot be improved, and a measure shared across three functions with no single owner produces finger-pointing when it declines instead of a decision. The fix is unglamorous: every measure gets one person who can influence it, or it gets decomposed into parts that can each be owned.
How to build a strategy map you can actually steer
Building the picture takes a workshop. Building something that survives the quarter takes four more decisions.
Start at the impact layer and work backward
Begin with the financial or mission result you are accountable for, then ask what directly drives it, then what drives each of those. Revenue decomposes into customer count, average deal size and win rate. Win rate decomposes into things a team can act on this quarter. Keep going until you reach a level where a named team can move the number through its own work.
This is the value driver tree, and it is the honest way to populate the middle of a strategy map. Working top-down from the financial layer forces each box to justify its place by its connection upward. Working bottom-up collects every worthy initiative in the organization and calls the pile a strategy. We go through the mechanics in KPI trees. The output is a traceable line from a business KPI, through a value driver, to a leading indicator a team owns.
Workpath's KPI management holds these dependencies as structured impact chains, so the picture updates when a number moves instead of sitting still until someone redraws it.
Turn each arrow into a leading indicator
An arrow with no measure attached is an opinion. Give each one a number that would move first if the claim were true.
Good leading indicators share four properties. They correlate with the lagging result, and the correlation has been checked, not assumed. A team can influence them through its own work. They move faster than the thing they predict, so a weekly or monthly reading is meaningful against a quarterly outcome. And they are specific enough to change behavior, which "customer experience" is not and "time to first value" is.
You will not get all of them right. That is the point of writing them down. If the leading indicator improves and the lagging one does not, you have learned something concrete: either the hypothesis was wrong, the lag is longer than you assumed, or something else is interfering. All three are useful. None of them are available to an organization that never named the indicator.
Give every box and every measure an owner
Ownership is where the ClearPoint numbers bite, and it is the cheapest thing on this list to fix. Each objective gets a named owner. Each measure gets a named owner who can actually influence it. Where a measure genuinely spans functions, either name one accountable owner or split the measure until each part has one.
An owner is not a reporter. The job is to hold a view on whether the arrow above their box still looks true, and to say so early when it does not.
Decide in advance where an arrow gets falsified
A hypothesis needs a forum and a date. Two forums do different work here.
- Check-ins, every two weeks: did the work we funded move the leading indicator? This tests the bottom of the chain, where initiatives meet the measures they were meant to shift.
- Reviews, at the end of the cycle: did the leading indicators moving actually move the lagging KPI? This tests the arrow itself.
The second question is the one that gets skipped, because answering it honestly sometimes means the quarter went well and the strategy was still wrong. That is an uncomfortable meeting. It is also the only one where the strategy itself gets checked. Workpath's Business Reviews exist to hold that conversation with the data already in the room, so the hour goes to the arrow instead of to reconstructing what happened.
How a strategy map fits with the balanced scorecard and OKRs
The three are layers of the same system, and organizations get into trouble mainly by treating them as competing choices.
- The balanced scorecard holds the stable structure: the perspectives, the strategic objectives and the KPIs that measure them over years. It changes slowly by design.
- The strategy map is the scorecard's causal picture. It shows why the objectives in one perspective should produce the objectives in the next.
- OKRs operationalize a slice of that picture for one quarter. The Objective names an outcome from the map, the Key Results are the leading indicators for the arrows you have decided to test now, and the initiatives underneath are the work.
Put together, the chain runs from perspective to strategic objective to KPI, down to an outcome-oriented Objective, down to Key Results as leading indicators, down to the initiatives that move them. We look at the framework relationship in more detail in OKRs and the balanced scorecard.
This is also the cleanest way to explain why a strategy map alone does not steer anything. It describes intent across a horizon of years. Steering happens at the cadence of a quarter, which is what the strategy execution steering model sits between them to provide.
What this looks like in practice
Take an industrial manufacturer moving from equipment sales toward service revenue, which is the most common strategy map in this sector right now.
The financial box says service revenue reaches 30% of total revenue. The customer box says existing accounts treat the service contract as their default rather than an add-on at renewal. The process box says field service response time drops below four hours in the top three markets. The capability box says technicians are trained and equipped for remote diagnostics.
Four boxes, three arrows, and every arrow is arguable. Does response time actually drive contract attachment, or does contract attachment depend on how the sales team prices the bundle? The map asserts the first. So the organization measures response time weekly, measures attachment rate at renewal, and books a review at the end of the cycle to compare them. If response time halves and attachment does not move, the arrow was wrong and the next map should point somewhere else. That is a year of strategic learning available to anyone willing to write the prediction down first.
The same discipline is what separates a real outcome from a delivered output. A shorter response time is an output. A customer changing their renewal behavior is an outcome. The gap between them is where most strategy execution quietly fails, and it is worth being precise about the difference between outcome and impact before you commit a map to it.
Frequently asked questions
What is the difference between a strategy map and a balanced scorecard?
The balanced scorecard is the set of objectives and measures across four perspectives. The strategy map is the diagram that shows how those objectives cause one another. The scorecard tells you what you are tracking. The map tells you why you believe tracking those things together makes sense.
How many objectives should a strategy map have?
ClearPoint's analysis of more than 20,000 plans found the workable range is roughly five to nine strategic goals with nine to eleven measures. Beyond that, attention fragments and no single arrow gets enough scrutiny to be tested. If your map has thirty boxes, it is a list of everything the organization does rather than a statement of how it intends to win.
Who owns the strategy map?
The executive team owns the map as a whole, since the arrows encode strategic choices only they can make. Each individual box and each measure needs its own named owner who can influence it. A map owned collectively and by no one in particular is the pattern that produces the unassigned-measure numbers above.
Can a strategy map replace OKRs?
No, and it is not trying to. A strategy map describes a multi-year causal theory. OKRs commit a team to testing one part of it in the next quarter with measurable Key Results. Organizations that already run a scorecard usually find OKRs easier to introduce as the execution layer under the map than as a replacement for it.
How often should a strategy map change?
The picture should be stable for two to three years, because a causal theory you redraw every January was never a theory. What changes quarterly is which arrows you are actively testing and what the measures say. A box or an arrow should change when evidence says it is wrong, not because it is planning season.
If you are redrawing yours for the coming year, the useful question is not whether the picture is right. It is which arrow you would notice being wrong, and when.
