Consulting

IT roadmap: how to prioritise your digital projects

How to build an IT roadmap for 12 to 36 months: score each project on value, effort and risk, order by dependencies, phase the budget, review quarterly.

Every leadership team has a list: a new CRM, a customer portal, a cleaner way to invoice, a dashboard for the board, something with AI. The list grows faster than the budget, and the loudest request often wins. An IT roadmap fixes that. It turns needs into a short sequence of projects over 12 to 36 months, chosen on value, effort and risk, ordered by what depends on what, and paid for in phases.

In this guide we show how we build one with our clients: where to start, how to score projects with a simple value/effort grid, how to phase the budget, and how to keep the plan alive with a quarterly review.

What an IT roadmap is, and what it is not

An IT roadmap is a dated, ordered list of the technology projects your business will run, with the reason for each one, its rough size and its place in the budget. It fits on two pages. Anyone on the leadership team should be able to explain why project B comes after project A.

It is not a shopping list of tools, a five-year master plan nobody reads, or a technical architecture document. The roadmap answers three questions only:

  • What do we do, and why does it matter to the business?
  • In which order, given our budget, our people and what depends on what?
  • When do we check that the order is still right?

A good roadmap also says what you will not do. Saying “not this year” to a project, in writing, is often its most useful line.

IT strategy for small business: start from needs, not solutions

For a small or medium-sized enterprise (SME), IT strategy does not need a thick document. It needs a shared view of the problems worth solving. That is why we never start a roadmap from a list of products. The same is true of digital transformation in an SME as a whole: it is about changing how the business works, not buying software, and the audit and the roadmap are among its first steps.

1. Take stock of what you have

Before ranking new projects, know your starting point: which applications you use, who uses them, where the data lives, what is fragile and what each tool costs. If nobody has that picture, an IT audit is the natural first step, and its report feeds the roadmap directly.

2. Collect needs in business language

Interview each team lead for 30 minutes. Ask what slows them down, what they re-type, what they cannot see, and what they fear will break. Write each answer as a need, not a solution: “we lose track of quotes after they are sent”, not “we need a CRM”. The same need can be met by a setting in an existing tool, a subscription or a custom application; choosing comes later, and our article on off-the-shelf or custom software helps with that choice.

3. Group needs into candidate projects

Several needs often point to the same project. Three complaints about quotes, follow-ups and lost leads may form one “sales pipeline” project. Aim for 8 to 15 candidates: fewer means you have merged too much, more means you have not grouped enough.

Scoring projects on value, effort and risk

This is the heart of a digital transformation roadmap: a short, explicit scoring that everyone can challenge.

Value

Score from 1 to 5 how much the project helps the business: time saved, errors avoided, revenue protected or won, a legal or contractual obligation met, a risk removed. A legal deadline or a system about to lose support can justify a 5 on its own.

Effort

Score from 1 to 5 the size of the work: budget, internal time, number of teams involved, data to move. You do not need a precise estimate at this stage, only a consistent order of magnitude. When a project rises to the top, a proper estimate follows; our guide to software project estimation explains how.

Risk

Score from 1 to 5 what could go wrong: unclear requirements, a dependence on a single supplier, sensitive data, a team already overloaded. Risk does not disqualify a project; it tells you to start it with a small first phase.

The value/effort scoring grid

Divide value by the average of effort and risk. The higher the ratio, the earlier the project tends to come.

Illustrative example (fictitious figures) for a 40-person services company:

Candidate project Value Effort Risk Priority score* First reading
Replace the shared quote spreadsheet with a simple sales pipeline 4 2 1 2.7 Quick win: early
Automate monthly reporting for the board 3 2 2 1.5 Early, after the data is cleaned
Customer portal for document exchange 4 4 3 1.1 Phase it: start small
Replace the ageing accounting system 5 5 4 1.1 Plan it now, run it next year
AI chatbot on the website 2 3 3 0.7 Not this year

*Value ÷ ((Effort + Risk) ÷ 2), rounded.

The score is a starting point for discussion, not a verdict. If the leadership team disagrees with a line, the conversation that follows is exactly what the grid is for.

Ordering projects by dependencies and phasing the budget

A high score does not mean “start Monday”. Some projects need others first.

Map the dependencies

For each project, ask: what must exist before this works? A board dashboard needs clean customer data. A customer portal needs a reliable client database behind it. A new ERP needs its data cleaned and its processes agreed. Draw arrows between the cards; the order often becomes obvious.

Split large projects into releases

A large project rarely needs to arrive all at once. Define a first release that delivers value on its own, then plan the rest. When our founder, Anass Chabbab, in his previous role as IT director of DIGIIT Solutions (2019–2022), led a custom CRM/ERP for a Sydney law firm, the first release went live in under 6 months. The application went on to serve 100+ users and cut processing time by 40%. Read the case.

Phase the budget

Lay the projects on a timeline of quarters and check three limits for each quarter:

  • Money: the total stays within what you can commit, with a margin for the unexpected.
  • People: the same key people are not needed by three projects at once.
  • Change: teams can absorb only so much new software at the same time.

Year one is detailed by quarter. Year two is a list of projects in rough order. Year three, if you plan that far, is a list of intentions. Precision should fall with distance.

Keeping the roadmap alive: the quarterly review

A roadmap written once and filed away is out of date within months. Put a 90-minute review in the calendar every quarter, with the same small group.

At each review:

  1. Check delivery: what finished, what slipped, and why.
  2. Check value: did finished projects deliver what their card promised? If not, what do you change?
  3. Add new needs: score them on the same grid, no shortcuts for urgent-sounding requests.
  4. Re-order: move projects up, down or out, and update the budget phasing.
  5. Write the decisions down, with a date, so the next review starts from facts.

Once a year, step back and check that the roadmap still matches the business plan. If the company has changed direction, the roadmap must too.

Frequently asked questions

How long should an IT roadmap cover?

Usually 12 to 36 months. Twelve months suits a small business with a few clear projects. Beyond 18 months, keep only year one detailed by quarter and treat later years as an ordered list that the quarterly review refines.

Is there a technology roadmap template we can use?

A spreadsheet is enough. One tab lists the candidate projects with their need, value, effort, risk, score and dependencies. A second tab lays the selected projects across quarters with their budget. A third records the decisions of each review. The template matters less than the habit of scoring every new request the same way and reviewing it on schedule.

Who should own the IT roadmap?

One named person on the leadership team, with the authority to say no. In many SMEs nobody has that role full time. Some appoint a fractional CIO, an experienced IT leader for a few days a month, to run the scoring and the quarterly reviews; others keep it with the managing director and bring in outside help only to build the first version.

In short

An IT roadmap turns a long list of ideas into a short, ordered plan over 12 to 36 months. Start from needs and from an honest picture of what you have, score each project on value, effort and risk, order them by dependencies, and phase the budget with year one detailed by quarter. Then review it every quarter, so the plan follows the business instead of the other way round.

More project ideas than budget? Book a free 30-minute discovery call: we look at your list together and help you see which projects to run first. You can also see how we approach custom software once a project reaches the top.

Related servicesCustom software

Have a project in mind?

Let’s talk about it on a 30-minute discovery call, free and with no obligation.

Book a discovery call

Further reading

All articles