Staying Lean Is Not Free
Many businesses try to stay lean. It’s good business philosophy, repeated so often it’s stopped being examined.
But “lean” is not one decision. It’s a label we put on four or five different decisions, and we rarely stop to ask which one we’re actually making.
Is it keeping overheads low? Is it squeezing more out of the staff you have rather than hiring? Is it doing everything in-house instead of bringing in outside help? Is it holding off on investing in technology, process improvement, or innovation because the current setup still just about works?
All four get filed under the same word — lean — as if they carry the same risk. They don’t. Each one is a different trade, with a different bill, arriving at a different time.
Here’s the pattern I keep seeing across programs and organisations: the cost of running lean is almost never visible at the point you decide to run lean. It shows up later, in a different budget line, often attributed to a different cause entirely.
A council keeps its project team at three people instead of five to save on headcount. For eighteen months, nothing goes wrong. Then the one person who understood how three systems talk to each other resigns. The organisation doesn’t call it “the cost of running lean.” It calls it “a difficult transition period.” Same bill, different name.
A mid-sized organisation decides not to bring in outside specialists during an ERP configuration, to save the consulting fee. The in-house team does its best, learns as it goes, and ships something that works — for now. Two years later, the workarounds have compounded into a system nobody fully trusts, and the rebuild costs four times what the specialist would have charged upfront. Nobody frames this as the lean decision maturing. It gets framed as “the system never quite worked properly.”
A business defers the process automation project for another year because the manual version still gets the job done. Three deferrals later, the manual version is the only version anyone remembers how to run, the person who runs it is the only one who can, and “we’ll automate this properly next year” has quietly become permanent. The cost didn’t disappear when it was deferred. It was accruing interest the whole time.
Why the trade-off stays hidden
None of this is dishonesty. It’s structural. At the moment you decide to stay lean, the trade-off hasn’t happened yet — it’s a future condition, not a current one. The status report stays green because there’s nothing yet to flag. The saving is immediate and countable. The cost is deferred and, until it lands, uncountable. Anyone comparing the two at decision time will always see lean winning, because only one side of the ledger has numbers on it yet.
This is exactly why staying lean is so easy to defend and so easy to over-apply. It looks like discipline in the moment it’s chosen and only reveals itself as a gamble in the moment it’s paid for.
What actually needs deciding
None of this is an argument against running lean. Low overheads, a small team doing more, capability built in-house, deferred spend on tooling — these can be exactly right. Staying lean and staying safe are not opposites.
But “we run lean” is not a decision. It’s a slogan that’s hiding several decisions you haven’t actually made. The real work is naming, for each of the four questions above, where you are genuinely choosing to run lean, and where you are simply avoiding the conversation about what it will cost you later and who will be paying it.
So the question worth sitting with isn’t whether to stay lean. It’s this: where, specifically, are you running lean right now — and have you actually named the price, or just postponed the invoice?
