Skip to main content
Legia

IT Support & Consulting

Building a Three-Year Company IT Roadmap: Template and Steps

A company IT roadmap is a written plan of which systems to build, fix, or retire over three years, with the order, cost, and owner of each. Here are the steps and a template.

SEO and Content Specialist

6 min read

A consultation discussion in an office lounge

Short answer: a company IT roadmap is a written three-year plan that answers which systems will be built, fixed, or retired, in what order, at what estimated cost, and under whose responsibility. Build it in five steps: a map of the current state, input from the business, a list of initiatives, priorities based on value and effort, then a semester schedule with a budget. Year one is detailed; years two and three are a direction, reviewed each year.

Technology spending is often decided one item at a time, whenever there is a request or something breaks. The result is overlapping systems, contracts that expire unnoticed, and a budget that only appears once a system has become urgent. A company IT roadmap replaces those piecemeal decisions with one document that directors, the IT team, and finance can all read. This article explains what it contains, the five steps to build it, and a template you can copy.

What a company IT roadmap contains

A roadmap is not a shopping list and not a technical architecture document. It holds decisions: what will be done, when, by whom, at what estimated cost, and the business reason. The minimum elements:

  • Current state: the systems in use, their owners, their costs, and their support or contract end dates.
  • Three-year business goals that need technology support, for example opening a branch or a new service.
  • Initiatives: the proposed work, each with a reason, an owner, and a measure of success.
  • Order and schedule by semester.
  • Budget: one-time and recurring costs, kept separate.
  • Risk of postponing, so directors see the consequence of each choice.
Illustration: IT support

Step 1: map the current state

A roadmap starts from facts, not wishes. Build one table of the systems that run today, then fill in the columns most often left empty: the end-of-support date and the contract end date. How to collect the data is covered in How to Build an IT Asset and Software License Inventory.

SystemFunctionBusiness ownerCost per yearEnd of support or contractCondition
(system name)(what it is for)(who)(fill in)(date)(good, needs fixing, needs replacing)

An end-of-support date often becomes a year-one initiative by itself. For example, Microsoft lists Windows Server 2016 as receiving extended support until January 2027, while Windows Server 2022 passed the end of its mainstream support in October 2026 and its extended support runs until October 2031. Servers running such versions need to be in the roadmap, with their deadlines.

Step 2: gather input from the business

Technology supports business goals, so first ask the head of each unit three things: the target for the next three years, the work that takes the most time today, and the recurring complaints about systems. Record the answers as given. A complaint raised by three different units is often more important than one request that sounds sophisticated.

Step 3: turn the input into initiative cards

Every proposed piece of work is written on one card in the same format, so they can be compared with each other.

FieldContent
Initiative nameA short sentence with a verb, for example “Replace servers whose support is ending”
Business reasonThe problem or goal it answers, and the consequence of not doing it
OwnerOne person on the business side responsible for the result
Measure of successSomething that can be checked, not “better”
DependenciesOther initiatives or contracts that must finish first
Estimated costOne-time and recurring, kept separate
Estimated timeDuration of the work and the suggested semester

Also make sure no area is forgotten. The NIST Cybersecurity Framework 2.0 has six functions, Govern, Identify, Protect, Detect, Respond, and Recover, and is designed for organizations of many sectors and sizes. The list can serve as a reminder that a roadmap is not only new systems: backup, recovery, and access management are also initiatives worth scheduling.

Step 4: set priorities with a value and effort matrix

Not every initiative can run at once. The Microsoft Cloud Adoption Framework uses a matrix of business value against effort to sequence the move of workloads to the cloud, and the pattern can be applied to any IT initiative:

Business valueEffortHow to treat it
HighLowDo first, the results show quickly
HighHighStrategic investment, plan with enough resources
LowLowFiller between large pieces of work
LowHighAvoid or postpone

Score business value and effort on each card together with the unit heads, not by the IT team alone, so the order reflects the company’s interests. Initiatives driven by a deadline, such as the end of support for an operating system, move to the top without needing to be rescored.

Step 5: build the semester schedule and the budget

Year one is detailed by semester, year two by year with a general direction, and year three can simply be a goal. Planning in great detail for year three will almost certainly change, so the schedule is deliberately graded in certainty. Here is a template you can copy:

InitiativeOwnerYear 1, semester 1Year 1, semester 2Year 2Year 3One-time costRecurring cost
(initiative 1)(name)(stage)(stage)(direction)(direction)(fill in)(fill in)
(initiative 2)(name)

A few habits that keep the budget readable:

  1. Separate one-time costs from recurring costs. Subscriptions, licenses, and maintenance keep running after the project ends, and their total often matters more than the cost of building.
  2. Include maintenance costs for every new system, not just the cost of building it.
  3. Review the roadmap each semester and update the later years. A roadmap that is not reviewed becomes an outdated document.
  4. Prepare a one-page summary for directors with the main initiatives, the order, the total cost per year, and the risk of postponing.

When outside help is needed

An IT team that runs daily operations rarely has time to build a roadmap, and a view from the inside is often too close to the systems. The signs that make a consultant worthwhile are covered in When Does a Company Need an IT Consultant. Technology planning is one form of work in Legia’s IT Consultant service: arranging the order of work and estimated costs for one to three years ahead. The system review and technology plan generally take 3 to 6 weeks, depending on the number of systems and work units involved. The result is a staged recommendation document that belongs to your company, also listing options that do not involve Legia, together with a one-page summary for a directors’ meeting. Other services in this pillar are on the IT Support & Consulting page.

Frequently asked questions

How often should an IT roadmap be updated?

Review it at least once each semester, and update it when something big changes, such as an acquisition, a new branch, or a serious incident. Year one can shift, while years two and three adjust to the results of the previous year.

Does a small company need a three-year roadmap?

Yes, in a compact form. One page with the main systems, the contract or support end dates, three to five initiatives, and a budget per year is enough. The length of the document follows the number of systems, not the size of the company.

Who should write the roadmap?

The IT team or a consultant writes it, but the owner of each initiative and the one who sets priorities is the business leadership. A roadmap written only by IT tends to be full of technical items not connected to company goals.

What is the difference between an IT roadmap and the annual IT budget?

The annual budget answers how much will be spent this year. The roadmap answers what for, in what order, and what the consequences are over three years, so each year’s budget has the same foundation.

Sources

Category IT Support & Consulting

Keep reading

Related articles

All Articles