The Language Gap: Why Your Most Important Project Keeps Losing

What I See Every Day: The project that matters most gets the least airtime

Here's a scene I've watched play out in almost every prioritisation meeting I've sat in across 15+ years.

The commercial team presents their project. There's a revenue number. A growth projection. A market opportunity with a deadline. The language is confident, specific, and financial. The room gets it immediately.

Then the IT or operations team presents theirs. There's a platform that needs upgrading. A security vulnerability. A procurement process that's entirely manual and creating control gaps. The work is solid. The need is real.

But the case lands as "we need to do this" or "this is a risk", and it's sitting next to a slide that says "£320K additional revenue in the first 12 months."

The commercial project wins. Every time.

Not because it's more important, but because nobody gave the operational project an equal voice in the conversation.

I call this the language gap, and it's one of the most expensive, invisible problems in mid-market businesses.

The gap isn't in the quality of the work. It's in the quality of the articulation.

What Needs to Happen: Give "Do Nothing" a price tag

Most business case templates have a field somewhere that asks: "What happens if we don't do this?" It's almost never filled in properly. One line. Maybe two. "Continue with current process." "Accept current risk."

And that's the problem. "Do nothing" is never actually "nothing happens." It's "these specific consequences happen, on this timeline, at this cost." But because nobody is required to articulate those consequences with the same rigour as the revenue projection sitting next to it, the field gets skipped.

What needs to change is simple in principle: every project entering a prioritisation conversation should be evaluated on both what it delivers and what happens if it doesn't get done.

Return on investment asks: "What do we gain by doing this?" Risk of inaction asks: "What do we lose, risk, or fail to prevent by not doing this?"

Every prioritisation decision has both sides. Right now, most businesses only formalise one.

Tip of the Week: Audit your "Do Nothing" row

Pick one project on your backlog that doesn't have a revenue number. Open the business case or request form, whatever your process uses.

Find the field that asks what happens if you don't do it. Read what's there.

If it's a single sentence, "manual process continues," "current risk remains", that's your language gap in action. That field is where the real decision lives, and it's been left empty.

This week, try rewriting that one field with specificity:

• What exactly happens if this doesn't get done? (Not "things get worse", what specifically?)

• What is it already costing you in time, money, rework, or risk?

• Does that cost grow the longer you wait?

You don't need a framework yet. You just need to stop accepting one line answers for the most important question in the business case.

Next week in Part 2, I'll unpack why deferred projects don't just wait, they get more expensive. The compounding cost of inaction is the piece most leadership teams never see.

• Curious about how we could work together? Book a 20-mintue intro call - no pitch, just pattern matching.

helen.beckford@felicetteconsultancy.com 
www.felicetteconsultancy.com | www.linkedin.com/in/hebeckford