$2.3 trillion. That's the estimated global spend wasted annually on digital transformations that fail to deliver what was promised. Not projects that crash and burn spectacularly - most don't. They quietly absorb budget, produce something that technically exists, and never quite generate the return that justified the investment in the first place.
McKinsey's 2024 research puts the failure rate at 70% for large-scale transformations. Bain goes further - 88% fail to achieve their original ambitions. And yet boards keep approving these investments using the same information, in the same format, with the same governance structures that produced those numbers.
I've been in enough of those rooms to know how it goes. Someone presents the case. There's a discussion about cost. A few questions about timeline. Maybe a debate about vendor selection. Then a vote or a nod and everyone moves on.
We've approved the budget. That's our job. It's the team's job to deliver it. We don't need to be involved in the detail.
I get it. You've got a firm to run. You hired people you trust. But the difference between digital investments that deliver and those that don't is almost never visible in the original proposal. It shows up in how the investment is governed after approval. And the board members who ask the right questions before approving are the ones who make good governance possible.
I want to tell you about a board meeting I sat in a few years ago. A professional services firm - about 300 people, good reputation, genuinely needed to modernise their client-facing systems. The proposal was well-presented. Forty slides. A business case projecting 300% ROI over three years. The board approved it in under an hour.
Eighteen months later, they'd spent the budget. The platform technically existed. Nobody could tell you whether the investment had worked because nobody had defined what "working" looked like before they started. The 300% ROI figure, it turned out, had been reverse-engineered to justify the budget. When I eventually asked the project lead how they'd calculated it, there was a long pause. Then: "We worked backwards from what we needed the board to approve."
That's not a technology failure. That's a governance failure.
When I look back at the transformation programmes we've seen stall or underdeliver - both ones we've been brought in to recover and ones we've watched from the outside - the failure modes are remarkably consistent. Unclear outcome definitions that make it impossible to know whether the investment succeeded. Diffuse ownership where responsibility sits with a committee but nobody is personally on the hook. No mechanism for escalating the decisions the delivery team genuinely can't resolve on their own. And no structure that allows the investment to be redirected when early evidence suggests the original direction was wrong.
BCG's 2024 research found that 60% of transformation failures come down to the absence of a governance framework. Sixty percent. Not bad technology. Not wrong vendors. Not insufficient budget. The absence of a plan for how decisions would be made once the money was committed.
All of these are things a board can require at approval stage. Almost none of them appear in the standard project proposal.
I've distilled this down to five questions over the years - not from reading about governance, but from watching what happens when these questions aren't asked. They're not complicated. They don't require technical knowledge. But asking them genuinely, not rhetorically, changes the shape of everything that follows.
1. What specific problem does this investment solve?
Not what capability it creates. Not what technology it implements. What identifiable problem does it eliminate, and for whom? "We need a new client portal" is not a problem statement. "40% of broker applications contain errors because the current portal doesn't validate inputs in real time, and brokers are placing business elsewhere" - that's a problem statement. The reason this matters is that it determines how you'll measure success. Without it, you're approving a hope.
2. How will we know if it has worked?
What is the measurable outcome, defined in advance, that constitutes success? Not "improved client experience" - that's a feeling, not a metric. Something like "portal login failures reduced by 40% within six weeks of launch" or "qualified inbound enquiries increase by 25% within six months." If the team can't define this before approval, they can't deliver against it after. And you'll have no basis for the conversation when someone tells you it's going well.
3. Who owns the outcome?
Not who owns the project. Not which committee has oversight. Who is the single, named individual who is personally accountable for whether the measurable outcome is achieved? And - this is the bit that gets missed - what authority do they have to make the decisions necessary to get there? Accountability without authority is just a way of setting someone up to fail.
4. What is the cost of not doing this?
What happens specifically if this is deferred for twelve months? This forces the proposal team to articulate the commercial consequence of inaction, not just the benefits of action. Sometimes the answer is genuinely "not much" - and that's useful information. More often, there's a compounding cost the board hasn't fully priced in. Legacy platforms hide a lot from your P&L, and the numbers are usually larger than people expect.
5. What is the phased approach?
What is the first stage, what does it deliver, and what would cause you to stop, redirect, or expand before committing to the next phase? Any proposal that delivers all its value at the end - a big bang after twelve months - is a proposal that gives you no real information until it's too late to act on it.
These five questions are what our WHNN® framework structures into a repeatable process - What, How, Now, Next. But honestly, you don't need the framework to use the questions. You just need someone in the room willing to ask them and wait for a proper answer.
Once you know what to look for, you'll start seeing patterns in proposals that should give you pause.
A proposal that describes outputs rather than outcomes. "We will build a new client portal" versus "clients will access matter documents same-day, measured by portal usage data." The first is a description of activity. The second is a commitment to a result.
A business case projecting ROI without a stated calculation methodology. See above. If someone can't explain how they got to the number, the number is decorative.
A governance structure placing accountability on a steering committee rather than a named individual. Committees are fine for oversight. They're terrible for accountability. When something goes wrong - and something always goes wrong - you need one person who can make a call, not six people who need to schedule a meeting.
A timeline delivering all value at the end rather than in phases. This is the one that catches the most firms out. You approve a 12-month programme, you get status updates saying "on track" for 10 months, and then you find out in month 11 that it isn't. By then, you've spent the money.
And - increasingly common - a proposal written around a specific technology rather than a defined problem. "We recommend implementing [platform X]" before anyone has properly articulated what the platform needs to solve. Technology is an answer. Make sure you've agreed the question first.
The single most effective governance mechanism I've seen - and this applies whether you're a 100-person consultancy or a 500-person law firm - is milestone-based approval with explicit stage gates.
Instead of approving the full budget upfront and hoping for the best, you approve the first phase. At a defined interval, the board reviews actual progress against the measurable outcomes you agreed at the start. Then you decide: proceed, redirect, or stop.
Each stage gate needs three things: a named decision-maker, a defined set of evidence required to proceed, and a clear articulation of what "good enough to continue" looks like. That last one matters more than people think. Without it, stage gates become rubber stamps - everyone nods through because nobody agreed what they were looking for.
Kitces' 2025 research on financial services client portals makes the point well: a 75.8% adoption rate sounds impressive until you realise nearly a quarter of users aren't engaging with the thing you built. If you'd set adoption targets at each stage gate, you'd have spotted the problem early enough to do something about it. Instead, most firms discover it at the post-project review, which is a bit like reading the autopsy report and being surprised the patient died.
I want to land on this because I think it gets misunderstood. The board member who requires this level of rigour isn't making the investment harder to deliver. They're creating the conditions under which delivery is actually possible.
A well-governed investment is one where the team has clarity about what they're trying to achieve, the authority to make the decisions that will get them there, and an escalation route when something goes wrong. That's not interference. That's support.
A COO I spoke with last year told me they'd been about to approve a £400k website and CRM rebuild. The board asked the five questions - their version of them - and it turned out 60% of the original brief was unnecessary. They ended up spending £80k on the thing that actually mattered. Within 90 days, enquiry-to-client conversion had improved by 22%. The original proposal wouldn't have measured that at all.
"We were about to spend £400,000 on a project we did not fully understand," the COO told me afterwards. "The assessment cost us a fraction of that and told us what we actually needed."
That's what asking the right questions costs: one meeting. Not asking them costs everything that comes after.
If you want the five questions and the stage-gate framework as a one-page checklist you can bring to your next board or investment committee meeting, download it here. It's designed to be shared with your finance director, NEDs, or anyone else who'll be in the room when the next digital investment lands on the agenda.