# 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.

Source: https://ciohelm.com/guides/it-strategy-on-a-page · By the CIO Helm team · Updated 2026-11-13

## 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.

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.

| Box | What to write | Common mistake |
| --- | --- | --- |
| **1. Business drivers** | Five to eight business objectives, in the executives' words, with their measures | Translating them into technology too early |
| **2. Where we stand** | Three to five facts about today: capabilities that hold the business back, the state of key systems, cost, risk | A long current-state description nobody reads |
| **3. Ambition** | One or two sentences: what technology will make possible for the business in three years | A slogan that could belong to any company |
| **4. Strategic choices** | Three to five themes, each a real choice between options, such as one global platform rather than regional systems | Themes so broad that nothing is excluded |
| **5. What we will not do** | The things you have decided against, or postponed, and why | Leaving it out: it is the box executives remember |
| **6. Initiatives** | The ranked initiatives that fit the investment envelope, each with a business sponsor | Twenty initiatives starting in year one |
| **7. Foundations, organisation and risks** | The 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 strategy | A long list of generic principles, and no risks |
| **8. Money** | The investment envelope by year, the change in run cost, and the value expected | No envelope: then it is a wish list |
| **9. Measures and review** | Six to ten outcome measures the business owns, with baseline and target, and when the strategy is reviewed. The operational IT scorecard sits below them | IT 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:

| Box | Example |
| --- | --- |
| Business drivers | Grow service revenue; cut order-to-delivery time; integrate two acquisitions; reduce working capital; meet new customer reporting obligations |
| Where we stand | Three 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 |
| Ambition | Every customer, order and machine visible in one place, so that the company can sell, deliver and service as one business |
| Strategic choices | One 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 do | No custom e-commerce platform; no new local systems in acquired companies; no AI programme separate from the data platform |
| Initiatives | 1. 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 risks | Data 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 |
| Money | Envelope 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 |
| Measures | Service 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

| Failure | What it looks like | What prevents it |
| --- | --- | --- |
| A technology plan with a business cover | Initiatives named after products; no executive owns any | Start from business drivers; a sponsor for every initiative |
| No choices | Everything is a priority; nothing is refused | An envelope, a funding line and a "will not do" box |
| Too much at once | Twenty initiatives start in year one | A limit on initiatives in delivery; honest sequencing |
| Benefits nobody owns | A large benefit figure with no name beside it | Benefits owned by sponsors and reviewed every quarter |
| Approved, then forgotten | The roadmap in use is not the one approved | A quarterly review and an annual refresh |
| Written for IT | Architecture diagrams in the board deck | Business language; technology in the appendix |

## From blank page to board approval in six weeks

| Week | Work | Output |
| --- | --- | --- |
| 1 | Mandate with the CEO, including the investment envelope; executive interviews | Business drivers |
| 2 | Capabilities workshop; facts on the application portfolio | Capability gaps |
| 3 | Applications workshop; options for the two or three big choices | Portfolio positions; options scored |
| 4 | Initiatives listed, scored and costed with their sponsors | Ranked list against the envelope |
| 5 | Roadmap, investment, risks and measures; priorities workshop | Funded roadmap; owners named |
| 6 | Write the page and the document; walk each executive through it; present | Strategy presented for approval |

Six weeks assumes you know the company. In a new role, do the diagnosis first: see the [first 90 days checklist](https://ciohelm.com/guides/new-cio-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.

### Build the strategy with the IT Strategy and Roadmap Kit

A 14-sheet workbook that keeps the thread from drivers to capabilities, applications, options, ranked initiatives, a funding line, a 12-quarter roadmap with a capacity check, investment and NPV, plus a 17-slide board deck, a strategy document, a business case template, interview and workshop guides, technology principles and a review routine. One-time price , no subscription.

[Download the kit](https://ciohelm.com/download/it-strategy-and-roadmap-kit)[See what is inside](https://ciohelm.com/toolkits/it-strategy-and-roadmap-kit)

## 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

- [Roadmap Builder](https://ciohelm.com/toolkits/roadmap-builder): a technology roadmap people believe
- [AI Strategy Builder](https://ciohelm.com/toolkits/ai-strategy-builder): build an AI strategy your executives can fund
- [Executive Briefing Notes Kit](https://ciohelm.com/toolkits/executive-briefing-notes-kit): keep executives and directors fluent on technology

## Related

- [Technology business case: a structure finance will recognise](https://ciohelm.com/guides/technology-business-case)
- [New CIO checklist: the first 90 days, week by week](https://ciohelm.com/guides/new-cio-first-90-days-checklist)
- [IT KPIs for the board: the measures that matter](https://ciohelm.com/guides/it-kpis-for-the-board)
- [Digital Maturity Assessment: a quick baseline for box 2](https://ciohelm.com/digital-maturity)
