The cost discipline framework
Cost work becomes effective when it is tied to the operating model instead of one-off budget cuts. A short framework for cost programs that survive the quarter.
Where the work starts
Real cost discipline depends on visibility, ownership and a clear view of what the business actually needs to keep doing.
Without those pieces, cost work becomes cosmetic. The numbers look good on one quarter's board deck and quietly snap back the next. Every cost program that sticks is, at heart, an operating-model change with a cost narrative on top.
The four cost lenses
We look at every cost base through four lenses in sequence. Volume — are we doing too much of this thing, regardless of unit cost? Unit cost — are we paying too much per unit of output? Mix — are the wrong activities taking the most expensive capacity? Timing — are we paying for capacity that sits idle between peaks?
Most cost programs we review have focused on one lens — usually unit cost — and missed the structural opportunity. The compounding savings live where two lenses intersect, not where one is maximized.
Cost work that lasts vs. cost work that snaps back
The test is simple: after the cost saving is booked, does anyone need to do anything differently every day? If no, the cost is structural — it will stay saved. If yes, the cost will come back the moment attention moves.
Headcount freezes snap back. Tooling rationalisations snap back when a new tool gets bought. Process redesigns with explicit new workflows tend to stick because the old workflow is physically not there anymore to default to.
Why most cost programs fail at the handoff
The failure pattern is almost always the same: the consultancy leaves, the new process lives in a PowerPoint, and within two quarters the business has drifted back. The consultancy calls it 'change-management failure'. The client calls it 'another expensive slide deck'.
The only reliable prevention is a handover protocol written into the SOW from day one. The runbook has to live where the team actually works — not in a shared drive nobody opens. The first thirty days after the engagement are where the cost saving is either made real or quietly abandoned.
More from the field notes
The AI pilot blueprint
The shape of an AI pilot decides its fate before anyone writes a prompt. Here is the engagement we run — phase by phase — and why every slot is engineered to close on a handover, not to keep the advisor in the room.
Read moreWhy AI projects fail at the process layer
A useful AI initiative still collapses if the underlying process is unclear, expensive or fragmented. The model gets blamed — but the process was the failure point all along.
Read morePrioritizing AI use cases without the hype
The right use case is the one that fits the operating model and creates leverage the business can own — not the one that makes the best demo. A field-tested filter for the shortlist.
Read more