Most transformations don't fail in delivery. They die in a planning phase that never ends. Here's how to escape the strategy coma and actually start.
Here's a confession that might sound odd coming from someone who runs a consultancy: I've sat in more kickoff meetings than I've seen projects actually kick off.
Not literally. But the ratio is closer than it should be. And the reason is almost always the same. The meeting goes well. Everyone's energised. There's a genuine sense that something needs to change. Someone mentions getting the strategy right before committing budget. Someone else suggests a broader stakeholder consultation. A third person raises whether IT should be leading this or marketing. And then - with the very best of intentions - the whole thing drifts into a planning phase that never quite ends.
I've started calling it the strategy coma. The organisation isn't dead. People are busy. Documents are being written, workshops are being scheduled, vendor shortlists are being assembled. It looks and feels like progress. But nothing is actually changing. No decision has been made that has consequences. No customer is having a different experience. No system has been touched.
We need to get the strategy right first. If we rush into delivery, we'll waste money.
And you're not entirely wrong. Some planning is essential - rushing headlong into a £300k platform rebuild without understanding what you're solving for is genuinely reckless, and I've written separately about why digital projects fail to deliver when the foundations aren't right. But here's what I've noticed over 25 years of doing this: the firms that stall almost never stall because they did too little planning. They stall because the planning became the thing they were doing. The strategy document became the deliverable. And at some point, without anyone consciously deciding it, the planning phase replaced the transformation it was supposed to enable.
There's something psychologically satisfying about planning. It feels responsible. Rigorous. You can point to it in a board meeting and say, "We're being thorough." Nobody ever got fired for recommending more research.
But I think there's something else going on - something a bit less comfortable to name. Planning is safe. Delivery is not. The moment you commit to building something, you've created the possibility of failure - visible, measurable, blame-attractable failure. Whereas a strategy phase can run for eighteen months and the only thing anyone can say is that you were being diligent.
I was working with a mid-sized consulting firm - about 180 people, decent reputation, solid client base - who'd been "in the planning phase" of their website and CRM transformation for fourteen months. Fourteen months. They'd produced a digital strategy document (62 pages), a technology options appraisal (another 40), run workshops with every practice group, surveyed their top 50 clients, and commissioned two separate vendor evaluations. The total cost of all that planning? Somewhere north of £120k when you factored in internal time and external consultants.
The outcome? A recommendation to do more discovery work before committing to a platform.
The managing partner looked at me across the table and said something I've never forgotten: "We've spent a year getting ready to get ready."
That's the strategy coma in one sentence.
I'll be honest - I didn't handle that conversation particularly well. I'd seen the signs early on and said something vague about "maintaining momentum" rather than naming the problem directly. By the time I was sitting across from the managing partner, we'd both wasted time we didn't need to. I should have called it sooner.
It's rarely one thing, and it's rarely as neat as a list of causes. What I usually find is a specific combination of pressures that, individually, sound perfectly reasonable - and together, create paralysis.
Fear of getting it wrong is almost always in the mix, especially in firms where a previous digital project went badly. The scar tissue from a failed implementation three years ago creates an institutional aversion to commitment. So you keep planning, because planning can't fail in the same way delivery can. Except it can - it just fails quietly, through opportunity cost rather than write-offs.
Then there's the ownership problem, which is endemic in partnership structures. Who actually owns digital transformation in a law firm? The managing partner? The COO? The head of marketing? The IT director? I've been in rooms where all four of those people were present and every single one of them thought it was primarily someone else's call. When nobody has unambiguous authority to make the decision, everyone defaults to consensus-seeking. And consensus-seeking in a partnership of 40 people is a fantastic way to ensure nothing happens for a very long time.
Underneath both of those, there's usually a quieter thing: the belief that one more piece of research will finally provide the certainty needed to act. One more competitor to benchmark. One more vendor demo. One more stakeholder to consult. I understand the instinct - but in digital transformation, you never have perfect information. The landscape shifts. Your competitors don't wait. And half of what you learn in month one of delivery will contradict what you assumed during planning anyway.
I worked with a financial services firm a few years back - about 300 people, well-regarded in their sector - where all three of these were running simultaneously. A botched CRM implementation in 2019 had left the leadership team genuinely gun-shy. Ownership of the digital programme was split, uncomfortably, between the CTO and the CMO. And they'd been benchmarking competitors for so long that the benchmarks themselves were out of date. When I pointed that out - that they were comparing themselves to where their competitors had been eighteen months ago, not where they were now - there was a long silence. Then someone said, "Right, so we've been planning against a moving target." Yeah. Exactly.
While you're workshopping, your competitors are shipping.
That's not hyperbole. We work with firms across professional services, financial services, legal, and consulting. And the gap between the ones that move and the ones that plan is getting wider every quarter. Not because the movers are reckless - most of them are actually quite cautious. They just made a different choice about where to apply their caution.
Two mid-market law firms, similar size, similar practice areas, similar market position. Both recognised in early 2023 that their websites were underperforming. Firm A commissioned a full digital strategy review. Firm B ran a 14-day diagnostic, identified their biggest problem - a clunky, leaky handoff between initial enquiry and client onboarding that was haemorrhaging conversion - and fixed it in a 90-day sprint for about £80k. By the time Firm A had finished their strategy phase and was ready to brief agencies, Firm B had already seen a 22% improvement in enquiry-to-client conversion and was onto their second initiative.
Firm A wasn't being stupid. They were being careful. But "careful" had cost them nine months and roughly £90k in planning costs, with nothing to show a client or a partner. Firm B had evidence. And evidence, it turns out, is a much better foundation for the next decision than assumptions.
Every month in the coma is a month where the gap widens. And the really maddening irony is that the longer you plan, the bigger the eventual project becomes, because the gap keeps growing. The thing you were trying to avoid by being thorough - an overwhelming, expensive transformation - becomes more overwhelming and more expensive precisely because you waited.
I'm not arguing against strategy. That would be daft. What I'm arguing against is strategy as a prerequisite for action, rather than something that emerges from it.
The firms that break out of the coma share a pattern. They start small. They pick one thing - usually the thing causing the most visible pain - and they fix it. Not perfectly. Not comprehensively. But tangibly. Then they use what they learn from that to inform what comes next.
A 400-person professional services firm we worked with had been quoted over £400k for a full website and CRM rebuild. Their COO had a nagging feeling they were about to spend a lot of money solving the wrong problem - not a specific technical objection, just a gut sense that the brief had grown too big and too vague. So instead of signing off on the whole thing, they started with a two-week diagnostic. It turned out that roughly 60% of the original brief was unnecessary. The real drag on their business was something much more contained: a broken handoff between their sales team and their onboarding process that was losing them clients they'd already won. They fixed that first - about £65k, ten weeks - and used what they learned to write a much sharper brief for the rest.
That's not anti-strategic. That's the most strategic thing they could have done. They bought themselves evidence before they bought themselves a project.
But we've already done a diagnostic. We know what the problems are.
Do you, though? Or do you know what the problems looked like when you last looked properly? Because I've had that conversation more times than I can count, and when I ask when the last diagnostic was done, the answer is usually "about eighteen months ago" - which, in digital terms, is basically a different era.
One of the reasons we built the WHNN framework, The What and the How, for the Now and the Next, is because we kept seeing the same failure mode. Firms that could articulate what they wanted to achieve but had no honest assessment of where they actually were, and no mechanism for maintaining momentum once the initial enthusiasm wore off.
The "Now" assessment is where the strategy coma usually breaks. Not "where do we want to be?" - everyone loves that conversation. But "where are we actually, right now, today?" That's the one people avoid, because the answer is usually uncomfortable. I've sat in rooms where the "Now" conversation revealed that the firm's most-visited web page was a 404 error. That their highest-traffic content was a blog post from 2017 that nobody remembered writing. That their enquiry form had been broken for six weeks and nobody had noticed because enquiries had been so low for so long that the absence of them didn't register as unusual.
And then the quarterly cadence does the rest. Every three months, the leadership team reconvenes. What's working? What isn't? What's changed in the market? Where should the next investment go? It sounds simple - and it is - but it prevents the single most common failure mode in transformation: the slow drift back to business as usual once the initial energy dissipates.
When you know you're reconvening in 90 days and someone's going to ask what happened, it concentrates the mind wonderfully.
Look, I understand the instinct. You're responsible for a significant investment. You've probably seen digital projects go sideways. The last thing you want is to be the person who signed off on something that didn't work.
But consider this: what's the actual cost of another six months of planning? Not just the direct cost - the consultants, the workshops, the internal time. The indirect cost. The clients who are tolerating your portal rather than valuing it. The talent you're not attracting because your digital presence looks like 2019. The competitors who started their transformation six months ago and are already seeing results.
So here's my challenge. If you've been planning for more than three months and haven't shipped a single change that a client or employee would notice, you're probably in the coma. And the cure isn't a better strategy document.
Start with a diagnostic. Start with the thing that hurts most. Start with something you can deliver in 90 days and learn from. Then build your strategy around what you discover, not what you assumed.
The firms that win at this aren't the ones with the best plans. They're the ones who started.
If you're not sure where that first step should be, the practical companion piece on where to start goes into the mechanics - what a good first 90 days actually looks like, and how to pick the right problem to fix first.
