Ask most owners of a 20-person company who is responsible for IT and you will hear some version of "whoever is closest to the problem." Laptops get bought when someone's old one dies, software is added one subscription at a time, and security is something to look at "after this busy season." None of this is negligence — it is what happens when technology grows faster than the time anyone has to plan it.
A 12-month IT roadmap fixes that without turning you into an enterprise. It is a short document that answers three questions: what do we have, what is at risk, and what will we change this year — in what order and for how much.
1. Start with an honest inventory
You can't plan what you can't see. Spend an afternoon listing:
- Devices — laptops, desktops, phones and their age. Anything older than five years is on borrowed time.
- Accounts and subscriptions — email, file storage, accounting, CRM, design tools. Note who pays and who is the admin.
- Data — where customer, financial and HR data lives, and whether it is backed up anywhere other than the same service.
- Vendors — internet provider, software resellers, the freelancer who "set up the Wi-Fi."
The inventory usually surfaces quick wins on its own: duplicate subscriptions, ex-employees who still have access, or a single person who holds every admin password.
2. Rank risks by business impact, not by technology
A server that is out of warranty matters only if the business stops when it fails. For each risk, ask: if this broke tomorrow, what would it cost us in a day? Typical top items for small businesses are:
- No multi-factor authentication on email and finance systems.
- Backups that have never been tested with a real restore.
- Admin access concentrated in one person or an outside contractor.
- Old devices without security updates.
3. Turn risks and goals into quarterly themes
Trying to do everything in January guarantees nothing gets finished. Group the work into one theme per quarter — for example Q1: secure the basics (MFA, password manager, offboarding checklist), Q2: move to the cloud, Q3: automate a painful process, Q4: reporting and budget for next year.
A good roadmap fits on one page. If it needs a table of contents, it is a project plan, not a roadmap.
4. Put a number on every line
Each item gets an estimated cost (one-time and monthly) and an owner. Ranges are fine — "$2–4k" is far more useful than "TBD." This is what lets you approve the plan once instead of debating every purchase.
5. Review it every quarter
Business priorities change. A 30-minute review each quarter keeps the roadmap honest: what got done, what moved, and whether next quarter's theme still makes sense.
Where to start
If you only do one thing this month, do the inventory and turn on multi-factor authentication for email. If you'd like a second pair of eyes, our Technology Roadmap Workshop produces exactly this document in half a day.
Tell us about your setup — we reply within one business day.
