6 July 2026 · Helen Beckford
The "Do Nothing" Illusion: Why Deferral Is the Most Expensive Decision Nobody's Costing
What I See Every Day: "We'll get to it when things are quieter." Things are never quieter.
If Part 1 resonated, if you recognised the language gap, where your operational project can't compete because it doesn't have a revenue number, then here's the belief I need to challenge this week: that deferring it is a neutral decision. That pushing it to next quarter means the cost stays the same. That "do nothing" means nothing happens.
It doesn't.
I worked with a mid-market business that had a technology stack review sitting on the backlog. The stack had grown organically over several years, tools adopted department by department, some through formal procurement, many put on a company card before IT knew they existed. Nobody had a complete picture of what the business owned. Duplicate subscriptions across teams. Unused licences auto-renewing monthly. Capabilities already available in existing platforms being duplicated by new purchases because nobody knew what was already there.
The item got raised. It got acknowledged as sensible. And every quarter, it got pushed, because a commercial initiative with a revenue number took its place.
Here's what I watched happen while that audit sat on the backlog: every other project I worked on was affected by the gap it would have filled. Integration decisions made without knowing what the business already owned. Budget approved for tools that duplicated existing capabilities. Technical debt accumulating because workarounds were built on top of a stack nobody fully understood.
There was no single failure point. No alarm. The cost was invisible, spread across every other decision being made without the full picture. And with every quarter of growth, the eventual project got larger. More tools adopted. More contracts signed. More entrenched workflows to unpick.
That's the "do nothing" illusion. Deferral doesn't pause the cost. It compounds it.
What Needs to Happen: Stop treating deferral as a zero-cost option
I posted about this on LinkedIn last week, the "do nothing" field in most business cases is one line. But the problem goes deeper than a poorly filled field. The problem is what that empty field allows: a belief that deferral is free.
It isn't. And the cost compounds in three ways I see often:
Cost compounds. Duplicate spend continues. Unused licences renew. Manual workarounds consume team hours month after month. The number gets larger every quarter, you just don't see it because nobody's tracking the cumulative total.
Complexity compounds. The eventual project grows in scope. More data to migrate. More integrations to unpick. More teams with entrenched habits to transition. What would have taken 6 weeks a year ago now takes 12, not because the methodology changed, but because the problem grew while you waited.
Decision quality compounds. Every investment decision made without the full picture carries a risk of being wrong. Not because the evaluation was poor, but because the decision-maker didn't have the information they needed. Those blind decisions stack up.
When a leadership team sees that deferral doesn't just delay value but actively increases the eventual cost, the question shifts from "can this wait?" to "can we afford to wait?"
A necessary caveat. Articulating the cost of inaction doesn't mean the deferred project always wins. The revenue initiative might still be the right priority. But the decision should be informed and deliberate, not a default to whichever project showed up with a number attached. And sometimes, when you calculate the cost of deferral honestly, the answer is "it's manageable, this can genuinely wait." That's a legitimate, valuable outcome. You've parked it with confidence, not neglect. The point isn't to make everything sound urgent. It's to make the full picture visible so leadership teams can make the call with both eyes open.
Tip of the Week: Calculate the 12-month cost of your most deferred project
Pick the one item on your backlog that's been pushed at least twice. Then answer three questions:
What is the monthly cost of not doing it? This could be team hours consumed by workarounds, duplicate spend continuing, errors requiring correction, or risk exposure growing. Even a rough estimate works.
Multiply by 12. A monthly cost sounds manageable. The annual total rarely does. £2K per month in duplicate subscriptions is £24K in a year. 15 hours per month in manual processing is 180 hours, over four working weeks of someone's year.
What's changed since the first time it was deferred? Has the scope grown? Has the problem expanded? Is the eventual project now harder or more expensive than it would have been the first time it was raised?
If the answer to that last question is yes, you're not just deferring value. You're actively paying for the delay. Make that number visible before your next prioritisation conversation.
Bonus: Use this AI prompt to draft your cost of inaction statement in under 10 minutes.
Copy and paste the below into ChatGPT, Claude, or your AI tool of choice. Replace the bracketed sections with your project details:
Context: I have a project that has been deferred [X] times over [timeframe]. Here's what I know:
Project: [one-line description]
What it would fix: [the problem it addresses]
What's currently happening because it hasn't been done: [describe workarounds, manual processes, risks, or inefficiencies]
What it's competing against: [the type of initiatives that keep winning — e.g. commercial projects with revenue projections]
My audience: [who I need to convince — e.g. CFO, CEO, leadership team, board]
I need to build a structured risk of inaction case that competes on equal terms with revenue-driven business cases in my next prioritisation conversation.
Role: You are a senior programme governance advisor with 15+ years of experience helping mid-market leadership teams evaluate operational and infrastructure investments alongside commercial initiatives. You specialise in translating technical and operational risk into financial language that CFOs and boards act on.
Action: Run a structured working session with me. Ask questions one at a time across four areas:
The monthly cost of the current situation (in time, money, rework, or risk)
Whether that cost is flat or compounding with each quarter of deferral
What has changed since the first deferral that increases the eventual project's scope, cost, or complexity
What decisions are currently being made without the information this project would provide
If I don't have exact numbers, help me estimate using reasonable assumptions or industry benchmarks. Once you have enough information, produce two outputs.
Format: Two outputs:
Output A: A one-paragraph "cost of inaction" statement (under 100 words) written for my leadership team — specific, evidence-based, ready to present
Output B: A comparison table showing: (1) monthly cost of deferral, (2) 12-month cumulative cost, (3) one line on how the project scope has grown since first deferral, and (4) one line on what decisions are being made blind without this project
Tone: Professional and financially literate. Not dramatic or alarmist. Evidence-first. The language should feel like it belongs in the same conversation as a revenue projection — equal rigour, equal specificity, equal confidence.
Next week in Part 3, I'll introduce the four questions that turn "we should probably do this" into a structured case your CFO can evaluate, the practical framework behind everything I've been describing.
Curious about how we could work together? Book a 20-mintue intro call - no pitch, just pattern matching.
Get the next one in your inbox
