Overview
The Balanced Scorecard was developed by Robert S. Kaplan (Harvard Business School) and David P. Norton (founder of Nolan Norton Institute), first published in their January–February 1992 Harvard Business Review article "The Balanced Scorecard — Measures That Drive Performance." The foundational book, The Balanced Scorecard: Translating Strategy into Action, followed in 1996 (Harvard Business School Press).
The framework emerged from a 1990 research study in which Kaplan and Norton found that organizations were over-relying on financial measures — lagging indicators that tell you what happened, not what's about to happen. A business could look healthy on financial measures while quietly eroding its competitive position through underinvestment in customers, processes, and people.
The four perspectives, with their causal relationship made explicit:
- Financial — how do we look to shareholders? Revenue growth, profitability, return on capital, cash flow. The lagging outcomes that financial stakeholders care about.
- Customer — how do customers see us? Market share, customer satisfaction, retention, net promoter score, on-time delivery. A leading indicator for future financial performance.
- Internal Business Process — what must we excel at? Cycle time, quality, throughput, innovation rate. The processes that create customer value.
- Learning & Growth — can we continue to improve? Employee skills, information systems, organizational culture, employee satisfaction. The foundation that enables everything above it.
The causal logic runs bottom-up: investments in Learning & Growth improve Internal Processes; better processes drive Customer outcomes; satisfied customers produce Financial results. The Scorecard makes this causal chain visible and measurable.
Kaplan and Norton later introduced the Strategy Map — a visual cause-and-effect diagram across the four perspectives — in their 2000 HBR article "Having Trouble with Your Strategy? Then Map It." The Strategy Map became as important as the Scorecard itself for communicating why the organization's strategic choices make sense.
When to Use It
When a client needs to translate strategy into measurable execution — particularly in large, complex organizations where strategy easily becomes disconnected from day-to-day operations. The Balanced Scorecard is most powerful as an organizational alignment tool: it forces leadership to agree on what matters in each perspective and holds them accountable. Also useful for strategy review conversations: looking at all four perspectives together tells a story that financial reports alone cannot.
How It Works
- Clarify the strategy — the Scorecard translates strategy into measures; if the strategy is unclear, the Scorecard will be too. Start with a clear strategic hypothesis about how the organization creates value.
- Develop objectives in each perspective — for each of the four perspectives, identify 3–5 strategic objectives: specific outcomes the organization needs to achieve to execute the strategy.
- Define measures — for each objective, identify 1–2 indicators of progress. Measures should be concrete, quantifiable, and within the organization's influence.
- Set targets — for each measure, what level of performance would indicate success? Targets should be ambitious but grounded.
- Define initiatives — what specific programs or projects will drive performance against each objective? This is where the Scorecard connects to actual resource allocation.
- Build the Strategy Map — draw the cause-and-effect relationships across perspectives. Which Learning & Growth objectives enable which Internal Process improvements? Which process improvements drive which Customer outcomes?
- Cascade — develop Scorecards at business unit, department, and team levels that align with the organization-level Scorecard.
Running It in a Session
The Balanced Scorecard is most useful in sessions where the client's problem is strategy execution — "we have a strategy but it isn't translating into results" or "our metrics are all financial and we can't see what's coming." Use the four perspectives as a diagnostic structure: which perspective is underperforming? Is the financial problem a symptom of a customer problem, which is a symptom of a process problem, which is rooted in a capability gap?
That causal chain often points directly to the root cause and the highest-leverage intervention — and it shifts the recommendation from "improve financial performance" to something the client can actually act on.
Common Pitfalls
- Measure proliferation — 40+ metrics across four perspectives creates a reporting system, not a strategic management tool; a usable Scorecard has 20–25 measures at most
- Financial dominance — despite the framework's intent, Financial measures crowd out the others in most review conversations; push back when the discussion drifts entirely to lagging indicators
- Metrics without owners — every measure needs a person accountable for it; a Scorecard without ownership is just a dashboard
- Ignoring the causal logic — selecting measures in each perspective without building the cause-and-effect Story Map misses the framework's core value
- Confusing it with a KPI dashboard — the Balanced Scorecard is a strategic management system built around a theory of value creation; a KPI dashboard is just a collection of metrics
References & Further Reading
- Kaplan, Robert S. and Norton, David P. "The Balanced Scorecard — Measures That Drive Performance." Harvard Business Review (January–February 1992)
- Kaplan, Robert S. and Norton, David P. The Balanced Scorecard: Translating Strategy into Action (1996, Harvard Business School Press)
- Kaplan, Robert S. and Norton, David P. "Having Trouble with Your Strategy? Then Map It." Harvard Business Review (September–October 2000)
Recommended Books
- The Balanced Scorecard — Kaplan & Norton
- Strategy Maps — Kaplan & Norton
- Execution — Larry Bossidy & Ram Charan