A roadmap and a wish list can look similar on paper — both are lists of things you'd like to do with technology. The difference shows up the moment budget season actually arrives, and one of them tells you what to do next.
What's actually in a real roadmap
A real IT roadmap ties each initiative to a business reason, a rough cost, a timeframe, and a dependency — what has to happen first. It's a sequence, not a pile. "Migrate to the cloud" isn't a roadmap item; "migrate email and file storage in Q1, ahead of the office lease renewal" is.
How it differs from a wish list
A wish list grows every time someone has an idea. A roadmap forces tradeoffs — if everything is priority one, nothing is. The discipline of saying "not yet" to some good ideas is what makes the ones you do pursue actually get finished.
How often to revisit it
Quarterly is usually the right cadence for a growing business — often enough to stay realistic about budget and priorities, rare enough that you're not constantly re-litigating the plan. Annual reviews tend to go stale by month four.
The real payoff
The value of a roadmap isn't the document itself — it's the conversation it forces before money gets spent. Organizations with one make fewer reactive purchases, and the ones they do make are easier to justify after the fact.