IT roadmap template — editable, free
An IT roadmap is mostly about what you are turning off. This template gives every item a lifecycle — adopt, upgrade, replace or retire — across four parts of the estate, saves a view of nothing but the retirements, and marks vendor end-of-support dates as milestones, not estimates.
| View | Groups by | Visible fields |
|---|---|---|
By lifecycle (board) | Lifecycle | Name, Estate, Owner, End |
Leadership (timeline) | Estate | Name, Lifecycle, Start, End |
What is being turned off (timeline) | Estate | Name, Lifecycle, Start, End, only Retire |
All items (table) | Nothing — one flat list | Name, Estate, Lifecycle, Status, Owner, End |
What is an IT roadmap actually for?
Making removals visible. Everything else on the estate has somebody asking for it — a new tool has a sponsor, an upgrade has a vendor reminder, a laptop refresh has people complaining. Retirements have nobody, which is why the on-premise directory that should have gone two years ago is still running and still in scope for every audit.
So lifecycle is the primary field here, and one of the four saved views shows nothing but the retirements. That view is the reason to keep this document.
What is in this template?
Ten items across four parts of the estate — identity, endpoints, network and business apps — each marked adopt, upgrade, replace or retire, at quarter resolution.
One milestone is a vendor’s date, not yours: Windows 10 support ending. Those are the only items on an IT roadmap with no negotiation available, and drawing them as milestones says which parts of the year have a wall at the end of them.
One item is blocked on a finance system upgrade owned by another function. It stays on the page at its real length, because a delay that isn’t yours still needs to be legible as a delay.
Who is this shown to?
Rarely the people doing the work. An IT roadmap travels to a leadership group, a risk committee and whoever signs off spend, and it’s usually forwarded rather than presented. Roadmap for stakeholders is about designing for the reader who gets the picture and a subject line and nothing else.
At the top of that chain the filter gets harsher again. Board meeting roadmap sets out why status and owner come off for a room that carries a duty to oversee — at a board, a blocked item is something the room is now on record as having seen.
For the same horizon organised by where the money went, an annual roadmap template groups by investment area. For the systems inside the product rather than around it, an engineering roadmap template draws the dependency chain. And for the people programmes that run alongside all of it, an HR roadmap template marks what comes round every year.
Common mistakes
Only recording what you’re adding. Nobody requests a retirement, so it never happens unless it’s on a page somebody reviews, and the estate grows by one system a quarter forever.
Treating a vendor end-of-support date as an estimate. It’s somebody else’s date with no negotiation available, and the only useful response is to work backwards from it.
Grouping by project. Projects end and the estate doesn’t, so a roadmap grouped by project has to be rebuilt every year and loses the history of what was replaced.
Leaving the tools nobody owns off the page. Unowned software is the part of the estate that surprises a security review, and naming it’s most of the work of retiring it.
Questions
Why lifecycle instead of priority?
Because lifecycle is the field that determines everything else. A retirement needs a migration path and a date; an adoption needs a pilot. Priority tells you the order and nothing about the shape of the work.
How far out should an IT roadmap go?
Twelve to eighteen months, because hardware refreshes and contract renewals run on that cycle. The far end carries quarters and no promises.
What about the things blocked on somebody else?
Mark them blocked and leave them at their real length. An item waiting on a finance system upgrade that isn’t yours to schedule is information a leadership audience needs, and hiding it makes the delay look like yours.
Related
- Annual roadmap templateFour calendar quarters grouped by where the money goes, with confidence on every item and a board view.
- Roadmap for stakeholdersBuild for the reader three forwards away, and show only the dependency they owe you.
- Board meeting roadmapFive or six bets, the quarter each lands in, and nothing a board would be obliged to chase.
Last updated