Balanced scorecard: four perspectives, and why three get ignored

The balanced scorecard is a framework for measuring a business from four perspectives at once — financial, customer, internal process, and learning and growth — instead of from financial results alone. Kaplan and Norton introduced it in the early nineties, on a simple premise: financial figures report the consequences of decisions taken months earlier, so managing by them alone means steering by the rear window.

It has since acquired a reputation as heavy corporate machinery, deservedly in some cases. But the core exercise is worth doing at any size, and it takes an afternoon: state what has to be true in each of the four areas for the financial result to arrive, and then measure those things.

What a balanced scorecard measures

• Financial: revenue, margin, cash — how the results look to owners. Lagging by nature.
• Customer: satisfaction, retention, share of a target segment, whether customers would recommend you.
• Internal process: the operations that produce the customer outcome — delivery times, defect rates, rework, capacity used.
• Learning and growth: the capability behind the processes — skills, tools, information, culture, staff retention.

The four perspectives are meant to form a causal chain, and that is the part most implementations discard. Better capability produces better processes; better processes produce better customer outcomes; better customer outcomes produce financial results. If your scorecard cannot show that chain, it is four unrelated lists sharing a page.

Why the financial column dominates anyway

In practice, most scorecards collapse back into financial reporting with three decorative columns. The reasons are structural rather than lazy: financial numbers are precise, available monthly and tied to pay, while learning and growth measures are soft, slow-moving and easy to postpone. Under pressure, attention goes to the column with consequences attached.

The counter-measure is unglamorous — give the non-financial perspectives the same standing as the financial one. An owner, a target, a place on the agenda before the financial section, and a genuine conversation when they move the wrong way. Where an organisation is unwilling to do that, the honest response is to keep a shorter scorecard rather than maintain three columns nobody acts on.

Building one for a small company

1. Write the strategic objective in one sentence — the thing the scorecard exists to advance.
2. For each perspective, ask what must be true for that objective to be reached. One or two answers each.
3. Choose one or two measures per perspective. Eight measures total is plenty; twenty is a project nobody finishes.
4. For each measure, state the target and the person accountable.
5. Draw the causal chain explicitly: this capability enables this process, which improves this customer outcome, which produces this result.
6. Review quarterly rather than monthly — the non-financial measures move too slowly for a monthly cycle to be informative.
7. At each review, ask whether the assumed causal links are actually holding.
8. Drop measures that have never changed a decision.

Strategy map, scorecard, dashboard

Three related things worth keeping apart. The strategy map is the diagram of causal links between objectives. The balanced scorecard adds measures, targets and initiatives to those objectives. A KPI dashboard is a display of current numbers, which may or may not have any strategic logic behind it. The dashboard is the easiest to build and the emptiest without the reasoning the other two supply.

A small company reasonably starts at the scorecard and skips the formal map, as long as the causal chain gets written down somewhere, even as a sentence per link.

Confusing the two is common enough to be worth settling explicitly. OKR vs KPI comes down to ambition against measurement: one sets a target somebody has to stretch for, the other tracks whether an ongoing process stays healthy.

Where it lives

Ettex Board suits the part that determines whether a scorecard does anything: the initiatives. Each objective gets its improvement work as cards with owners and dates, so a target for customer retention is attached to the work meant to move it rather than sitting as a number that gets discussed quarterly and never acted on.

There is no scorecard view: no four-perspective layout, no strategy map, no cascading of objectives down an organisation, and no automatic roll-up of measures to a parent objective. The measures themselves belong in a sheet or a report; what belongs on a board is the work.

One objective, two measures per perspective, the causal chain written down — and the non-financial perspectives discussed before the financial one, or not kept at all.