Operating Playbook: Operating-Model Efficiency

Why efficiency gains reinflate

Operating-model efficiency programs share a signature failure: the reinflation curve. Year one is strong. A team removes duplicated roles, flattens a management layer, consolidates a process, and books a real reduction in cost-to-output. Then attention moves on, and over the next eighteen months the savings leak back. A layer quietly reforms as spans of control creep down. Roles reappear one requisition at a time, each individually justified. A streamlined process accretes steps as exceptions get handled by adding a check. None of it is a decision to reverse the program; it is the absence of a discipline that would have caught the drift. The organization looks up in year two to find the cost base back near where it started and no single moment to point at.

This playbook is about the years after the win, when efficiency has to be held rather than found. The insight is that efficiency is a set of ratios, not a one-time cost number, and ratios drift silently unless something watches them. Cost-to-output, span of control, process steps per transaction, and support-to-frontline ratio all reinflate on their own gradient if no one owns them. The playbook wires those ratios into a standing review with thresholds and an owner, and adds a re-baseline discipline so that the target itself does not quietly loosen. Holding efficiency is a governance act, not an analytical one.

The reason reinflation is so hard to resist is that every individual step back is defensible. The manager who asks for one more report has a real workload argument. The requisition that rebuilds a role points to genuine backlog. The added process check prevents a real error that happened once. No one is wrong in the moment, and that is exactly why efficiency erodes: it is the sum of reasonable local decisions that no one is weighing against the aggregate ratio. The scorecard's contribution is to put the aggregate back in the room, so that the tenth reasonable requisition is seen against the span-of-control line it is quietly breaching.

Hold efficiency with a standing ratio scorecard

Convert the year-one savings into a small set of efficiency ratios, set a target and a reinflation threshold for each, and review them on a cadence with a named owner. The worked example is a services business that took cost-to-output down 14 percent in year one. The scorecard is what tells the owner, in month seven, that a ratio has started to drift before the drift becomes a year of cost.

The thresholds are the mechanism. Efficiency does not reinflate in a jump the operating review would notice; it reinflates a percent at a time, which is exactly the movement a monthly number hides and a threshold catches. When cost-to-output crosses $106, the owner acts that quarter rather than waiting for it to reach $115 and become a re-do of the original program. On this business, a full reinflation back to the $118 baseline would erase roughly $6.8 million of annual savings on 400,000 units; the scorecard's job is to make sure the drift is caught at $106 and corrected for a fraction of that, over and over, so the 14 percent holds into year three.

The re-baseline discipline is the second half of the mechanism, and the more neglected one. Without it, a target quietly becomes a ceiling: the organization treats the post-program number as good enough forever and stops looking for the next increment of efficiency that new tooling or automation makes available. An annual re-baseline, done on the record and tied to demonstrated capability gains, does two things at once. It tightens the target where real improvement has been earned, and it forces an explicit conversation about any ratio that has slipped, so drift cannot hide inside a target that was loosened without anyone deciding to loosen it.

The cadence that holds the gains

• Express the year-one savings as a small set of efficiency ratios, not a single cost number, so reinflation shows up as movement in a named metric.
• Set a reinflation threshold for every ratio, so drift triggers an action before it grows into a program-sized problem.
• Review the ratio scorecard on a fixed cadence with one named owner accountable for each ratio in the operating review.
• Re-baseline deliberately once a year, so the target tightens with genuine capability gains and does not quietly loosen as a way of hiding drift.
• Gate every new role and every new process step against the relevant ratio at approval, so reinflation is stopped at the source rather than caught after it lands.

What lets efficiency reinflate

• Booking a single cost number as the result. A number with no owner drifts invisibly. Fix: express efficiency as ratios that show movement.
• No reinflation threshold. Drift is only noticed once it is large. Fix: set a threshold per ratio that triggers action early.
• No owner per ratio. Shared accountability is no accountability. Fix: name one person answerable for each ratio in the operating review.
• Approving roles and steps without a ratio gate. Reinflation enters one justified requisition at a time. Fix: gate new roles and process steps against the ratio at approval.
• Letting the baseline loosen silently. A quietly relaxed target hides the drift it should expose. Fix: re-baseline once a year, on the record, tied to real capability gains.

To hold efficiency past year one

• Year-one savings are expressed as a small set of efficiency ratios with owners.
• Every ratio has a reinflation threshold that triggers action before the drift compounds.
• The ratio scorecard is reviewed on a fixed cadence in the operating review.
• New roles and process steps are gated against the relevant ratio at approval.
• The baseline is re-set once a year, on the record, so the target tightens rather than loosening.