Most roadmaps gather dust because they're built as planning exercises, not execution tools. Here's what yours needs to survive contact with shifting priorities and politics.
Every firm I've ever worked with has had a roadmap at some point. A surprising number have had several. They're usually sitting in a shared drive somewhere - a beautifully formatted PowerPoint from 2022, maybe a Gantt chart that someone built in Smartsheet during a particularly optimistic offsite, occasionally a Miro board so dense with sticky notes it looks like abstract art.
And almost none of them are being followed.
I want to start with a specific one, because it's the one that still bothers me. A consulting firm, about 150 people, had a roadmap I'd helped them build. Solid thinking, reasonable ambition, phased sensibly. We'd spent two days getting the priorities right. Six months later I asked how it was going. The managing partner said "really well, we're making progress." I asked what had shipped. Long pause. "We've been doing a lot of groundwork."
Nothing had shipped. The roadmap was still in the deck. The groundwork was real - meetings, discussions, a couple of vendor conversations - but nothing had actually been delivered. And the reason wasn't that the priorities had changed or the budget had disappeared. It was that the roadmap had been built as a planning exercise rather than an execution tool. Nobody owned anything specific. There were no success measures anyone could point to. And the quarterly rhythm we'd agreed on had quietly been replaced by "we'll pick this up when things calm down."
Things never calm down. That's not a cliché - it's the actual operating condition of every mid-sized firm I've ever worked with.
_We have a roadmap. It's just that priorities keep changing._
I hear this constantly. And I'm sympathetic - priorities genuinely do change. But when I dig into what actually happened, the roadmap didn't fail because priorities shifted. It failed because it was built in a way that couldn't absorb shifting priorities. Rigid where it needed to be flexible, vague where it needed to be specific, and - most commonly - completely disconnected from the way the organisation actually makes decisions and allocates resources.
So let's talk about what a digital roadmap actually needs to look like if you want it to survive contact with reality.
They tend to break for the same reasons, and I've seen enough of them to spot the patterns early now.
The first is over-ambition in Phase 1. Someone gets excited during the planning process and the roadmap tries to solve everything simultaneously. New website, CRM integration, client portal, content strategy, analytics overhaul, accessibility remediation - all in the first six months. It's like renovating your kitchen, bathroom, and loft at the same time with one builder and a budget that was really only enough for the kitchen. Everything gets started, nothing gets finished, and you're eating takeaway in the hallway for a year.
The second is no connection to measurement. The roadmap says "improve digital experience" or "modernise the platform" but never defines what success looks like in terms anyone can actually track. So three months in, when someone asks how the roadmap's going, the answer is always some version of "we're making progress." Which is meaningless. Without clear success measures per phase, you can't tell whether you're on track, behind, or wasting money.
The third - and this is the one that kills more roadmaps than the other two combined - is that the plan doesn't account for how the firm actually operates. A roadmap built in isolation from the organisation's decision-making rhythm, budget cycles, and internal politics is a fantasy document. If your firm approves budgets annually in September but the roadmap assumes rolling quarterly investment, it's dead on arrival. If the roadmap requires marketing, IT, and the partnership to collaborate closely but those three groups haven't agreed on anything since the office Christmas party, you've got a problem that no Gantt chart can solve.
Right, let's get practical. If you're building a digital roadmap - or more likely, rebuilding one after the last one gathered dust - here's what needs to be in it.
**Phased priorities, not a wish list.** A roadmap is not a backlog. It's not "everything we'd like to do, roughly ordered." It's a deliberately sequenced set of initiatives where each phase has a clear scope, a realistic timeline, and a defined outcome. Three to four phases over 12-18 months is usually about right for a mid-sized firm. More than that and you're kidding yourself about your ability to predict the future.
Each phase should answer five questions: What specifically are we doing? Why now rather than later? What does it depend on? Who owns it? And - the one where most roadmaps fall apart - how will we know it worked?
"Launch new website" is not a success measure. "Increase qualified enquiries from the website by 30% within six months of launch" is. The difference matters enormously, because it forces you to think about whether the thing you're building will actually move the numbers you care about. It also means that when someone asks how Phase 1 went, you have an actual answer.
Dependency mapping. This sounds technical but it's really just common sense written down. If Phase 2 requires a CRM integration, and Phase 1 doesn't include cleaning up your CRM data, then Phase 2 is going to go badly. I worked with a professional services firm last year that had a perfectly good roadmap on paper - new site in Q1, portal in Q2, personalisation in Q3. Except the personalisation work needed clean client segmentation data that lived in a CRM that hadn't been properly maintained since 2020. Nobody spotted the dependency until they were halfway through Q2, and the whole thing slid by four months.
Write down what each phase needs to be true before it can start. Then check whether the preceding phase actually delivers that. If it doesn't, you've found a gap.
Realistic timelines based on your capacity, not your ambition. How many people do you actually have who can work on this? Not theoretically. Actually. If your marketing team is three people and they're already running events, managing social, and producing thought leadership, they cannot also lead a website redesign. I've seen firms put together 12-month roadmaps that would require roughly twice the capacity they have. When I point this out, the usual response is "we'll bring in contractors" or "we'll reprioritise other work." Neither of those things happens without explicit planning and budget. So either plan for the contractors - their cost, the ramp-up time, the management overhead - or reduce the scope to match what your existing team can actually deliver.
Ownership that's specific enough to be enforceable. "Marketing leads Phase 1" is not ownership. "Sarah Chen, Head of Digital Marketing, is accountable for Phase 1 delivery, with a fortnightly check-in with the COO" is ownership. The difference is that the first version allows everyone to assume someone else is handling it. The second version means Sarah knows she's going to be asked, in person, every two weeks, whether things are on track.
I was working with a mid-market law firm a couple of years ago where the roadmap assigned ownership to departments rather than individuals. Six months in, I asked who was responsible for the CMS migration that was supposed to have started in Q2. Three different people said it was someone else's job. The meeting was one of those quietly excruciating ones where everyone in the room knew the answer and nobody wanted to say it first. Classic.
Here's something that rarely makes it into articles about roadmaps: the biggest obstacle to execution is usually internal politics, not technical complexity.
A digital roadmap touches multiple departments. Marketing wants the website rebuilt. IT wants the platform modernised. The partners want the client portal improved. Finance wants to understand the ROI before committing budget. And everyone thinks their priority should be Phase 1.
If you don't address this head-on during the planning process, you'll end up with one of two outcomes. Either the roadmap tries to please everyone and becomes that over-ambitious monster I described earlier. Or the most politically powerful person in the room wins, the roadmap reflects their priorities, and everyone else quietly disengages.
The way to handle this is unglamorous but effective: bring the competing stakeholders into the prioritisation process and make the trade-offs explicit. Not "what do you want?" but "given that we can realistically deliver two major initiatives in the next six months, which two matter most and why?" Force the conversation. Make people argue for their priority against someone else's. It's uncomfortable, but it produces a roadmap that has genuine buy-in rather than one that everyone nods at and then ignores.
I remember sitting in a planning session with a consulting firm where the head of IT and the CMO had been arguing about whether the first phase should be a CRM cleanup or a website redesign. They'd been having this argument informally for months, each lobbying the managing partner separately. We put them in the same room, mapped out the dependencies, and it took a while - longer than I'd expected, and there was a point where I thought the IT lead was going to walk out - but eventually they both saw that the CRM cleanup had to come first because the website redesign depended on clean data for the personalisation they both wanted. The disagreement wasn't really about priorities. It was about a dependency neither of them had articulated out loud.
That kind of conversation doesn't happen unless someone creates the space for it.
Building the roadmap is actually the easy part. The hard part is stopping it from becoming irrelevant within three months.
The mechanism we use at Distinction is a quarterly review cycle - we call it WHNN, the What and the How, for the Now and the Next. The principle is straightforward: every quarter, bring the leadership team together to review what's been delivered, assess what's changed, and make deliberate decisions about what happens next. It works because it builds in the assumption that things will change. The roadmap becomes a living document that gets updated every 90 days based on what you've learned, rather than a fixed plan you either follow or quietly abandon.
A typical quarterly review covers three things. First: what did we actually deliver last quarter, and did it produce the outcomes we expected? Not "what did we work on" but "what shipped." If Phase 1 was supposed to increase enquiries by 30% and it increased them by 12%, that's useful information. Maybe the target was unrealistic. Maybe the execution was off. Maybe the measurement is wrong. Either way, you need to know before you commit to Phase 2.
Second: what's changed since we last planned? New competitive threat, budget pressure, a key person leaving, a regulatory change, an AI development that makes one of your planned initiatives either more urgent or less relevant. These aren't excuses to abandon the roadmap - they're inputs that might change the sequencing or scope.
Third: what are we committing to for the next 90 days? Specific deliverables, specific owners, specific success measures. Not "continue with Phase 2" but "complete the CRM data migration by end of March, with Sarah leading, and success defined as 95% of active client records cleaned and categorised."
The quarterly rhythm does something psychologically important too. It gives people permission to adjust without feeling like they've failed. When the roadmap is treated as sacred and immutable, any deviation feels like a defeat. When it's explicitly designed to be reviewed and updated every quarter, changing course becomes part of the process.
Not every roadmap can be saved with a quarterly tweak. Sometimes you need to stop, acknowledge that the plan is no longer fit for purpose, and start again. That feels like failure, but it's usually the smartest thing you can do.
The foundational assumptions have changed. If the roadmap was built around a specific platform and you've since discovered that platform can't do what you need, iterating within the existing plan is pointless. I've seen firms spend two quarters trying to make a failing approach work because nobody wanted to admit the original decision was wrong. Sunk cost dressed up as commitment.
You've lost the people. If the person who was driving execution has left, and their replacement has a fundamentally different view of priorities, forcing the new person to follow the old roadmap is a recipe for passive resistance and poor outcomes.
The business context has shifted materially. A merger, a major client loss, a funding round, a regulatory change - any of these can make a roadmap obsolete overnight. When we worked with a top-20 accountancy firm that had been through three mergers in two years, the pre-merger digital roadmap was completely irrelevant. They needed to consolidate four websites and four CMS platforms before they could even think about the initiatives on the original plan.
And then there's AI. Firms that built roadmaps eighteen months ago without accounting for it are now finding that entire phases need rethinking. Not because AI is a magic bullet - it isn't - but because it changes the cost-benefit calculation on things like content migration, personalisation, and data processing in ways that weren't foreseeable when those plans were written.
If any of these apply, don't keep patching. Spend two weeks doing a fresh assessment, rebuild from current reality, and go again.
I promised practical, so here's roughly how I'd structure a 12-month digital roadmap for a mid-sized professional services firm. Your priorities will be different, but the structure holds.
Months 1-3: Fix what's broken and establish measurement. Don't start with the exciting stuff. Start with whatever is actively costing you money or clients right now. Broken enquiry forms, a contact process that takes three days, a portal that doesn't work on mobile. Simultaneously, get your analytics in order so you can actually measure whether subsequent phases are working. It's dull. It's essential.
Months 4-6: Deliver the highest-impact initiative. This is usually the website or the client-facing experience. Pick the one thing that will make the biggest measurable difference and do it properly. Resist the urge to bolt on three other things while you're at it.
Months 7-9: Build on what's working and address the next dependency. If Phase 2 was the website, Phase 3 might be CRM integration or a content strategy. Use the data from Phase 2 to validate your assumptions before committing.
Months 10-12: Optimise and plan the next horizon. By now you've got nine months of data, three completed phases, and a much clearer picture of what matters. Use this phase to optimise what you've built and plan the next 12 months with actual evidence rather than optimism.
After each phase, run the quarterly review. Adjust. Recommit. Keep moving.
A plan tells you what to do. A roadmap tells you where you're going and roughly in what order - while accepting that the route will change, because it always does.
The firms that get this right aren't the ones with the most sophisticated planning tools or the biggest digital budgets. They're the ones with the discipline to phase honestly, measure what actually matters, review regularly, and change course when the evidence says they should. And - maybe most importantly - the ones who are willing to have the uncomfortable conversation about why last quarter's roadmap is sitting untouched in a shared drive.
If you've read this far and you're thinking about that PowerPoint from 2022: open it. Be honest about what's still relevant. Start again from where you actually are, not where you planned to be.