You launched the new platform. The team has been trained. The metrics improved. The board got their update. And then, slowly, almost imperceptibly, everything started drifting back.
Not dramatically. Nobody pulled the plug or declared the project a failure. It was subtler than that. The quarterly reviews stopped being quarterly. The workarounds that were supposed to disappear crept back in because "it's just quicker this way." The champion who drove the programme got pulled onto something else. And twelve months later, you're sitting in a leadership meeting looking at numbers that have flatlined, wondering where the momentum went.
If this sounds familiar, you're not alone. McKinsey's 2024 research on transformation sustainability found that even among programmes that succeed initially, around 40% fail to maintain their gains beyond twelve months. Which means the 70% failure rate everyone quotes is actually worse than it looks - because a chunk of the "successes" quietly unravel too.
I've seen this pattern play out so many times that I've started treating it as the default outcome, not the exception. That reframe changed how I think about everything we do at Distinction.
Let me make this specific, because I think you'll recognise it.
A mid-sized professional services firm - 200 people, four offices - invests properly in a digital transformation. New CMS, redesigned client portal, CRM integration, the works. The programme runs for six to nine months. There's a steering committee, a project manager, weekly standups, the full governance apparatus. It launches. The early metrics are genuinely good. Enquiries up, bounce rate down, the team publishing content independently for the first time. Everyone's pleased.
Then the programme gets declared "complete." The steering committee disbands. The project manager moves on. The budget line gets closed. And the organisation collectively exhales and turns its attention to the next thing.
We've done the transformation. The new systems are in. The team knows how to use them. We don't need to keep pushing - we just need to let it settle.
I understand that instinct completely. After months of sustained effort, the desire to step back feels not just reasonable but healthy. And sometimes it is. But "letting it settle" and "actively maintaining the new standard" are not the same thing. One is rest. The other is neglect dressed up as patience.
The transformation wasn't the problem. The sustainability design was missing.
I'm not arguing that you need another transformation programme running alongside the one you just finished. That's the fastest way to exhaust an organisation. Initiative fatigue is real, and I've written separately about the cultural blockers that kill digital progress - it's right near the top of that list.
What I am arguing is that continuous improvement needs to become a quarterly discipline. A rhythm. Something lightweight enough to sustain with existing capacity, but structured enough that drift gets spotted before it becomes entrenched.
Think of it like this. You wouldn't renovate your house, spend a fortune on a new kitchen and bathroom, and then never service the boiler or clean the gutters again. You'd maintain it. Not with the same intensity as the renovation - but consistently, on a schedule, before the small problems become expensive ones.
The firms I see compounding their digital improvements year on year aren't the ones with the biggest programmes. They're the ones that have made improvement a habit rather than an event. Research consistently shows that continuous improvement programmes sustain outcomes three times better than project-based transformations that declare completion. Not a marginal difference.
So what does this actually look like in practice? Specific enough that you could run the first one of these next month without calling anyone.
The quarterly review. Sixty minutes. Senior level. Once a quarter. You're answering three questions: what has improved since last quarter? What has drifted? And what is the single highest-impact action for the next quarter? Not a reporting exercise - a decision-making conversation. The temptation is to turn this into a two-hour dashboard review with 40 slides. Resist that. The value is in the conversation, not the deck.
I sat in one of these recently with a COO at a consulting firm. Took us about 45 minutes. We identified that their content publishing cadence - which had been excellent post-launch - had dropped from weekly to "whenever someone gets round to it." That single observation, caught at the three-month mark rather than the twelve-month mark, was the difference between a quick fix and a full reset. She was genuinely surprised. She'd assumed someone was keeping an eye on it. Nobody was.
Firms that review quarterly rather than annually are significantly more likely to sustain their gains - and yet most organisations I talk to either review annually or not at all.
The prioritisation rule. Simple but brutal: no new digital initiative starts until an existing one has either delivered its expected outcome or been formally deprioritised. The single biggest killer of sustained improvement isn't lack of ambition - it's fragmented attention. Firms trying to do seven things at once end up doing none of them properly. Focus beats breadth, every time.
Honest measurement. Pick three to five outcome metrics and report them consistently. Not vanity metrics. Not "we had 50,000 website visitors this month." Metrics that connect to commercial outcomes: enquiry volume, conversion rate, time-to-publish, client satisfaction scores. Whatever matters to your firm. If the numbers are drifting, say so. The whole point of measurement is to make drift visible before it becomes entrenched.
Celebrating progress. This one feels soft, and I'll admit I used to be dismissive of it. I've changed my mind. Professional services firms are culturally wired to focus on problems. Partners talk about what's broken, what needs fixing, what's at risk. Rarely does anyone say "that thing we launched six months ago? It's still working brilliantly and here's the proof." I remember sitting with a managing partner last year who genuinely didn't know that the portal his team had rebuilt eighteen months earlier had cut client onboarding time by a third. Nobody had told him because it was working. Deliberately recognising improvements that have been sustained creates a positive feedback loop. It sounds obvious, but I can count on one hand the number of firms I've seen actually do it.
So you've got the four mechanisms. The question is: how do you stop the quarterly review itself from becoming another thing that happens twice and then fades?
This is where I want to talk about how we approach it at Distinction. We developed a framework called WHNN - What, How, Now, Next - and its quarterly cadence is specifically designed to solve this problem.
Each quarter, the review gets structured around four questions. What has changed since last quarter - in the market, in client expectations, in the firm's own context? How should priorities shift in response? What does the Now require - what's the immediate work that needs doing? And what does the Next look like - where are we building toward in three, six, twelve months?
The reason this works better than a freeform "how are things going" conversation is that it forces you to connect immediate tactical decisions to the broader direction. Without that connection, quarterly reviews tend to become reactive - you fix whatever's most visibly broken and move on. With it, you're making choices that compound.
I'll be honest: when we first started running these with clients, I expected them to feel like governance. Useful but slightly dreary. What actually happened was that leadership teams started looking forward to them. One operations director told me it was the only meeting where she felt like the organisation was actually steering rather than just reacting. Which, if you've ever tried to get partners excited about a governance meeting, you'll know is not nothing.
There's a companion piece on WHNN that goes into much more detail about how the framework operates in practice.
Let me make this concrete, because the compounding argument is the one that tends to land hardest with managing partners.
Say your website currently generates 20 qualified enquiries a month. You run the quarterly rhythm. Each quarter, you identify one high-impact improvement and execute it. Each improvement delivers a 10% lift on that metric - conservative, based on what we typically see.
After quarter one: 22 enquiries a month. After quarter two: roughly 24. After quarter three: about 27. After two years - eight quarters of 10% compounding improvement - you're at around 43 enquiries a month. More than double where you started.
Now compare that to the alternative: a big-bang programme every three years. You invest heavily, get a 50% lift, ride it for a year, watch it plateau, watch it drift, and end up back near your starting point by the time the next programme kicks off. The peak might be higher. The sustained average is lower. Often significantly lower.
The maths isn't complicated. The discipline required to sustain it is the hard part.
If all of this sounds straightforward, it's because conceptually it is. The challenge isn't intellectual - it's organisational. The things that prevent firms from sustaining improvement are almost never technical. They're cultural. The partner who doesn't see digital as their responsibility. The operations leader stretched across too many priorities. The assumption that the transformation "settled" things and now everyone can move on.
The firms that invest consistently outperform the ones that invest heavily but episodically. There's a real difference between those two things, and most organisations don't clock it until they're already behind.
So if you've just finished a transformation programme and you're feeling the collective organisational exhale, this is the moment. Not in six months when the metrics have plateaued. Not in twelve months when the workarounds have reappeared. Now. While the governance muscle is still warm and the team still remembers what good looks like.
Set the first quarterly review. Block sixty minutes. Ask the three questions: what's improved, what's drifting, what's the highest-impact next action. Then do it again in three months.
If you want a structure for that conversation - something you can put in front of your leadership team next month - we've put together a one-page quarterly transformation review template. It covers the three review questions, a preparation guide, and a simple format for recording decisions and commitments. It's built around the WHNN framework, but honestly, it's useful whether you ever work with us or not.
The firms that win aren't the ones with the biggest transformation budgets. They're the ones that turned transformation from a project into a habit.