Somewhere in your last filing a sentence announces a cost savings initiative, usually with a number and a period attached. Everyone treated it as a spending commitment.
It is also a commitment about work. A cost that is going to be lower next year is a piece of work that has to be performed differently, by somebody, starting on a date. The filing names the amount and the period. It does not name the mechanism, and in most companies of this size nobody in the reporting chain is responsible for producing one.
Over the trailing twelve months, SEC full-text search returns 239 filings describing a cost savings initiative. Those are filings, not companies, so distinct issuers are fewer.
A Target Is Not A Mechanism
The target arrives at the operating level already divided. Finance allocates the figure across functions, and each function now owns a share. Three answers come back.
- Headcount. Positions are removed outright or left unfilled. This can be counted on the day it happens, which is the reason why it is always the first answer.
- Procurement. Contracts are renegotiated, vendors consolidated, discounts taken. Also countable on the day, and largely exhausted after the first cycle.
- Efficiency. The same work, done with fewer hours. This is where the remaining balance is assigned, and it is the only one of the three with no standard method behind it.
The third category is where the initiative usually stalls. It is written into the plan as a percentage rather than as a change to a specific process, because the person who owns the number does not own a way to change how the work is performed.
A saving assigned to "efficiency" with no named process change is not a plan. It is the amount by which the other two answers fell short.
Why The Cost Comes Back
Earnings targets and managerial incentives affect the stickiness of costs (Kama & Weiss, Journal of Accounting Research, 2012): when managers face incentives to avoid a loss, avoid an earnings decrease, or meet an analyst forecast, they bring forward the reduction of slack resources rather than letting it follow activity. The reported cost falls in the reporting period. Whether the work falls too, the filing does not ask. The removed hours reappear as overtime, contractors, a backlog that becomes a quality problem two quarters later. A reduction changes who does the work; it does not, by itself, change what the work is.
Where The Savings Actually Are
In a company between sixty and two hundred million dollars in revenue, the recoverable hours are rarely in the work itself. They are in the coordination around the work: finding the current version of something, asking a colleague for a status, re-entering the same values into a second system, and rebuilding a report because the source moved.
| What the savings line says | What must change to make it true |
|---|---|
| Reduce contractor spend in operations | The process stops needing a person to chase it |
| Improve shared service center productivity | The same request stops being entered twice |
| Consolidate reporting effort | The numbers come from one always-current place |
| Reduce overtime at period close | Steps that must happen in order actually do |
Each right-hand cell is a piece of software, and each one of them is small. The instinct of a leader who has lived through an enterprise system implementation is that any software answer means a year of work and a seven-figure budget, so it is refused before anyone has put a price on it. The work that sits around the enterprise system is a different size of problem entirely, and it is the size that most savings targets are actually made of.
Make The Saving Measurable Before You Claim It
A saving you cannot count is a saving you cannot report, and most process-level savings are uncountable as the process runs today. If the work happens in a spreadsheet, an email thread and a weekly meeting, there is no record of how many items were handled or how long each took. The initiative gets reported by headcount, the only measure available.
The order that works is the reverse of the usual one. Instrument the process first, so the current cost is measured, not estimated. Then change the step. Then report the difference from the same instrument, in a form somebody outside the department can check.
A process that records its own volume, timing and exceptions is a process you can say the status of without asking a person, which means the savings claim in next year's filing rests on a system's own record rather than on the assurance of a manager.
First Steps
- Take the savings figure and write the mechanism next to each part. Headcount, procurement, or a named process that changes. An amount that fits none is unallocated.
- For the largest process-change amount, ask the person who is running that process how they would count the cost today. If the answer relies on an estimate or a sample instead of a record, the saving cannot be evidenced later on either.
- Write down the single step in that process where work waits for a person. Waiting is where recoverable hours sit, and the step a small system removes most reliably.
Price The Mechanism Before The Period Ends
A published savings number has a period attached that cannot be renegotiated quietly.
A fifteen-minute call — nothing paid, nothing signed — takes one process from your savings plan apart: where the hours currently go, which of them a system can remove, what would have to be built, and what it costs. If the honest answer is that the hours are already thin and the saving is not there, that is what we will say, and you will have avoided spending against it. To size the hours before the call, run the savings estimate.
Where something has to be built, it runs as a monthly engineering partnership: one prioritized delivery lane, with the measures each release has to meet written down before it starts. After that, $10,000 a month puts one accountable person on keeping it running, with a written monthly report of what ran and what changed. That report is also the evidence your savings claim needs, produced continuously, not assembled at the end.
References
- Kama, I., & Weiss, D. Do Earnings Targets and Managerial Incentives Affect Sticky Costs? Journal of Accounting Research, 2012.
