Guides · Plan

IT strategy on a page: template and example

A technology strategy is a set of choices, not a list of projects. This guide gives you a one-page template in nine boxes, a filled-in example, the thread that links each initiative to a business objective, and a six-week route to board approval.

What an IT strategy is, and is not

A technology strategy answers four questions for the people who run the company: what does the business need from technology, where do we stand, what do we choose to do and not to do, and what will it cost and return. A list of projects is not a strategy. Neither is a picture of a future architecture.

The two-minute test. Could an executive who was not involved explain your choices, and what you decided against, in two minutes? If not, the strategy is still a plan of work.

Putting the strategy on one page forces the choices. Whatever does not fit on the page is either detail, which belongs in the appendix, or something you have not yet decided.

The strategy on a page: nine boxes

Fill the boxes in this order. Each one rests on the one before it.

BoxWhat to writeCommon mistake
1. Business driversFive to eight business objectives, in the executives' words, with their measuresTranslating them into technology too early
2. Where we standThree to five facts about today: capabilities that hold the business back, the state of key systems, cost, riskA long current-state description nobody reads
3. AmbitionOne or two sentences: what technology will make possible for the business in three yearsA slogan that could belong to any company
4. Strategic choicesThree to five themes, each a real choice between options, such as one global platform rather than regional systemsThemes so broad that nothing is excluded
5. What we will not doThe things you have decided against, or postponed, and whyLeaving it out: it is the box executives remember
6. InitiativesThe ranked initiatives that fit the investment envelope, each with a business sponsorTwenty initiatives starting in year one
7. Foundations, organisation and risksThe few enablers everything depends on (data, security, skills), what changes in the IT organisation and sourcing, the principles that settle arguments, and the main risks to the strategyA long list of generic principles, and no risks
8. MoneyThe investment envelope by year, the change in run cost, and the value expectedNo envelope: then it is a wish list
9. Measures and reviewSix to ten outcome measures the business owns, with baseline and target, and when the strategy is reviewed. The operational IT scorecard sits below themIT activity measures instead of outcomes

An example, filled in

A fictional mid-size industrial manufacturer, operating in a dozen countries, with growth coming from services. All figures are illustrative:

BoxExample
Business driversGrow service revenue; cut order-to-delivery time; integrate two acquisitions; reduce working capital; meet new customer reporting obligations
Where we standThree ERP systems after acquisitions; no single view of customers or installed equipment; field service on spreadsheets; the main plant system loses support in two years
AmbitionEvery customer, order and machine visible in one place, so that the company can sell, deliver and service as one business
Strategic choicesOne ERP template for all countries, phased by region; buy a service management platform rather than build; a single data platform for customer and equipment data; keep plant systems local, connected by standard interfaces
What we will not doNo custom e-commerce platform; no new local systems in acquired companies; no AI programme separate from the data platform
Initiatives1. Service management platform (sponsor: head of services); 2. ERP template and first region (CFO); 3. Customer and equipment data platform (chief commercial officer); 4. Plant system replacement (head of operations); 5. Security operations upgrade (chief operating officer)
Foundations, organisation and risksData owners named for customers, products and equipment; tested recovery for critical systems; reuse before buy before build; one integration team replaces three regional ones; main risks: business experts not released for the ERP template, and too much change on the plants in year two
MoneyEnvelope of 9.0 million over three years (4.0, 3.0, 2.0); run cost flat in real terms by year three as three old ERP systems retire; value of about 2.5 million a year by year three, owned by the sponsors
MeasuresService revenue share 18% to 25%; order-to-delivery 21 to 14 days; revenue on the common ERP 0% to 60%; days to close the books 9 to 5; customer and equipment records in one place 35% to 90%; critical systems with tested recovery 40% to 100%

Keep one thread from objective to money

The strength of a strategy is that every line can be traced. Business objectives lead to the capabilities they depend on. Capabilities lead to the applications that support them. Gaps lead to initiatives. Initiatives are ranked, sequenced and costed. When someone challenges a priority, you follow the thread back together, instead of arguing opinions.

  • Capabilities before systems. Score what the business must be able to do on importance and on how well technology supports it. "Good enough" is as much a decision as "close the gap".
  • Applications on two axes. Rate each application on business fit and technical fit, with its business and technical owners in the room. Each one lands in one of four positions: invest, migrate, tolerate or eliminate.
  • A funding line. Rank the initiatives with their sponsors and draw the line where the envelope runs out. The line turns "everything is a priority" into a concrete trade: to fund this, we do not fund that.
  • A limit on change. Sequence by dependency and by how much change the organisation can absorb each quarter, not by enthusiasm.

Six ways IT strategies fail

FailureWhat it looks likeWhat prevents it
A technology plan with a business coverInitiatives named after products; no executive owns anyStart from business drivers; a sponsor for every initiative
No choicesEverything is a priority; nothing is refusedAn envelope, a funding line and a "will not do" box
Too much at onceTwenty initiatives start in year oneA limit on initiatives in delivery; honest sequencing
Benefits nobody ownsA large benefit figure with no name beside itBenefits owned by sponsors and reviewed every quarter
Approved, then forgottenThe roadmap in use is not the one approvedA quarterly review and an annual refresh
Written for ITArchitecture diagrams in the board deckBusiness language; technology in the appendix

From blank page to board approval in six weeks

WeekWorkOutput
1Mandate with the CEO, including the investment envelope; executive interviewsBusiness drivers
2Capabilities workshop; facts on the application portfolioCapability gaps
3Applications workshop; options for the two or three big choicesPortfolio positions; options scored
4Initiatives listed, scored and costed with their sponsorsRanked list against the envelope
5Roadmap, investment, risks and measures; priorities workshopFunded roadmap; owners named
6Write the page and the document; walk each executive through it; presentStrategy presented for approval

Six weeks assumes you know the company. In a new role, do the diagnosis first: see the first 90 days checklist.

A note on AI. AI belongs inside the themes, not in a separate strategy. Treat each AI use case like any other initiative, with a driver, a sponsor and a benefit, and treat the AI foundations (policy, data, skills, risk) as one initiative on the page.

Questions

How long should an IT strategy be?

One page for the executive committee, a deck of about fifteen slides for the board, and a written document of ten to fifteen pages for the people who will deliver it. The page comes first: if the choices do not fit on it, they are not yet made.

Over what period should an IT strategy run?

Three years is the usual horizon, with a rolling roadmap reviewed every quarter and refreshed every year. Show five-year value for major investments, because a three-year window understates anything delivered in year three.

Should the IT strategy be separate from the digital strategy?

Rarely. Two strategies compete for the same money and people. Write one technology strategy that serves the business strategy, with digital and AI choices as themes inside it.

What should trigger an early rethink of the strategy?

An acquisition or sale, a new CEO or company strategy, a large funding cut, a major security incident or partner failure, or a technology shift that changes the economics of a choice you made.

Toolkits on this topic

Related