Four dollars in five keep the lights on
The US Government Accountability Office has looked at what federal agencies spend on information technology many times, and the shape keeps coming back the same. It reported the split in 2019 and 2021 3, and again in 2025: "agencies have typically reported spending about 80 percent on operations and maintenance of existing IT" 1. Four dollars in five go to running what already exists. One goes to anything new.
The government is required to plan this money. Its rules say each agency "shall develop and maintain an IRM Strategic Plan that describes the agency's technology and information resources goals," and that the plan "must support the goals of the Agency Strategic Plan" 2. Many companies keep a version of the same document. And many versions, public and private, share a habit: they spend their pages on the new projects and a line or two on the systems that absorb most of the money.
That is backward. The biggest decisions in an IT plan are usually not what to build. They are what to stop running, what to replace before it fails, and what the existing systems will not let the business do. A plan that skips them is planning a fifth of the budget.
The most strategic line in an IT plan is often the one that says what you will stop running.
Why most IT plans read as shopping lists
IT plans are usually written by collecting requests. Each business unit asks for its systems; the technology team estimates and sequences them; the result is a roadmap of projects with dates and costs. It is useful as a schedule. It is not a strategy, because it never asks whether those are the right projects, or whether the money tied up in existing systems should be freed to pay for them.
A strategic plan does three things a project list does not. It connects each investment to a business priority, so a board can see which priorities have technology behind them. It puts the run budget on the table, system by system, so it can be cut as well as added to. And it says where the existing systems limit the strategy, which is often the most valuable thing the technology team knows. For the thinking behind this, see technology strategy.
The template: the plan on a page, then the run review
| Section | What to write |
|---|---|
| 1. The business priorities it serves | The three to five corporate priorities this plan exists to support, quoted from the corporate strategy, with the capability each needs. |
| 2. What technology has made possible | Two or three shifts since the last plan that could change what the business offers or what it costs, each with what it would let the business do. |
| 3. Where our systems hold the strategy back | Named systems, the strategic choice each limits, and what it would take to remove the limit. |
| 4. The run budget, and what we will change in it | Total spent running existing systems, and the keep, replace and retire decisions from the run review below, with the money each frees. |
| 5. The change budget, by priority | Each new investment, the business priority it serves, its cost and its owner. Any priority with no investment against it, named. |
| 6. The roadmap | Quarter by quarter for the first year, half-year by half-year after: what starts, what finishes, what is retired. |
| 7. Risks we are carrying | Systems past support, security exposures, single points of failure, key-person dependencies, each with an owner. |
| 8. How we will decide and measure | Who decides when priorities conflict, the review rhythm, and the measures that show the plan is working. |
| Column | What to write |
|---|---|
| System | The application or platform, as people call it. |
| Cost a year | Licenses, hosting, support and the people who keep it running. |
| Business process it serves | In business words: billing, onboarding, scheduling. |
| Business owner | The person who would notice if it stopped. |
| Condition | Healthy, aging, past support, or blocking a priority. |
| Decision | Keep, invest, replace or retire. |
| Reason and date | One sentence, and when the decision takes effect. |
How to fill it in
- Start with the run review, not the wish listList every system that costs real money to run, with its cost and its business owner. Most teams find systems nobody owns; those are the first candidates to retire.
- Quote the business priorities, do not paraphrase themCopy them from the corporate strategy. If you cannot find three priorities clear enough to quote, raise that before writing the plan; see the strategic plan template.
- Write the 'made possible' and 'held back' sections before the roadmapThey are the sections the business most needs from you and the ones most often skipped. Keep each item to what it would let the business do, or stop it doing.
- Fund priorities, not requestsEvery change investment names the priority it serves. A request that serves none waits, however loud its sponsor.
- Show the money movingReport the split between running and changing this year and next. If retiring systems frees money, show where it goes.
- Put the roadmap lastDates follow decisions. A roadmap drawn first turns into the strategy by default.
A filled-in example
The example is invented to show the shape. The point it illustrates is real: the plan's most important sentence is about the old policy system, not the new portal, because the old system decides how fast the growth priority can move.
Keep it short, and revisit it
Eight sections and one table can fit in ten pages. If yours runs to fifty, the strategy is buried in the inventory; move the inventory to an appendix. Review the run table every quarter alongside the business review, and rewrite the plan each year after the corporate strategy, not before it; see the annual planning cycle.
For the roadmap itself, the strategic roadmap template shows how to draw the points where you will decide, not just the dates where things finish.
Before you send it
- Every business priority is quoted from the corporate strategy, and every change investment names one.
- The run budget is shown, system by system, with keep, replace and retire decisions.
- At least one system is being retired, or the plan says why none can be.
- The 'held back' section names real systems and real limits.
- Any priority with no technology investment against it is named, not hidden.
- The roadmap follows the decisions, and each item has an owner.
- Someone outside IT has read it and can say what it means for their part of the business.
IT strategic plan template
A free, editable Word document built from this guide: the template itself, how to fill it in, and the worked example and review checklist where the guide has them. Stratrix branded, and sent to your work email.
Questions
- What should an IT strategic plan include?
- The business priorities it serves, what technology has made possible, where existing systems limit the strategy, a review of the run budget with keep, replace and retire decisions, the change budget by priority, a roadmap, the risks carried, and how decisions and progress will be governed.
- How much of an IT budget goes to running existing systems?
- For the US federal government, about 80 percent, according to the Government Accountability Office. Wherever the share is that high, a plan that lists only new projects leaves most of the money unexamined.
- What is the difference between an IT strategic plan and a technology roadmap?
- The plan sets out the decisions: which priorities to support, what to keep, replace or retire, and how to split the money. The roadmap schedules the resulting work over time. A roadmap without the plan behind it is a list of projects.
- How often should an IT strategic plan be updated?
- Rewrite it each year after the corporate strategy is set, and review the run budget and roadmap every quarter alongside the business review.
Sources
- US Government Accountability Office (2025). GAO-25-107795 (July 17, 2025). US Government Accountability Office.
- US Office of Management and Budget (2016). Circular A-130: Managing Information as a Strategic Resource, section 5.a(1). The White House.
- US Government Accountability Office (2021). GAO-21-524T (April 27, 2021); see also GAO-19-471 (June 11, 2019). US Government Accountability Office.
Tools to try
- Ansoff move finderFramework: Ansoff Matrix
- Business model canvas builderFramework: Business Model Canvas
- Change readiness checkFramework: Kotter's 8-Step Change Model
- Five Forces scorerFramework: Porter's Five Forces
- SMART goal builderFramework: SMART Goals
- SWOT builderFramework: SWOT Analysis
More from Stratrix
“What is stopping a working pilot from reaching production?”
One decision per pack: the framework, a working model, the sourced cases and the board material.
See the pack — $499 →Test a decision, free
Set a live decision against the companies that made it before you.
AcquisitionsThe Distance TestDivestituresThe Divestiture TestDiversificationThe Diversification TestMake or buyThe Make-or-Buy TestStratrix Team
Every Casebook, three Strategy Packs a seat each year and Ask Stratrix, for teams that face these decisions all year.
$1,999 a year · $499 a seatWhat is included →Strategic Decisions
The big calls companies keep facing, told through the 819 companies on record that made them.
24 decisionsFind your decision →New analyses, by email
The defining moves in business, and what they teach, as they publish.