Technology Roadmap
A technology roadmap lays out, on a timeline, which technology initiatives get built when and why, so investment follows business priority instead of whoever shouts loudest.
Five steps carry you there: an honest audit of the current state, objectives named, initiatives prioritised against them, placed on a timeline, then reviewed as things shift.
Reach for this when…
- Every department has its own wish list and no shared sequence.
- A big technology investment is being justified after the decision, not before it.
- Nobody can say what's being built next quarter and why.
How to run it
- Capture the current state of systems and capability honestly.
- Name the business objectives technology needs to serve.
- Prioritise initiatives against those objectives, not against what's exciting.
- Place initiatives on a timeline with real milestones.
- Review and re-sequence as objectives or technology shift.
A worked example
Situation. Pham Minh Duc led operations at a digital bank in Da Nang, Vietnam where four teams were each quietly building their own version of a customer onboarding fix, unaware of each other.
Applied. He pulled department heads into one room, mapped the current state honestly, and forced every proposed initiative to justify itself against one of three named business objectives before it earned a slot on the timeline.
Result. Two of the four onboarding projects were cut, the surviving one launched on schedule, and the next roadmap review took two hours instead of two weeks of politics.
The catch
A roadmap is only as honest as the prioritisation behind it - without a real filter, it becomes a wish list with dates attached. It also ages fast: a roadmap built once a year and never revisited is a historical document, not a plan.
If every initiative on the roadmap is rated 'high priority', the roadmap hasn't done its job.