What a roadmap is for
A roadmap has one job: to make the next decision easier. When a vendor calls, a manager requests a tool, or a spreadsheet breaks, the roadmap tells you whether that request fits this year’s priorities or waits. Without one, every request is urgent and technology spend follows whoever spoke last.
It is also a communication tool. A one-page roadmap on the wall tells the whole team what is coming, which reduces the shadow-IT problem of everyone adopting their own tools.
The one-page template
| Section | What goes in it | Keep it to |
|---|---|---|
| 1. Current state | The systems you run, who owns each, what they cost, and the top three pain points people actually complain about. | One table, 6–10 rows |
| 2. Objectives for the next 12 months | Business outcomes, not tools. “Close the month in 5 days instead of 15.” “Answer any customer status query without asking someone.” | Three, maximum |
| 3. Now / Next / Later | Initiatives grouped by horizon. Now is in progress or starting this quarter; Next is the following quarter; Later is acknowledged but not scheduled. | 2–3 items per column |
| 4. Owners | One named person per initiative. Not a department. | A name beside every item |
| 5. What we will stop doing | Tools to retire, reports nobody reads, processes replaced by an initiative above. | Two or three lines |
| 6. Guardrails | Annual budget envelope; rules such as “no new tool without a named owner” or “anything touching customer data goes through a review.” | Three to five bullets |
| 7. Review date | When the page will be revisited — quarterly is the right cadence for most small teams. | One date |
Filling it in: a practical order
- Start with pain, not ideas. Ask five people what wastes their time each week. Patterns appear quickly and they are usually about information not being where it is needed.
- Write the three objectives as measurable outcomes. If you cannot say how you would know it worked, rewrite it.
- Map initiatives to objectives. Anything that does not serve one of the three goes to Later or is dropped.
- Sequence by dependency and value. Data clean-up usually comes before dashboards; a single source of customer records comes before automation that relies on it.
- Size the Now column honestly. A team under 50 people can typically absorb one significant change per quarter alongside normal work. Two is ambitious; three is a plan to finish none.
Common first initiatives for small teams
- One reliable place for customer or order records, replacing three spreadsheets and a WhatsApp group.
- A status dashboard so the founder stops being the reporting system.
- Connecting the accounting package to the operational system so invoices are not typed twice.
- Automated reminders and alerts for the follow-ups that currently depend on someone remembering.
- Access and permissions clean-up — who can see what, and removing accounts of people who have left.
None of these are glamorous. All of them free up hours every week, and each one makes the next initiative easier because the data underneath is cleaner.
Keeping it alive
The roadmap fails when it is written once and filed. Put the quarterly review in the calendar now. At each review: move items between columns, record what shipped, retire what is no longer relevant, and update the three objectives only if the business has genuinely changed direction.
Keep the page to one page. If it grows, that is a signal to cut, not to add a second page.
Want a roadmap built with you, not for you?
Our Technology Roadmap Sprint produces exactly this page — plus the workflow review behind it and a scoped plan for the first item — in one to two weeks of focused work with your team.