Measure the Function, Not Just the Outcome

Every health system measures something. Dashboards proliferate, scorecards multiply, and quarterly reports grow thicker. Yet leaders keep asking the same uneasy question: is the organization actually performing, or are we simply counting?

The performance-measurement era in health care is now three decades deep. The Balanced Scorecard, introduced by Kaplan and Norton in 1992, broke the assumption that financial numbers alone capture performance — pairing them with measures of customer experience, internal process, and organizational learning. A substantial body of peer-reviewed work has since adapted the model to hospitals, public-health agencies, and provider networks, and the consistent finding is telling: the scorecard's real value lies less in the metrics themselves than in the accountability structure it creates — strategy maps that let an organization assign responsibility for performance at every level.^[1]

The trap most measurement programs fall into

Adopting a framework is not the same as measuring the right thing. The most common failure we see is an organization that measures the outcome of a program and never measures the function that produces it. A clinic reports its diabetes outcomes and concludes the program "works." Yet that same program may be delivering those results at an unsustainable cost, or through an unstandardized process that cannot be repeated, audited, or scaled. By the logic of outcomes alone, it passes. By the logic of a system, it is fragile.

"A program can deliver results and still be failing — at far too high a cost, or without a standardized process underneath."

Why function comes first

Evaluating function before outcomes is not bureaucratic caution; it is how accountability becomes real. When you can describe how a program is supposed to operate — its delivery standards, its decision points, its data — you can tell whether a disappointing result reflects a broken design or simply a hard problem. You can also cascade that clarity. A KPI that lives only in a board report changes nothing; a KPI that traces from governance mandate down to a frontline team's daily work changes behavior. That cascade — mandate to measure to frontline action — is the difference between a reporting habit and an accountability system.

What it looks like in practice

Consider a provincial primary-care system asked to prove it is delivering value. The instinct is to publish outcome dashboards. The more durable move starts a level higher: assess the governance models and mandates first — who is accountable for delivering what — then map those mandates down into the operational and evaluation models that distribute responsibility across organizations. Only then do outcome measures carry weight, because each one now has an owner and a process behind it. That sequence — governance, to operations, to evaluation — is how a system proves it works rather than merely asserting it.

This discipline also guards against the two failure modes that quietly defeat most measurement programs. The first is the vanity metric: a number that looks impressive on a slide but drives no decision and changes no behavior. The second, more corrosive, is measurement without accountability — data dutifully collected while no one owns the result it implies. A scorecard that cannot answer a simple question — who acts on this, and how? — is decoration. A genuine accountability system can always answer it, at every level, from the board's mandate to the team delivering care on Monday morning.

The organizations that improve durably are not the ones with the most metrics. They are the ones whose measures connect to mandates, whose mandates connect to the work, and who can prove — not assume — that the function beneath their outcomes is sound. That is the system Sage builds.