Strategy Map: Draw the Line From Strategy to Every Department

A strategy map is a one-page diagram that shows how a company's objectives depend on each other: what it must learn and build, which processes it must run well, what customers must experience as a result, and the financial outcome that follows. Robert Kaplan and David Norton introduced it as the companion to their balanced scorecard. This article explains the original, then a simpler version that ends where most strategy maps stop short: an owned KPI for every department.

The appeal of a strategy map is that it turns a strategy document, usually pages of prose, into a picture people can argue with. The weakness of most strategy maps is that the picture ends at the objectives. Nobody's name is on it, and no department can find itself on the page.

What a strategy map is

Kaplan and Norton's balanced scorecard asked companies to measure performance from four perspectives, not just the financial one, on the reasoning that financial results report the past while the other three explain what will produce the future. The strategy map came later, as a way to show why those measures belong together. It places objectives in the four perspectives and draws arrows between them to show cause and effect.

Read a strategy map from the bottom up. Better skills and systems make better processes possible. Better processes produce a better experience for customers. A better experience for customers produces the financial result. Each arrow is a hypothesis: "if we do this, that will follow." The map is useful precisely because those hypotheses are written down where they can be tested.

The four balanced scorecard perspectives

Public-sector and nonprofit organizations often move the customer or mission perspective to the top, since financial results are a constraint rather than the goal. The structure still works.

Why most strategy maps stall

The method is sound. The way it is usually done is where things go wrong.

The map stops at objectives. "Deliver on time, every time" is a good objective. It is not a measure, it has no baseline, and nobody is accountable for it. Without the next step, the map is a poster.

Perspectives are not departments. "Internal process" is not a team anybody works in. A head of Operations looking at the map has to work out for herself which boxes are hers, and two department heads can each assume a box belongs to the other.

It is built once, by a few people. A strategy map drawn by the leadership team, or by consultants, in a single offsite, rarely survives contact with the departments that have to deliver it. They were not there for the arguments, so they do not trust the arrows.

It has too many boxes. Twenty-five objectives across four perspectives is a map of everything the company does, not of its strategy. A useful map has room to breathe.

A simpler strategy map that ends in owned KPIs

Keep the four layers and the bottom-up logic, and add the two things the classic map leaves out: a department owner for each objective and a KPI for each owner.

Build it with four plain questions, in order:

1. Where are we now? Today's numbers for the results that matter: revenue, retention, margin, delivery, whatever the business lives by.
2. Where are we going? The financial and customer outcomes the strategy is aiming at. These form the top two rows of the map.
3. What could affect us? The risks and constraints that decide which processes and capabilities matter most. These shape the bottom two rows.
4. What must we deliver? For every objective on the map, the department that owns it and the KPI that shows whether it is happening, with a baseline, a target and one named person.

Then apply three rules:

• No more than three objectives per row. Twelve boxes in total is a ceiling, not a goal.
• Every arrow must be explainable in one sentence. If you cannot say how one box causes the next, remove the arrow.
• Every box in the bottom two rows has a department. If a box has no owner, either it does not matter or the organization chart has a gap. Both are worth knowing.

The KPIs themselves should be written with the method in how to create KPIs. The map's job is to show how they connect.

A worked example

A fictional 300-person regional logistics company. Its strategy: grow revenue from existing business customers by becoming the carrier they never have to chase.

FINANCIAL        Grow revenue from existing customers ── Hold gross margin
                          ▲                                    ▲
CUSTOMER         Customers trust our delivery dates ── Customers expand with us
                          ▲                                    ▲
PROCESS          Flag delays before they happen ── Quarterly account reviews ── Route cost control
                          ▲                                    ▲
LEARNING         Dispatch sees every order live ── Account managers trained in reviews

Each arrow reads as a sentence. If dispatch sees every order live, we can flag delays before they happen. If we flag delays early, customers trust our dates. If they trust our dates, they give us more of their volume.

Now the step most maps skip. Each box gets a department, a KPI and an owner (figures illustrative):

Nine boxes, seven owners, every department on the page. A department head can now find herself on the map, see which arrow she feeds, and see whose results depend on her.

Strategy map template

A fill-in version you can copy into a document or a whiteboard session:

STRATEGY IN ONE SENTENCE: ___________________________________________

FINANCIAL     Objective: ________________   Objective: ________________
CUSTOMER      Objective: ________________   Objective: ________________
PROCESS       Objective: ________________   Objective: ________________   Objective: ____________
LEARNING      Objective: ________________   Objective: ________________

FOR EVERY OBJECTIVE ABOVE:
  Department: __________   KPI: ______________________
  Baseline: ____   Target: ____   Owner (one person): __________
  Arrow: "If we do this, then ____________________ follows."

Fill it top-down (results first, then what produces them), then check it bottom-up by reading each arrow aloud. Arrows that sound unconvincing out loud are where the strategy is weakest.

From the map to the dashboard and the board

The worked example's table is most of a dashboard already. The top two rows become the organization KPIs the board sees each quarter; the bottom two become the leading indicators the leadership team watches monthly, and each department carries its own rows weekly. For layouts of each view, see these KPI dashboard examples, and for how the board page sits inside a full pack, the board report template.

A strategy map shows the line from strategy to departments. It does not, on its own, settle how each department agrees its share. That negotiation, where a department says what it can deliver with what it has and the plan is adjusted, is the heart of hoshin kanri, and the two methods work well together: draw the map, then use catchball to agree the KPIs on it. If you would rather do that first draft with help, our free working session is built around the same four questions.

How often to revisit the map

Redraw it once a year, as part of annual planning, and check it every quarter. The quarterly check is not "are the KPIs on target?" (the dashboard answers that) but "are the arrows still true?" If on-time delivery reached 96% and customers still did not expand, the arrow between those boxes was wrong, and the strategy needs a different bet. That is the most valuable thing a strategy map can tell you, and it only can if the boxes carry measures.

Frequently asked questions

What is the difference between a strategy map and a balanced scorecard?

The balanced scorecard is a set of measures across four perspectives: financial, customer, internal process, and learning and growth. The strategy map is the diagram that shows how the objectives behind those measures cause each other. Kaplan and Norton developed both; the map explains why the scorecard's measures belong together.

Do I need all four perspectives on a strategy map?

Usually yes, because the value of the map is in the chain from capabilities to results. Many companies rename the layers in their own words, and public-sector or nonprofit organizations often put the customer or mission layer at the top. Leaving out the bottom layer tends to hide the investments the strategy depends on.

How many objectives should a strategy map have?

Fewer than you would expect. Two or three per perspective, ten or twelve in total, is a sensible ceiling for a company of 50 to 500 people. A map with twenty-five boxes describes everything the company does rather than what the strategy is betting on.

What should a strategy map template include?

A one-sentence strategy, two or three objectives in each of the four layers, the arrows between them, and, for every objective, a department, a KPI, a baseline, a target and one named owner. The last part is what turns the map from a diagram into a plan.

How is a strategy map different from a hoshin kanri X-matrix?

Both put a strategy on one page. A strategy map shows cause and effect between objectives; an X-matrix shows which annual objectives, improvement priorities and metrics support which long-range goals, and who owns them. Many companies use the map to agree the logic and the hoshin kanri process to agree each department's commitments.