Balanced Scorecard

The framework's argument is straightforward. Financial results describe what already happened. By the time they deteriorate, the causes have been operating for some time, and the measures that would have shown those causes earlier sit in the other three perspectives.

So the four are not a balanced set of report tabs. They are meant to be a chain: capability enables process, process delivers to customers, customers produce financial results. A scorecard whose perspectives have no causal relationship to each other has kept the format and discarded the idea.

The learning and growth perspective is the one HR most often owns, and it is the one most often filled with whatever was easy to count.

Training hours delivered, courses completed, headcount, and satisfaction scores appear routinely. None of them measures whether the organisation is more capable than it was, which is the question the perspective exists to answer.

• Capability against what the strategy actually requires, rather than training volume.
• Retention of the specific skills the organisation would struggle to replace, rather than overall attrition.
• Internal fill rate for critical roles, which measures whether capability is being built rather than bought.
• Time for a new joiner in a key role to reach competence, which is a capability measure disguised as an onboarding one.
• Whether people can actually get the information needed to do the work, which is the systems half of the perspective and is almost always omitted.

The test for any candidate measure is whether a change in it would plausibly move something in the internal process perspective. If it would not, it belongs in an HR report rather than on the scorecard.

Three failure modes account for most disappointing implementations.

The first is measure proliferation. A scorecard is a strategy statement, and the discipline is subtraction. Once it carries thirty measures it has stopped saying what matters and become a dashboard, which is a different and less useful object.

The second is the missing causal logic. Where nobody can articulate why a learning measure is expected to affect a process measure, the perspectives operate independently and the framework provides structure without insight.

The third is cascading. The scorecard is designed for an organisation or a unit. Pushed down to individuals, it produces personal scorecards containing measures the individual cannot influence, which is demotivating and generates gaming rather than alignment.

A junior employee held to a margin measure will either ignore it or find a way to appear to have moved it. Neither is what was intended.

• Fix a small number of measures per perspective, and treat adding one as requiring the removal of another.
• Write down the causal claim linking the perspectives, then check it periodically against what actually happened.
• Cascade the strategy rather than the scorecard, so a team knows what it contributes without inheriting measures it cannot move.
• Review measures annually and retire ones that never changed a decision.
• Keep the reporting cadence slower than the operational one, since a strategic measure read weekly invites reaction to noise.

The fourth point is the most neglected. Measures accumulate because removing one feels like admitting it was never useful, so scorecards grow monotonically until nobody reads them.