I want to describe a document you've almost certainly seen. You might have commissioned it. You might even have one sitting in a shared drive right now, somewhere between the brand guidelines nobody opens and the IT roadmap from 2022 that was out of date before the ink dried.
It's about 40 pages. Maybe 60. It has a contents page. It has a section called "Vision and Ambition" near the front, a section called "Key Priorities" in the middle - usually between six and twelve of them, which is already a problem - and a section called "Implementation Roadmap" near the back that gets progressively vaguer the further out it goes. There are some nice diagrams. A maturity model, probably. Some competitor screenshots. A few references to "best practice" that are really just things the consultants who wrote it saw at their last client.
It cost somewhere between £30k and £150k to produce. It took four months. It involved workshops. It involved stakeholder interviews. It involved a steering committee.
And it changed absolutely nothing.
We invested significantly in our digital strategy. It's comprehensive and ambitious. We just need to execute it.
I hear this a lot. And every time, I want to ask the same question: if the strategy is so good, why hasn't anything happened? Not "why hasn't everything happened" - I'm realistic about timelines. But why, six or twelve months after the big reveal, are you still having the same conversations about the same problems? Why is the website still the website? Why are the same integration headaches causing the same workarounds? Why does the quarterly board update still say "in progress" next to the same three initiatives it said "in progress" next to last quarter?
The answer, in my experience, is almost never that the strategy was wrong. It was never really a strategy. It was a document. And those are very different things.
Over the years - and we've been doing this at Distinction for over two decades now, so I've seen a lot of these documents - I've noticed the same three patterns that turn strategic thinking into strategic theatre. I've started calling them comfort traps, because that's what they are. They feel productive. They look responsible. They give everyone involved the warm sense that something important is happening. But they're substitutes for the thing itself.
The first is strategy as document. The most common one, and almost invisible because it's so normalised. The process of producing the strategy becomes the achievement. There's a kickoff. There are workshops - sometimes genuinely good ones, where real problems get named for the first time. There's a discovery phase. There are interim readouts. Then there's a final presentation, usually to the board or the leadership team, where everyone nods and says "this is really thorough." And then... nothing. Or rather, nothing different. Because the energy went into the document, not into what comes after it.
I sat in a boardroom about eighteen months ago - professional services firm, about 250 people - and watched the CEO present what he called their "refreshed digital strategy." Lovely deck. Genuinely well-thought-through in places. And I asked a simple question: "Which of these initiatives has a named owner, a budget, and a delivery date?" The silence lasted about four seconds, which doesn't sound long, but try it in a boardroom sometime. It's an eternity.
What happened next was interesting. The CEO looked at his COO. The COO looked at the head of digital. The head of digital looked at her laptop. Then someone said, "We'd need to take that offline." We did take it offline. Six weeks later, I got an email saying they were "working through the prioritisation." I never heard back after that. Maybe they cracked it. I doubt it.
They didn't have bad ideas. They had no mechanism for turning ideas into commitments.
The second trap is strategy as consensus. This one's more insidious. It starts with good intentions - you want buy-in, you want alignment, you want the partners or the leadership team to feel ownership. So you workshop it. You iterate. You accommodate feedback. Someone in operations wants to add their priorities. The CFO wants cost reduction front and centre. The head of marketing wants brand. The CTO wants infrastructure.
By the time everyone has had their say, you've got a strategy that offends nobody and commits to nothing. Every priority is a priority, which means none of them are. The bold bet that might have actually moved the needle got softened into "explore opportunities in..." because one person on the steering committee wasn't comfortable with the risk.
Obviously consult people. But there's a difference between consultation and democracy. Strategy requires someone to make choices - real choices, the kind where you're explicitly saying "we're doing this and not that." If your strategy doesn't have a "not that" list, it's not a strategy. It's a wish list with a logo on the cover.
The third trap is strategy as aspiration. This is the one that sounds the most impressive and does the least. "We will become a digitally-led, data-driven, client-centric organisation." Right. By when? With what money? Who's leading it? What does it mean in practice for the person updating the website next Tuesday?
Aspiration without mechanism is just motivation. And motivation fades. Usually around week three, when the first real trade-off appears and nobody wants to make the call.
I've seen firms spend six figures on strategies that were essentially mood boards for the future. Beautiful documents describing a state of being that nobody had worked out how to get to. The gap between "where we want to be" and "what we're doing on Monday" was enormous, and nobody seemed troubled by it. Or if they were troubled, they weren't troubled enough to say so, because the document felt like progress. That's the trap.
Here's what frustrates me about the whole "strategies fail at implementation" narrative. People talk about it like it's some great unsolved puzzle. It's not. The reason most digital strategies fail at implementation is breathtakingly mundane: the things that were planned were never properly resourced, owned, or measured.
That's it. That's the whole mystery.
You can have the most insightful strategy in the world, but if nobody's calendar changed the week after it was approved, nothing's going to happen. If the people supposed to deliver it are the same people already running at 120% capacity on the day-to-day, nothing's going to happen. If success is defined as "improved digital maturity" rather than something you can actually observe and count, you'll never know whether it worked - which, conveniently, means you'll never have to confront the possibility that it didn't.
I remember one firm - mid-market accountancy practice, seven offices - where the digital strategy called for a complete replatforming of their CMS, a new client portal, a CRM integration, a content marketing programme, and an SEO overhaul. All within 18 months. Total budget allocated? About 40% of what the first item alone would have cost. When I pointed this out, the response was something like, "Well, we'll phase it."
Phasing is fine. Phasing is sensible. But phasing requires you to actually choose what comes first, fund it properly, and defer the rest explicitly. What they meant by "phasing" was "we'll figure it out as we go." That's not phasing. That's hoping. And hoping, as a delivery methodology, has a pretty poor track record.
The firms I've seen make genuine progress - the ones where the digital experience actually got better, where the platform actually got replaced, where the data actually started informing decisions - they didn't have better strategies. They had better operating rhythms. They made fewer commitments and kept them. They reviewed what was working every 90 days and adjusted. They had someone - a real person, with a name and a diary - who was accountable for each initiative.
Not glamorous. Doesn't photograph well for the annual report. But it works.
So what should you actually be aiming for? My honest view, and I appreciate it might sound reductive to anyone who's just spent £80k on a strategy document.
An effective digital strategy answers four questions. What exactly will change? By when? Who's doing it, and with what resources? And how will we know it worked?
If your strategy doesn't answer those four questions for every initiative it contains, it's incomplete. Not wrong, necessarily - incomplete. And incomplete strategies are what create that awful six-month drift where everyone technically agrees something should happen but nothing actually does.
"Improve our digital client experience" is not a strategic initiative. It's a vibe. "Reduce the average time from first enquiry to first conversation from 72 hours to under 4 hours by rebuilding the enquiry workflow on the website, led by [name], with a budget of £X, delivered by Q3" - that's a strategic initiative. Specific. Resourceable. Measurable. You can tell whether it happened or not.
I've started applying what I call the one-page test. If your digital strategy can't be summarised - meaningfully, not just as headings - on a single page, it's probably too complex to execute. Not too complex to understand. Too complex to execute. Because execution requires focus, and focus requires constraint, and constraint requires leaving things out.
This makes people uncomfortable. Especially in firms where multiple partners or department heads have expectations. But I'd rather have a one-page strategy with three things on it that actually get done than a 50-page strategy with fifteen things on it that generate twelve months of "in progress" updates before quietly being shelved.
I should be upfront: what I'm about to describe is how we work at Distinction, so take it with whatever pinch of salt you think is appropriate. But I'm describing it because it genuinely solves the problem I've been going on about for the last 1,500 words.
We built a framework called WHNN - pronounced "win" - which stands for The What and the How, for the Now and the Next. The core idea is almost embarrassingly simple. Get clear on what needs to be done. Agree how it'll be delivered - who, with what, by when. Make an honest assessment of where you are today. Define where you need to be in 3, 6, 12 months.
The bit that actually matters, though, is the rhythm. WHNN runs on a quarterly cycle. Every three months, the leadership team comes together, reviews what's working, confronts what isn't, and makes real decisions about where to put time and money for the next quarter. Not a status update. Not a RAG-rated dashboard that everyone glances at and nobody interrogates. An actual decision-making session where priorities get confirmed, adjusted, or killed.
Let me give you a concrete example of what that looks like in practice. We ran a quarterly review with a professional services client last year - about 180 people, four offices - where three initiatives had been sitting at "in progress" for two consecutive quarters. In the room, we went through each one. The first had genuinely moved forward and just needed a budget release to finish. Fine. The second had stalled because the person nominally leading it had changed roles and nobody had reassigned it. That's the kind of thing that sounds obvious in hindsight but somehow never gets surfaced without a forcing function. The third one - a CRM integration that had been on the roadmap for eight months - got killed entirely. Not deferred. Killed. Because when we actually looked at what it would take versus what it would deliver, the numbers didn't stack up anymore. The market had shifted slightly, the original use case had changed, and nobody had been willing to say so because it had been in the strategy document.
That session took three hours. By the end of it, two initiatives had clear owners and funded delivery plans. One was gone. And the leadership team left the room knowing exactly what was happening next quarter and why. That's what a strategy process is supposed to produce - and it happened in a quarterly review, not in the original strategy document.
This creates a forcing function that most strategy processes don't. You can't drift for twelve months because every 90 days you're back in the room, looking at what you said you'd do and what you actually did. That accountability - regular, unavoidable - is what turns strategy from a document into a discipline.
The day job always tries to crowd out the strategic work. Every time, without fail. The only thing that stops it is building a structure that protects the strategic work from the operational noise. Quarterly rhythm does that. A 60-page PDF does not.
Let me ask you something, and I'd genuinely like you to sit with it for a moment rather than reaching for the comfortable answer.
When was the last time your digital strategy directly caused something to happen? Not inspired a conversation. Not informed a brief. Directly caused a specific change - a decision made, a resource allocated, a thing delivered - that wouldn't have happened without it?
If you can point to specific outcomes, brilliant. Your strategy is working. Keep going.
But if you're being honest with yourself and the answer is "I'm not sure" or "it's hard to attribute specific things to the strategy" - then you don't have a strategy. You have a document. And the document is giving you the feeling of progress without the substance of it.
That's not a criticism of you, by the way. It's a criticism of an industry - mine included, at times - that has made strategy production a deliverable in its own right. We've all been part of the machine that treats the deck as the destination. Worth being honest about that, because until you name the pattern, you can't break it.
The firms actually making progress right now - the ones where the website got better, where the client portal works, where the CRM actually talks to the rest of the stack - they're not the ones with the best strategy documents. They decided less, committed more, and reviewed relentlessly. That's the whole thing, really.