Let me describe a room I've been in more times than I'd like.
A managing partner stands up at a board meeting. They've got a slide deck - a good one, actually. Clear business case, sensible numbers, a credible vendor shortlisted. They're proposing a digital investment. And before they've finished the second slide, someone across the table says: "Didn't we try this three years ago?"
The room shifts. You can feel it. The managing partner knows exactly what's coming, because they were there three years ago too. Maybe they even championed the last one. And now every subsequent slide - no matter how well-constructed - is being filtered through a single, unspoken question: Why should we believe it'll be different this time?
If you're reading this, there's a fair chance you're that managing partner. Or you're about to be. And the instinct you're probably fighting is to build a better business case - sharper numbers, stronger ROI projections, a more impressive vendor. More firepower to overwhelm the scepticism.
That's the wrong move. The problem you're solving isn't a budgetary one. It's a trust problem. And no amount of spreadsheet rigour fixes a breach of confidence.
Here's what makes failed digital investments so sticky inside organisations: they don't create a generalised reluctance to spend money. They create specific, personal, deeply felt positions held by specific people.
There's the partner who warned the board last time that the project was too ambitious, got overruled, and has been quietly vindicated ever since. That person isn't going to stay quiet this time. They don't need to be aggressive about it - they just need to raise an eyebrow, and half the room will remember they were right.
There's the board member who approved the original budget. They're not sceptical because they think digital investment is wrong. They're sceptical because approving it last time cost them credibility, and they're not volunteering for that again.
There are the middle managers who got dragged into workshops, user acceptance testing, and change management sessions for a project that ultimately didn't deliver what was promised. Their enthusiasm has been precisely calibrated by that experience. Next time someone says "we need your input on the new digital initiative," they'll smile politely and give you the minimum viable engagement.
And then there's you - or whoever championed the last investment. The person whose professional judgement is, fairly or not, associated with the outcome. Putting your hand up again takes a kind of courage that a business case template doesn't account for.
The board isn't going to approve another digital investment after what happened last time. We need to wait until it's forgotten.
I understand the impulse. Genuinely. But boards don't forget. They just stop talking about it openly. The scepticism doesn't fade - it calcifies. And in the meantime, the cost of whatever prompted the original investment in the first place is still compounding. Your platform is another year older. Your competitors are another year ahead. Your clients are comparing you to experiences that have moved on without you.
Waiting for people to forget isn't a strategy. It's a slow bleed.
This is the bit that makes people uncomfortable, so let me be direct: the single most important thing you can do when rebuilding the case is to say, clearly and specifically, what went wrong last time. Not in a vague "lessons learned" way. Not buried in an appendix. Up front.
Something like: "The last investment underdelivered for three specific reasons. The scope was too broad - we tried to solve everything at once instead of prioritising. The governance was too diffuse - we had a steering committee of twelve people and no single owner. And the data foundations weren't in place before we started deployment, which meant the platform couldn't do what we'd promised it would."
Now, I want to be careful here, because there's a version of this that tips into self-flagellation, and that's counterproductive. You're not standing up to apologise. You're standing up to demonstrate that you understand what happened - which is the precondition for anyone believing you understand how to prevent it happening again.
Honesty about attribution matters too. Some failures are primarily on the vendor side - they overpromised, under resourced, or lacked the sector knowledge they claimed. Some are primarily on the client side - scope kept changing, stakeholders disengaged, nobody owned the decisions. Most, in my experience, are both. The proposal that blames everything on the previous vendor will get the same reception as the one that takes no responsibility at all. Neither is credible.
I was working with a COO at a professional services firm last year - around 400 people - who'd been through exactly this. Their previous website and CRM rebuild had gone £200k over budget and delivered about 60% of what was scoped. When I asked what went wrong, he initially said "the agency let us down." But when we dug into it together, the picture was more nuanced. The agency had been mediocre, sure. But the firm had also changed the brief three times, pulled key stakeholders out of workshops, and never resolved an internal argument about whether the CRM integration was in scope or not. His honest version - delivered to his board - was far more effective than the blame-the-vendor version would have been. It said: we contributed to this, we understand how, and here's what we'd do differently.
In an environment of institutional scepticism, theoretical arguments lose to demonstrated proof every single time. So before you walk into the boardroom with a full proposal, build some evidence.
The most effective thing I've seen firms do is run something small first. A two-week proof of concept on a single process improvement - maybe £10-15k - and then use the results as the opening of the board presentation. "We tested this approach on our enquiry-to-onboarding handoff. Here's what happened. Now imagine that applied across the client journey." That's infinitely more persuasive than a slide that says "projected 25% improvement in client satisfaction." One of the firms we worked with did exactly this - a 400-person professional services firm that had been quoted over £400k for a full rebuild. We ran a 14-day assessment first, identified that around 60% of the original brief was unnecessary, and fixed the broken enquiry handoff in a 90-day sprint for roughly £80k. When the COO took that result back to his board, the conversation was completely different. He wasn't asking them to trust a projection. He was showing them a number that had already moved.
Peer evidence matters too. The "our firm is different" objection is the refuge of institutional scepticism - it sounds reasonable but it's almost never true in the way people mean it. Find comparable firms - similar size, similar sector, similar starting point - that have succeeded with the approach you're proposing. Not aspirational comparisons with firms five times your size. Relevant ones. A top-50 law firm that went from generating 4% of enquiries through their website to it outperforming their entire business development team within six months is a more useful reference point than a FTSE 100 digital transformation case study.
And then there's the cost-of-inaction argument, which most people undersell badly. The comparison isn't between the cost of the new investment and the cost of doing nothing - because doing nothing has a cost too. It's the ongoing maintenance spend on a platform that's getting more expensive to keep alive, the revenue you're not capturing, the security risk accumulating with every month your legacy platform goes unpatched. The data on this is striking: 60-80% of IT budgets in organisations running legacy platforms get consumed just keeping those platforms alive. That's money you're already spending. You're just not getting much for it.
Here's where I'd push you to do something most second-attempt proposals don't do: design the proposal itself as an answer to the scepticism, not as a case that hopes to overcome it.
Put the honest account of what went wrong on slide two, not in the appendix. Get it out of the way early so the rest of the conversation isn't shadowed by the unspoken question everyone's already thinking.
Then ask for a Phase 1 structure that limits the initial commitment. Don't ask for the full budget up front. Ask for a 90-day, single-use-case pilot. Define what success looks like. Define what happens if it doesn't work. The board isn't being asked to approve a three-year programme - they're being asked to approve a controlled test with a clear gate review before any further commitment. That's a fundamentally different ask, and it changes the risk calculus for everyone in the room - especially the board member who got burned last time.
And be specific about accountability. Not a steering committee. Not a quarterly update. A named owner with decision-making authority and a defined gate review at the end of Phase 1. Vague governance is how the last project died. The proposal that replaces it needs to make governance feel like a feature, not an afterthought.
This is the bit that separates proposals that get approved from proposals that get deferred indefinitely.
If you walk into a board meeting with a second-attempt proposal and it's the first time anyone in the room has seen it, you've already lost. Not because the proposal is bad, but because you've given every sceptic the home advantage. They get to react in real time, in public, with no preparation and no pressure to be constructive.
So do the groundwork first. Have the individual conversations before the meeting.
The frustrated believers - the partners who supported the first investment and are now watching the firm fall further behind - they're your natural allies, but they need to know you're going again before the meeting. Give them the honest failure account in advance. Let them process it privately. Then ask them to support the proposal publicly.
The privately concerned - the board members who've seen competitors move ahead and are more worried than they let on. They exist in almost every firm I've worked with. They won't champion the investment themselves, but they'll support it if someone else takes the lead and presents it credibly. A quiet coffee and a copy of the proposal a week before the meeting can turn a neutral vote into a supportive one.
And the clients. This one gets overlooked constantly. If clients have told you directly that your digital experience is falling short - and in my experience, they usually have, you're just not always listening - that's evidence. "Three of our top-ten clients have independently commented on our portal experience in the last six months" is a more powerful data point than anything in your business case.
I'd be dishonest if I didn't acknowledge this: sometimes the timing isn't right. If the previous failure was six months ago and the wounds are still fresh, forcing the conversation may do more harm than good. There's a difference between institutional memory that needs addressing and institutional trauma that needs time.
But "not yet" is different from "not ever." If you're waiting, wait with purpose. Use the time to build the small wins, gather the peer evidence, have the quiet conversations. So that when the timing is right, you're not starting from scratch - you're presenting a case that's already half-built.
Look, I won't pretend this is easy. Rebuilding the case for digital investment after a failure requires you to do something most of us find deeply uncomfortable: stand up in front of colleagues, acknowledge that something you were involved in didn't work, and ask them to trust you again.
But letting the scar tissue from a previous failure permanently reduce your firm's willingness to invest in its digital foundations is worse. The market isn't waiting for your board to recover its confidence. Your clients aren't grading you on a curve because you had a bad experience with a vendor three years ago. And the cost of inaction - as boring as that phrase sounds - is real and it's compounding.
The proposals that succeed the second time around aren't the ones with better numbers. They're the ones that address the trust deficit directly. Name what went wrong. Take your share of responsibility. Propose something structurally different - not just a different technology or a different vendor, but a different governance model, a different scope, a different accountability structure. Start small. Build evidence. Find your allies.
If you want support structuring that conversation - including an honest diagnosis of what went wrong and how to present a genuinely different approach - that's exactly the kind of work we do. Book a recovery planning session and we can work through it together. An outside perspective is useful here, but not because it brings a new strategy. It's useful because someone who's sat in that room before can tell you: this is fixable.