Home > Perspectives > Performance > Why Performance Management Systems Age Faster Than Organisations Realise

Why Performance Management Systems Age Faster Than Organisations Realise

Watch the short film

Play Video
Why performance management systems age faster than organisations realise: how growth phases outpace the systems built for an earlier stage.

The observation

Larry Greiner’s research on organisational growth, published in Harvard Business Review and reissued as an HBR Classic, describes an organisation’s evolution as a series of phases, each resolved by a specific set of practices that become, in the next phase, the constraint that has to be overcome. Greiner’s own framing of this is memorable: managers “experience the irony of seeing a major solution in one period become a major problem in a later period.” A performance management system — the criteria used to assess people, the cadence of review, the definitions of what good performance looks like in a given role — is exactly this kind of solution. It is designed to fit an organisation as it exists at a specific moment, and it does not automatically update itself as the organisation moves through subsequent phases.

The practical consequence is that performance management systems tend to age in a specific and predictable way: they remain formally unchanged, because changing a performance system is administratively significant and rarely urgent enough to prioritise ahead of more immediate demands, while the organisation around them keeps evolving. The system does not become wrong all at once. It becomes progressively less well matched to the organisation it is actually assessing, quietly, year by year, until the mismatch has grown large enough to produce visible symptoms — at which point it is usually diagnosed as a performance problem in the people being assessed, rather than what it more often is: a measurement problem in the system doing the assessing.

Why it happens

Two mechanisms drive this pattern, and they reinforce each other. The first is Greiner’s core finding: organisational structure and practice have to evolve through recognisable phases as an organisation grows, and each phase’s appropriate practices differ meaningfully from the last. A performance system built for a smaller, less formalised organisation — one where roles were fluid, responsibilities overlapped by necessity, and informal judgement substituted for defined criteria — is simply answering a different question than the one a larger, more structured organisation needs answered. Neither version of the system is wrong for the organisation it was built for. The mismatch appears only because the organisation moved and the system, absent a deliberate decision to move it too, stayed where it was designed.

The second mechanism is closer to organisational inertia than to any specific growth dynamic. Formal systems — performance management chief among them — carry real switching costs: redesigning criteria, retraining managers, communicating a change to an entire workforce, and living through the inevitable disruption of a transition period. These costs are visible and immediate. The cost of leaving an aging system in place is, by contrast, diffuse and gradual — a slightly worse fit here, a slightly less relevant criterion there, none of it individually significant enough to justify the disruption of a redesign. This asymmetry means an aging system tends to persist well past the point where it stopped being the best available fit, simply because no single moment ever makes the case for changing it more compellingly than the case for leaving well enough alone.

What it looks like in practice

Consider an organisation whose performance management system was designed several years ago, when the organisation was smaller and its roles were somewhat less specialised than they have since become. The system’s criteria for what constitutes strong performance in a given role were reasonable and well-matched at the time they were written. Since then, the organisation has added new specialisations, redefined several roles to be narrower and more focused than their earlier, more generalist equivalents, and introduced a layer of management that did not previously exist. The performance system, formally, has not changed.

Managers using the system increasingly find themselves interpreting or adapting its criteria informally to fit roles the criteria were never actually written to describe — a reasonable, well-intentioned workaround that nonetheless means the organisation no longer has a single, consistent standard being applied, even though the formal document suggests that it does. Employees, meanwhile, are assessed against criteria that describe, with decreasing accuracy, a version of their role that existed several reorganisations ago. None of this is usually visible from the system itself, because the system’s own documentation has not changed and therefore does not flag its own growing distance from the organisation it describes.

This pattern is easy to miss specifically because performance management systems are rarely reviewed on a schedule tied to organisational change — they are typically reviewed on a schedule tied to administrative convenience, such as an annual cycle, regardless of how much the organisation itself has actually moved in that period. An organisation that grew or restructured significantly in a given year and one that changed very little both proceed, by default, to the same annual review of their performance system, which means the system’s currency is essentially decoupled from the thing that should actually determine it.

The mismatch is often first noticed, if it is noticed at all, by people relatively new to the organisation rather than by those who have been there throughout the gradual drift. Someone who joined recently, and who is assessed against criteria written for an earlier version of a role they never actually held, has no accumulated familiarity with the system’s history to explain away the mismatch — where a longer-tenured employee or manager may have simply absorbed the informal adaptations over time without registering how far the formal system has drifted from what it describes.

Looking for your own sector? The Other Sectors page points to the closest match.

Questions worth considering

  1. When was this organisation’s performance management system last reviewed specifically against how much the organisation’s roles and structure have changed, as opposed to on a fixed administrative schedule?
  2. Are managers currently applying the formal system as written, or informally adapting it to fit roles it was not originally designed to describe?
  3. If a new performance system were being designed today, from scratch, for the organisation as it currently exists, how different would it look from the one currently in use?

This perspective is part of Performance.

Your team is facing similar challenges?

Evidence Without Assurance — performance management system
The Riddle Ledger, a brand of Zoom Riddle

Subscribe to The Riddle Ledger

Perspectives are sent as they are published, with no promotional email, and you can unsubscribe at any time.

Sources

Larry E. Greiner, “Evolution and Revolution as Organizations Grow,” Harvard Business Review, Vol. 50, No. 4 (July–August 1972), pp. 37–46; republished as an HBR Classic, Vol. 76, No. 3 (May–June 1998).

You need a PDF version for a meeting?

Frequently Asked Questions

The research does not point to a fixed interval; the more relevant trigger is the degree of organisational change since the system was last matched to it, rather than a calendar date.
Not usually — the mismatch tends to grow gradually and is often absorbed through informal manager adaptation before it becomes visible as a formal problem, which is part of why it persists for as long as it does.
Not necessarily — frequent redesign carries its own real disruption cost. The more useful practice suggested by the research is periodically checking the system’s fit against how much the organisation has actually changed, rather than defaulting to either extreme of constant redesign or indefinite inertia.
The page points to switching costs and inertia. Redesigning criteria, retraining managers and communicating change are visible and immediate costs, while the cost of an ageing system is diffuse and gradual. Systems are also typically reviewed on an administrative schedule rather than one tied to organisational change, so no single moment makes the case for changing them.
Greiner observed that managers experience the irony of seeing a major solution in one period become a major problem in a later one. The page treats a performance system as that kind of solution: designed to fit an organisation at a moment, and not updating itself as the organisation moves through later phases. Neither version is wrong for the organisation it was built for.
The page says the mismatch grows progressively, year by year, until it produces visible symptoms. At that point it is usually interpreted as a performance problem in the people being assessed, rather than what it more often is: a measurement problem in the system doing the assessing.
The page suggests people relatively new to the organisation are often the earliest to notice. Someone assessed against criteria written for an earlier version of a role they did not hold has no accumulated familiarity to explain the mismatch away, whereas longer-tenured staff may have absorbed informal adaptations without registering how far the formal system has drifted.
The page describes it as a reasonable, well-intentioned workaround, but one that means the organisation no longer applies a single consistent standard even though the formal document suggests it does. Because the documentation itself has not changed, the system does not flag its own growing distance from the organisation it describes.