Every long-term entity has a Roadmap. The question is who built yours.
Life has one. A product has one. Infrastructure has one. A business has one. Technology programs have one. Your career has one.
But here’s what most executives never stop to examine: a significant number of the roadmaps you’re operating on right now were never designed by you. They were handed to you. And you followed them anyway — not because you chose to, but because the path was already paved before you arrived.
Think about it.
The milestones of a human life — school, university, first job, mortgage, marriage, children, retirement — these aren’t universally chosen. They’re inherited. Built into the culture, the curriculum, the financial system. The roads you drive on, the platforms your organisation runs on, the processes your team follows — most of these predate your decisions. You stepped into them. You adapted to them. You optimised within them.
That’s not failure. That’s how systems work. The problem is when we mistake following a predefined roadmap for having a strategy.
There are really only four ways a roadmap gets built:
Strategically — You start with your goals and develop the roadmap to reach them. The map serves the destination.
Blindly — You inherit a roadmap predefined for you and follow it without questioning whether it leads where you actually want to go.
Reactively — You develop your roadmap around what’s urgent. Not what’s important. The loudest problems become the plan.
Retrospectively — You build the roadmap backwards, to justify decisions already made. The strategy is written after the knee-jerk. The documentation catches up to the action.
Most organisations — if they’re honest — are operating on some combination of the last three.
The retrospective roadmap is the one that should concern executives most. It looks like planning. The slides are professional. The logic is coherent. But the sequence is inverted. The decision came first. The roadmap was constructed to defend it.
This isn’t dishonesty, usually. It’s the natural result of pressure, speed, and the organisational instinct to protect commitments once made. But it means your roadmap isn’t leading your goals. It’s trailing your ego.
Out of all four approaches, only one is likely to help you achieve what you actually set out to achieve: a strategic roadmap that begins with clarity about where you’re going — before you commit resources, before you sign contracts, before the urgency machine takes over.
It sounds obvious. Most important things do.
The harder question is whether your current roadmaps — across your technology programs, your organisation, your own career — were built strategically, or whether they were inherited, reactive, or constructed after the fact to make sense of decisions already locked in.
Most leaders, when they examine it honestly, find the answer is more complicated than they expected.
Are you ready to look?
This is the work I do with executives sponsoring technology programs — not building the roadmap for them, but helping them see clearly whether the one they’re operating on is actually theirs.
