What I See Every Day: When it's not about money anymore

Over the last three weeks, I've talked about the language gap, the compounding cost of deferral, and the four questions that reframe any project. Every example so far has been about financial cost, duplicate spend, wasted team hours, growing complexity.

This week I want to start somewhere different, because the most important risk of inaction case I've ever seen had nothing to do with money.

I was working with a business that sold consumer products, including products designed for babies. A regulatory compliance requirement had been flagged. It needed work. It needed focus. But it was sitting on the backlog competing against commercial initiatives with revenue projections, and it wasn't getting the prioritisation it needed to ensure delivery before the deadline.

When we applied the four questions from Part 3, the conversation changed immediately.

What specifically happens if we don't do this? The product doesn't meet regulatory requirements. It can't legally be sold in key markets.

How likely is this? Certain. The deadline is fixed. There's no extension process.

When does it hit? A specific, immovable date, already approaching.

Does the cost grow the longer we wait? Yes, but not in the way you'd expect. The financial cost was a regulatory fine. Significant, but manageable. The real cost was what happens if a product reaches a consumer without meeting safety requirements. In this case, the end user was a baby. If that product caused harm because a compliance step was missed, that's not a financial conversation anymore. That's an existential one.

The project went to the top of the priorities. Not because someone shouted loudest. Not because of internal politics. Because the risk of inaction was articulated with the kind of specificity that made any other decision indefensible.

That's what competing on equal terms looks like. Not every case will carry this kind of weight. But every case deserves the same rigour of articulation, because until it does, leadership teams are making prioritisation decisions with half the picture.

What Needs to Happen: Put both sides of the equation on the same page

Throughout this series, I've argued that the problem isn't bad leadership or missing frameworks. It's a language gap. Revenue initiatives arrive in the prioritisation conversation fully dressed, numbers, projections, timelines, growth curves. Non-commercial initiatives arrive in a sentence: "We need to do this."

Here's what closing that gap actually looks like. Take a procurement controls project, a real example I've worked through, anonymised:

Before (how it typically lands):

"We need to implement a procurement system to improve our purchase order process and give budget holders better visibility of their spend."

That's competing against: "The new CRM integration will reduce our sales cycle by an estimated 15%, generating an additional £320K in revenue in the first 12 months."

It doesn't stand a chance.

After (reframed using the four questions):

"Without procurement controls, an internal review identified approximately £85K in duplicate or uncontrolled spend last year. The finance team spends an estimated 20 hours per month on manual reconciliation. Both figures grow as the business scales. And every quarter of deferral increases the data clean-up required when we eventually implement, meaning the project gets more expensive the longer we wait."

Same project. Same facts. Completely different weight in the room.

The revenue project might still win. But the decision is now informed and deliberate, not a default to whichever initiative showed up with a number attached.

That shift, from invisible to visible, from sentiment to evidence, from "we should probably do this" to a case your CFO can evaluate, is what this entire series has been building toward.

The Resource I've Been Building Alongside This Series

If you've followed this series, you've got the thinking. You understand the language gap. You know deferral compounds. You've got the four questions.

The question I keep getting asked is: "How do I do this consistently? How do I apply it across my whole backlog? How do I score and compare these projects so they compete fairly alongside revenue initiatives?"

That's what The Risk of Inaction Playbook is for.

It's a practical, function-by-function guide that takes the four questions from Part 3 and builds a structured, repeatable method around them, including:

• A four-component framework for articulating the risk of inaction with the same rigour your business already applies to return on investment

• Two scoring approaches, a rapid triage for your full backlog and a detailed numerical assessment for the projects that need a boardroom-ready case

• 10 function-specific worked examples (Finance, IT, Operations, HR, Legal, and more), each showing the before and after, with anticipated leadership questions and prepared answers

• A step-by-step process for applying the framework to your own backlog

• Guidance on presenting the case to different stakeholders and how to handle the most common pushback

This isn't theory. It's the methodology I use with leadership teams, built into a resource you can pick up and apply this week.

Get the playbook here.

Tip of the Week: Run the before/after test on your highest-priority non-commercial project

Pick the most important project on your backlog that doesn't have a revenue number. Write down how it's currently framed, the exact language from the business case, the request form, or however it entered the pipeline.

Then rewrite it using the four questions:

• What specifically happens if we don't do this? Evidence, not sentiment.

• How likely is that? Honest assessment, certain, probable, or possible.

• When does it hit? Fixed date, approaching threshold, or gradual erosion.

• Does the cost grow the longer we wait? What does 6 and 12 more months look like.

Put both versions side by side. Read them as if you're the CFO seeing them for the first time. The gap between the two versions is the language gap this series has been about, and closing it is how your project starts competing on equal terms.

Bonus: Use this AI prompt to build your side-by-side comparison.

A Final Reflection on This Series

Over four weeks, we've covered:

• Part 1: The Language Gap | why your most important project keeps losing, and it's not because it's less important

• Part 2: The "Do Nothing" Illusion | why deferral compounds cost, complexity, and decision quality

• Part 3: Four Questions That Change the Conversation | the exact reframe I use to turn "we should probably do this" into a case your CFO can evaluate

• Part 4: Competing on Equal Terms | what it looks like when both sides of the equation are visible, comparable, and articulated with equal rigour

The thread running through all four parts is simple: the projects that protect, sustain, and scale your business deserve the same quality of articulation as the ones that promise to grow it. Not because they're always more important, but because the decision about which one comes first should be informed, deliberate, and honest.

Revenue initiatives will still win sometimes. They should. But when they win by default, because nobody articulated the other side, that's not prioritisation. That's a language gap costing you more than any single failed project.

• 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