I need to be upfront before we get into this. What follows isn't the polished version - not the case study we'd put in a pitch deck. It's closer to what I'd tell you over a coffee if you asked me what it's actually like walking into one of these situations.
Because if you're reading this, there's a reasonable chance you're living in one right now. A programme that started with good intentions, got funded properly, and then just... stopped producing results. Not dramatically. No single catastrophic failure. More like a slow fade. And now you're sitting with a budget that's been partially spent, a team that's lost confidence, and a nagging feeling that bringing in another external partner might just repeat the whole cycle.
I get that. So let me tell you what happened with one firm - and I'll try to be honest about all of it, including the bits that weren't straightforward.
Mid-sized B2B professional services firm. Around 250 people, multiple offices, well-respected in their sector. They'd kicked off a digital transformation programme roughly eighteen months before we got involved. New website, CRM integration, client portal, reworked onboarding journey. Total approved budget somewhere north of £400k.
By the time we arrived, they'd spent approximately £280k. What they had to show for it: a partially built website that nobody was using, a CRM integration that had been "90% complete" for about six months, and a client portal that existed only as wireframes and a Jira backlog that hadn't been touched in eleven weeks.
The internal climate was - and I'm choosing this word carefully - toxic. Not between individuals, necessarily, but between functions. Marketing blamed IT. IT blamed the delivery partner. The delivery partner blamed scope creep. The COO, who'd originally championed the programme, had quietly stopped mentioning it in board meetings. And the team who'd been seconded to support it were demoralised in a way that was genuinely hard to watch. They'd given months of their time to something that felt like it was going nowhere, and they'd stopped believing anyone could fix it.
I've written separately about the five warning signs that a transformation is about to stall, and this firm had at least three of them running simultaneously. The delivery partner had disengaged - stopped attending steering group meetings about four months in. The governance structure had collapsed into status updates rather than decisions. And the original business case hadn't been opened since the day it was approved. Literally. The COO told me he wasn't even sure which shared drive it was saved on.
This sounds like every other agency case study. You'll tell me it went brilliantly and I'll wonder what you're leaving out.
Fair. So let me tell you what we actually found.
We ran a 14-day diagnostic. Not a sales exercise dressed up as discovery - an actual assessment of what had gone wrong and whether recovery was even viable. Sometimes the honest answer is "this isn't recoverable in its current form" and you need to be willing to say that.
The business case was the first problem. It had been written to secure budget, not to guide delivery. The outcomes it described were vague enough to be unfalsifiable - things like "improved digital client experience" and "streamlined operations." No specific metrics. No baseline measurements. No definition of what success would actually look like in six or twelve months. So when delivery started drifting, there was nothing concrete to drift from. Nobody could say "we're off track" because nobody had defined the track.
The delivery partner was the second thing. They were a decent firm - technically competent, good portfolio. But they'd been brought in to build, not to think. The architecture they'd designed was actually sound. The problem was they'd implemented it without adequate user testing or stakeholder input, because the governance structure didn't require either. They'd been building to a specification signed off in month two and never revisited, even as the business's understanding of what it needed evolved. By month eight, what was being built and what was actually needed had diverged significantly, and nobody had a mechanism to flag it.
The third finding surprised me. The internal people seconded to support the programme were good. Really good. They understood the business, they understood the clients, and they had practical ideas about what would actually make a difference. But they'd been positioned as "contributors" rather than decision-makers, so their input had been systematically filtered through layers of governance that diluted it into irrelevance. One of them told me, about a week into the assessment: "I flagged the portal problem in March. It went into the steering group notes. Nothing happened." That was eight months before we arrived.
When we presented these findings to the leadership team, the first reaction was defensive. Completely normal, by the way. Nobody wants to hear that the programme they funded and championed has structural problems that predate the delivery partner's involvement. The COO's initial response was essentially: "So you're saying we set this up to fail?" Honestly, that's not an unfair characterisation - but it's also not a helpful one. What we said was: the programme wasn't set up to succeed in the way it needed to, and the good news is that most of what's been built is usable. The foundations aren't the problem. The scaffolding around them is.
It took about two weeks of conversations to reach shared agreement on what had actually gone wrong. That felt slow at the time. Looking back, it was probably the most important two weeks of the entire engagement.
Three changes. I want to be specific because vague descriptions of "improved governance" are worth nothing.
Governance. We collapsed the steering group from twelve people to five. The COO, the head of marketing, the head of IT, one client-facing partner, and me. Monthly two-hour status reviews became fortnightly 45-minute decision sessions. Every meeting had a decision log. If a decision wasn't made, it was escalated - not deferred. And the internal team members who'd been sidelined got direct input into those sessions. Not a token seat at the table - actual authority to flag problems and propose solutions without going through three layers of filtering.
Scope. We cut the programme roughly in half. The client portal - the most ambitious and least-defined element - was deferred to phase two with a clear set of prerequisites attached. The CRM integration, which was genuinely close to working, became the first priority. The website was rescoped around three highest-value user journeys rather than the eighteen in the original specification.
Visible delivery. We committed to having something live and working within 30 days. Not a prototype. Not a staging environment. Something real that actual users could interact with. That ended up being the CRM integration - cleaned up, tested properly, deployed. Not glamorous. But when the sales team started getting properly routed enquiries for the first time in months, the mood shifted. People started believing recovery was possible.
There's a companion piece on what recovery looks like and how to restart a stalled digital programme that covers the methodology in more detail. What I'm describing here is one specific instance of it.
Round numbers, because that's what we actually have. Internal adoption of the new CRM workflow went from around 20% to around 60% within three months. The website - rescoped and rebuilt around those three core journeys - was live within fourteen weeks. Total additional spend for the recovery programme was approximately £110k, which means the firm's total investment came to around £390k - roughly in line with the original budget, but for a materially different and more focused set of outcomes.
Stakeholder satisfaction at programme close was genuinely high. Not because everything was perfect, but because people felt heard, decisions were transparent, and things actually moved. The COO told me at the final review that the most valuable thing wasn't the technology. It was getting the team's confidence back.
But - and this matters - those results weren't produced by Distinction alone. They were produced by a client leadership team willing to make uncomfortable changes. The COO personally took back ownership of the programme after having stepped away from it. The head of marketing agreed to defer the portal she'd been championing for over a year. The partner who'd been most vocal about the programme's failures agreed to join the stripped-back steering group and actually contribute rather than critique. Without those decisions, our approach would have made no difference at all. I want to be clear about that.
Here's the part that makes this different from a pitch deck.
The hardest moment was about three weeks in. The original delivery partner got wind that we were involved and requested a meeting. That meeting was, frankly, awful. They felt blindsided and defensive. We felt like we were being positioned as replacements rather than what we actually were - a recovery team. The client was caught in the middle. It nearly derailed the whole thing. In the end, the COO handled it well - he had a direct conversation with their MD, acknowledged what had gone right in the original engagement, and agreed a clean separation. But it was messy, and I underestimated how messy it would be.
What I'd do differently: I'd have insisted on that conversation happening in week one, not week three. We knew the original partner's disengagement was a finding. We should have anticipated that our involvement would surface it, and we should have helped the client manage that transition proactively. That's on me.
The other thing - less dramatic but arguably more important - is that we should have pushed harder on the business case rewrite at the very start. We flagged that the original was inadequate, but we didn't make rewriting it a prerequisite for restarting delivery. We did it in parallel, which meant for the first few weeks we were delivering against outcomes we'd agreed verbally but hadn't formally documented. In a programme that had already suffered from unclear objectives, that was a mistake. We got away with it because the client team was engaged and aligned. Same situation again, though, and I'd make the business case rewrite the first deliverable. Full stop.
There's one more thing - and I see this on every recovery engagement we do. Around week six, when the CRM integration was live and the website was taking shape, the natural enthusiasm kicked in: "Great, let's bring the portal back into scope." We had to have a firm conversation about why that impulse, while completely understandable, was exactly the pattern that had caused the original programme to stall. To their credit, they listened. But I've had that conversation in some form on every single recovery engagement. Success breeds ambition, and ambition breeds scope creep. It's almost gravitational.
I've written about why digital programmes fail in the first place and how to spot the warning signs before it's too late. If you've read those and you're still here, you're probably past the diagnosis stage.
If you'd like to talk through your situation without committing to anything, we offer a confidential first conversation. No deck, no proposal - just an honest discussion about what you're dealing with. Sometimes it confirms you need help. Sometimes it confirms you don't. [Book a conversation here].
The one thing I'd ask: don't let it sit for another quarter. Every recovery engagement I've been involved in has one thing in common. The client wishes they'd started it sooner. The programme doesn't get easier to fix with time - the team gets more demoralised, the sunk cost psychology gets stronger, the political dynamics get more entrenched.
You already know whether your programme is working. Trust that instinct.