Practice / I
IT strategy
A direction your organisation can fund, follow and measure itself against.

What you receive
A strategy document of around fifteen to twenty-five pages, written for a board rather than for technologists. It sets out the business priorities technology must serve, the current state in plain terms, the options considered, the choices made, an investment outline and a twelve-month plan with decision points. A one-page summary accompanies it.
How we build it
- Interviews with leadership, operational leads and IT, typically twelve to twenty conversations.
- Review of systems, contracts, costs, support arrangements and known risks.
- Workshops to agree priorities and test options.
- Drafting, challenge and revision with your sponsor.
- Presentation to decision-makers and a written record of the decisions taken.
Inputs we need
A sponsor at leadership level, access to the people we need to interview, current contracts and cost information, and any existing plans or reviews. Gaps in information are noted as such, not filled with guesses.
Tradeoffs to expect
Breadth against depth: a strategy covering everything says little about anything. We agree the scope up front. Speed against consensus: faster strategies involve fewer voices. We make the choice explicit.