Balanced Scorecard and Strategy Maps
The Balanced Scorecard (Kaplan and Norton, 1992) began as a needed rebellion against managing by financials alone: measure the business through four linked perspectives, because financial results are lagging echoes of decisions made lanes away and quarters earlier. Strategy Maps (2004) added the deeper idea: draw the causal chain, so the measurement system tells the story of how the strategy is supposed to work.
What it teaches, and what we carry
The causal-chain insight is the direct ancestor of metric trees and the discipline of leading and lagging indicators: measures are hypotheses about cause and effect, not a dashboard of whatever happens to be countable. Draw the map before choosing the numbers and you inherit Kaplan and Norton's best idea whether or not you ever build their scorecard. The four-perspective balance survives in translated form too: the insistence that money is a trailing signal and that capability and health deserve their own instruments is kin to the SHOP portfolio's Health lane. And their research gave the whole field its founding receipt, that roughly nine in ten strategies fail in execution, the number every system on the shelf exists to answer.
The natural hybrid
The scorecard and OKRs divide labour cleanly, because they answer different questions: the scorecard asks is the whole business healthy? while OKRs ask what are the few things we are changing right now? Run together, the strategy map and its measures become the watching layer, the KPI scorecard in richer clothing, and OKRs become the acting layer, with wildly important focus choosing the two or three places the map says intervention matters most. The KPI-to-OKR lifecycle is the join: a scorecard measure that breaks, or that strategy wants pushed to a new level, is promoted to an OKR, and returns to the scorecard with a new threshold when the work is done.
The practice drift worth watching
Kindly, because every measurement system faces it: scorecards accumulate measures the way gardens accumulate weeds. Prune on a schedule and keep ownership per measure; a number with no owner and no threshold is costing attention weekly, the hygiene covered in KPIs, metrics and measurements.
One line to keep: the scorecard watches the whole; OKRs move the part that matters now.
Credited to Robert Kaplan and David Norton (HBR 1992; Strategy Maps 2004). Machinery connections are ZOKRI methodology.
Should we replace our Balanced Scorecard with OKRs? +
No. They answer different questions: the scorecard watches whether the whole business is healthy; OKRs move the few things you are changing now. Run together, with a clean KPI-to-OKR lifecycle, they are stronger than either alone.
How do measures become OKRs? +
Two triggers: the measure is broken beyond routine fixing, or strategy wants it pushed to a new level. The OKR does the moving; the measure returns to the scorecard with a new threshold. No permanent residents.
Keep the scorecard; add the acting layer. We implement the OKR machinery and the lifecycle between them, running on your AI Business OS.