Straight answer

Do we need a CIO, or is an IT director enough?

An IT director is enough if technology mainly supports the business and the big decisions are rare. You need a CIO if technology shapes how you compete, a major programme is under way, or the board needs a senior voice on technology risk. The title matters less than whether someone has the remit, the access and the authority.

How can the board tell whether it is under control?

Signs it is under control

  • Someone owns technology strategy and risk at executive level, whatever their title.
  • Technology decisions are taken with the business in the room, not handed to IT afterwards.
  • The board hears directly from technology at least once a year on direction, not only on incidents.

Signs it is not

  • Major technology choices are being made by suppliers or by the finance team by default.
  • The IT director learns of business plans after they are approved.
  • Nobody can say who would brief the board on a serious cyber incident or a failed programme.

What is the one question to ask?

Ask at the next meeting

Who in the executive team is accountable for technology strategy and technology risk, and how do they reach the board?

A strong answer

One named person, a clear statement of what they decide and what they escalate, and a regular route to the board or a committee.

A weak answer

“It is shared between the IT director, the CFO and our main supplier.”

What is the real difference?

An IT director typically runs technology as a service: systems, infrastructure, support, suppliers and security, within a budget set by others. A CIO is a member of, or close to, the executive team, shares in decisions about where the business is going, and is accountable for how technology helps it get there. The difference is not seniority of title. It is whether the role helps make the decisions, or only carries them out.

Many companies do well with a strong IT director. If the business model is stable, technology spend is modest, and the main need is reliable systems at a fair cost, a CIO may be more than you need. The question changes when technology starts to decide outcomes: a large replacement programme, digital sales, heavy use of data, an acquisition, or rising cyber exposure.

What might the board be getting wrong?

Boards sometimes upgrade the title without changing the role. A new CIO with no seat in executive meetings and no say over the budget will struggle, and the board may then conclude the hire was wrong. The opposite mistake is also common. A capable IT director is never asked for a view on strategy, then judged as too operational. Before deciding on a title, ask what the board and the CEO actually want from the role, and whether they are ready to give it the access that requires.

How should the board decide?

Start from the decisions, not the job title. List the technology decisions the company will face over the next few years and ask who will make them. If the honest answer is a supplier, a consultant or nobody, the gap is at executive level. Ask the CEO whether the current leader could fill it with a wider remit and support. If yes, change the role before changing the person. If no, a CIO hire is probably justified, with the remit agreed before the search starts.

Where to go from here