The Difference Between an IT Plan and a Technology Strategy

An IT plan lists the technology work an organisation will do and when it will do it. A technology strategy explains what the business is trying to achieve, where technology helps it get there, and what will deliberately not be funded. One is a schedule; the other is a set of choices. Most organisations have the first and call it the second.

What an IT plan actually is

An IT plan is a list of work: the migration in Q2, the laptop refresh in Q3, the renewal of the core platform, the security patching programme. It is usually owned by the IT team, built from what is already in flight plus whatever has been requested, and organised by timeline and budget.

There is nothing wrong with that. Systems need to be kept running and projects need to be sequenced. The problem starts when the plan is the only document in the room, because a plan can only answer "what are we doing." It has no way to answer "should we be doing it."

What a technology strategy actually is

A technology strategy starts from the business, not from the systems. It says what the organisation is trying to achieve over the next few years, which of those goals depend on technology, and what has to be true for technology to support them. Then it makes trade-offs: this gets funded, that does not, and here is why.

The trade-offs are what make it a strategy. A document that lists everything the organisation would like to do is a wish list. A document that says what will be done first, what will wait and what will not happen at all is a strategy.

The two side by side

Why organisations mistake one for the other

The plan looks like a strategy. It has dates, owners and a budget, and it sits in a presentation with a confident title. It gets approved at the same planning meeting a strategy would be. Nobody stops to ask whether it contains any actual decisions about priorities, because everything on it is already underway or already committed.

It is also the easier document to produce. Writing down what is already happening takes an afternoon. Deciding what the business should stop asking for takes authority, and that is the part that tends to get skipped.

How to tell which one you have

A few questions separate the two quickly:

• Can you name something the document deliberately decided not to do, and explain why?
• Can each major item be traced back to a business goal, not just to a system or a contract?
• Does someone outside IT, such as the CFO or CEO, treat it as their own document?
• When a new request arrives mid-year, is there a way to decide where it ranks?

If the honest answer to most of these is no, the organisation has a plan. That is a useful thing to have, but it is not a substitute.

An IT plan tells you what will be done. A technology strategy tells you what to leave undone.

Getting from a plan to a strategy

The fastest way to see the gap is to review the existing plan against what the business is actually trying to achieve. A Technology Executive Diagnostic does exactly that: it shows which parts of the plan support a business outcome and which are simply inherited. From there, a Technology Strategy & Transformation engagement turns those findings into ranked priorities with clear ownership.

Where the organisation does not have that seniority in-house full time, a Fractional Technology Executive can own the strategy as an ongoing responsibility, so it is revisited as the business changes rather than filed after the planning offsite.

The bottom line

An IT plan keeps the technology function busy and organised. A technology strategy keeps it pointed at something. Most organisations need both, but they need to know which one they are holding, because the plan cannot rank its own priorities. That is the job of the strategy, and it only works if someone senior enough owns it.

Frequently asked questions