Can an IT Roadmap Fit on One Page? Five Questions for a 12-Month Plan
A lot of companies have no IT plan. What they have is a backlog scattered across inboxes and heads: “someone should look at that server”, “let’s sort out backups”, “when did that licence expire again?” As the list grows, the loudest item wins, not the most important one.
A roadmap is just that list, put in order. It does not need to be a thick document. One page, finished before the year closes, changes the budget conversation that starts in January.
Start with five questions
Whatever the size of the company, I begin with the same five. Each answer should fit in one sentence. If it doesn’t, that is where the real work is.
- Which system, if it stops, stops the business? ERP, email, file server, phone system. Write them down; everything else is secondary.
- If those systems fail, how fast and with what data do you come back? Not “we have backups”, but “last night’s state, within half a day”.
- Which product loses support or licensing this year? Put the dates in one table. I covered that exercise in a separate post.
- Who holds the knowledge? If one person knows the passwords, the network diagram and the vendor contacts, that is a risk item in itself.
- How will the company change next year? A new branch, a move, headcount growth, a new ERP. The IT plan follows the business plan, never leads it.
Turn the answers into a table
For each item three columns are enough: what, who owns it, which quarter. A fourth column for rough cost helps, and a range is fine.
| Quarter | Typical work | Why then |
|---|---|---|
| Q1 | Migrate what loses support, restore test for backups | Fixed dates and highest risk go first |
| Q2 | Close security gaps, sort out admin rights | User-facing changes while workload is lower |
| Q3 | Infrastructure refresh (server, network, UPS) | Summer, usually more tolerance for downtime |
| Q4 | Next year’s budget, inventory refresh | The cycle closes and the plan renews |
This split is not fixed. If your business has a peak season, do not schedule user-facing work into it. For a retailer October to December is a no-touch window; for an accounting office it is March and April.
Which item goes first?
With ten items on the table, I rank them with three questions:
- Does the deadline come from outside? Microsoft states that extended support for Windows Server 2016 ends on 12 January 2027. Dates like that are not yours to move, so they go first.
- If it fails, does the business stop? Backup and restore work is one. You do it when nothing is wrong, because once something is wrong there is nothing left to do.
- Is it small but constantly annoying? Slow network, a printer that drops off, the same wait every morning. These are not big projects, but they decide how much staff trust IT. Put one in every quarter.
Three common mistakes
Cramming everything into one year. Twelve months fit about six big jobs, not twelve. Keep the rest on a second list.
Letting IT write it alone. Some questions belong to management: how much continuity matters, which system is non-negotiable. Written by IT alone, the plan becomes a technical wish list.
Writing it and walking away. A thirty-minute review every quarter keeps it alive. Tick off what is done, add what is new, note why things slipped.
FAQ
Who prepares the roadmap if we have no IT team?
If you use an outside provider, ask them for it. With a managed IT service the inventory and monitoring data already exist, so a first draft can take a few days. If your provider has never offered one, that tells you something too.
Is a roadmap the same as an IT budget?
No. The roadmap answers what gets done and in which order; the budget answers what you set aside for it. With the roadmap first, the budget discussion is about work, not numbers.
What if something urgent comes up mid-year?
It will, and that is normal. The plan tells you where the urgent item goes: what you postpone and what you protect. Without a plan, every urgent job quietly eats the time of another one.
If you would like to draft a one-pager together, get in touch.
Related Posts
What Happens to Servers and Switches in a Power Cut? UPS Sizing and Care
When the office power drops for one second, what happens to the server, switches and NAS? A walk through UPS types, how to size capacity, when to replace the batteries and the yearly load test that tells you the truth before an outage does.
Read more: What Happens to Servers and Switches in a Power Cut? UPS Sizing and Care
Is It Time to Replace Your Server? Seven Signs to Check
Age alone does not decide it. Software support dates, warranty, disk health, backups and capacity tell you whether to replace the server, move to the cloud or safely wait another year.
Read more: Is It Time to Replace Your Server? Seven Signs to Check
IT Infrastructure Audit: What It Covers and What Turns Up in Week One
What an infrastructure audit actually looks at, from backups and admin accounts to servers nearing end of support, how long it takes, and how to rank the findings so the report leads to action instead of a drawer.
Read more: IT Infrastructure Audit: What It Covers and What Turns Up in Week One