How to build a balanced scorecard (without twenty-eight objectives)

The balanced scorecard is the most widely adopted framework in the public sector and among regulated organizations, because it forces performance to be described in more than one dimension. It is also the framework most often implemented badly — as four buckets to fill rather than a chain of cause and effect.

The four perspectives

• Financial — sustainability and stewardship. For governments and nonprofits, read this as fiscal health rather than profit.
• Customer / stakeholder — residents, clients, patients, students, members.
• Internal process — the operations that deliver for those stakeholders.
• Learning and growth — people, skills, culture, systems, data.

Step 1: write the strategic story first, in one paragraph

Before any objectives, write: *if we invest in these capabilities, our processes improve in these ways, which gives stakeholders this outcome, which produces this financial result.* That paragraph is your causal logic, and every objective you add later must sit somewhere in it.

Organizations that skip this step end up with twenty-eight objectives and no explanation of how any of them affect each other.

Step 2: cap the objective set

Eight to twelve objectives total across all four perspectives. Typically two to three financial, two to three stakeholder, three to four process, two to three learning and growth.

Each objective is a short outcome phrase — "reduce time to resolve service requests", "build data capability in every department" — with one accountable owner.

Step 3: draw the strategy map

Place the objectives in four horizontal bands, learning and growth at the bottom, financial at the top, and draw arrows only where you genuinely believe one objective drives another. Two rules:

• Every objective needs at least one arrow in or out. An isolated objective is not part of the strategy.
• If you cannot defend an arrow in a sentence, delete it.

The map is the single most useful artifact for board and council communication, because it explains *why* the plan is the plan.

Step 4: attach measures

One to two measures per objective. For each: definition with exclusions, unit and direction, source system, owner, update frequency, baseline, target. Twelve objectives with two measures each is twenty-four measures — that is the upper bound of what an organization can genuinely maintain.

See how to choose KPIs for the selection test, and KPI vs metric vs OKR for what belongs in the measure library instead.

Step 5: attach initiatives, with money

Objectives do not move on their own. Each objective gets zero or more initiatives, each with an owner, dates and a cost figure. Then run two checks:

• Coverage: any objective with no initiative is an aspiration.
• Load: any initiative serving five objectives is probably several initiatives.

Step 6: set the review rhythm

Measures monthly, objectives quarterly, map and objective set annually. The scorecard's failure mode is becoming a reporting template that is completed and filed; the quarterly decision requirement is what prevents it. See the quarterly review agenda.

Where scorecards go wrong

• Bucket filling. Objectives written to populate four perspectives evenly rather than to express a strategy.
• Measure inflation. Fifty measures, so nobody maintains any of them properly.
• No arrows. The map becomes a layout, and the "balanced" idea reduces to a colour scheme.
• Annual-only review. A scorecard reviewed once a year is a report card, not a management system.
• Separate reporting stack. If the public or board scorecard is rebuilt by hand from the working data, it will be out of date, and the version people see will not be the version management uses. Keep the measures in one place and treat the scorecard view as a rendering of them.

Public sector note

Cities, counties, health systems and universities usually publish the scorecard structure and manage the initiatives underneath it. If you are heading toward publication, define every measure precisely first — a published measure with an ambiguous definition invites a challenge you cannot answer. See strategic planning for city governments.