Writing an IT roadmap the board will actually fund

Why technology roadmaps get shelved

Most IT roadmaps fail in the boardroom for the same reason: they describe what IT wants to build rather than what the organization needs to achieve. A list of platform upgrades, however sensible, asks directors to trust judgment they cannot evaluate. A roadmap that reads as a plan to serve strategy, manage named risks and spend within a defined envelope is something they can actually decide on.

Consider who reads the paper. Directors have limited time and usually no technical background, but they are practiced at weighing risk, return and opportunity cost. Write to that skill. Use a one-page summary up front, push detail into an appendix, and prefer a simple diagram of three horizons to a dense Gantt chart that invites questions about dates rather than decisions about direction.

Begin with the strategy, in the board's words

Extract three to five priorities from the corporate plan: enter a new market, improve margin, strengthen resilience, meet a regulatory commitment. Use the wording the board already uses. Then ask for each initiative on your list which priority it advances and what would be different in twelve months if it succeeded. Initiatives that cannot answer either question belong in a maintenance budget or off the list.

Talk to business owners first. A roadmap that surprises the chief financial officer or operations lead in the meeting will stall; one they co-authored will be defended by them.

Describe the current state honestly

Give directors a short, plain picture of where technology stands today. Avoid jargon and blame, and include evidence.

• Critical systems approaching end of support and what depends on them.
• Single points of failure and tested recovery times against stated business tolerances.
• Significant findings from audits, assessments or incidents and their status.
• Skills and capacity constraints, including dependence on individuals or vendors.

Organize initiatives into themes with explicit outcomes

Group work into four or five themes, such as Resilience and security, Modern workplace, Data and insight, Customer experience, and Platform foundations. For each theme state the outcome, the measures that will show progress, the dependencies and the principal risk if it is not done. Use measures the business recognizes: hours of downtime avoided, onboarding time reduced, reporting cycle shortened.

Where you lack a measure today, make establishing a baseline the first deliverable. A credible roadmap admits what it does not yet know.

Show cost, options and trade-offs

Present investment as ranges by phase, separating one-time project cost from recurring run cost, and noting the assumptions behind each. For major items offer options: do nothing, do the minimum, recommended approach. Include the consequence of each, including the cost of delay. Directors rarely reject a clearly argued recommendation, but they will push back on a single option presented as inevitable.

Show the cost of inaction in business language too: the outage hours a legacy platform would cost if it failed, the audit finding left open, the revenue that depends on a system approaching end of support. Keep the estimates conservative and clearly labeled as assumptions, so credibility survives the first challenge from a director.

Be explicit about what you are not proposing. Showing that you considered and deferred items demonstrates discipline and builds trust in the items you do ask for.

Prepare for the questions that always come: what happens if we spend half, what happens if we wait a year, who else has done this and what did it really cost. Having a prepared, honest answer to each, including what you do not yet know, signals competence. Rehearse with your finance lead before the meeting so numbers are consistent across every page and every voice.

Phase the plan and build in decision points

Lay the roadmap across three horizons: now (next two quarters, committed), next (following two to four quarters, planned) and later (directional). Fund the first horizon firmly and treat the later ones as options you will revisit. Add stage gates where leadership can continue, adjust or stop, so approval does not feel like writing a blank check.

End the paper with the specific decision you are requesting, the date you need it, and a quarterly reporting commitment against the stated measures. A roadmap that ends with a question the board can answer yes or no to has a far better chance of being funded than one that ends with a summary.