Straight answer

Is my CIO good enough?

Often yes for running today's technology, but that is the wrong test. Judge a CIO on whether they can explain technology risk and value in business terms, deliver change without surprises, and tell the board bad news early. A CIO who keeps the lights on but cannot do those three things is not enough for a board.

How can the board tell whether it is under control?

Signs it is under control

  • The CIO explains choices in terms of cost, risk and business outcome, without needing a glossary.
  • Problems reach the board early, with options, rather than late with an apology.
  • Business leaders seek the CIO's view before making decisions, not after.

Signs it is not

  • Board papers from technology are long on activity and short on decisions or trade-offs.
  • Big programmes repeatedly surprise the board with delays or cost.
  • Other executives describe technology as a service desk rather than a partner.

What is the one question to ask?

Ask at the next meeting

What is the one technology decision the board will need to make in the next year, and what is your recommendation?

A strong answer

A specific decision, the options, a clear recommendation with its cost and risk, and what the CIO would need from the board to deliver it.

A weak answer

“We are focused on stability and continuous improvement across the estate.”

What does good enough look like?

A CIO (chief information officer) has two jobs. One is running the technology the company depends on today: systems, suppliers, security and support. The other is helping the company decide where technology should change the business, and then delivering that change. Many CIOs are strong at the first and less tested on the second.

For a board, the useful evidence is visible from the boardroom. Do you understand the CIO’s papers? Do the numbers in them hold from one meeting to the next? When something goes wrong, do you hear it from the CIO first? Do the CEO and the business leaders trust the CIO’s judgement on priorities, or work around them?

What might the board be getting wrong?

The board may be judging the CIO on things the board itself controls. A CIO given a small budget, a reporting line far from the CEO, and twenty minutes at the end of the agenda will look less strategic than they are. Directors sometimes blame the CIO for a programme the board approved too quickly, or expect them to explain technology in board language without ever saying what the board needs. Before deciding the person is wrong, check that the role, the access and the questions are right.

How should the board find out?

Give the CIO a real question and see what comes back. Ask for a short paper on one decision the board will face, with options and a recommendation. With the CEO’s knowledge, talk to the CEO, the CFO and one or two business leaders about how they use the CIO. Look back at the last two large programmes and ask how early the board heard about problems. If the answers are clear, specific and consistent, you have a CIO the board can rely on. If not, agree with the CEO what support, scope or change is needed, and revisit it at a set date.

Where to go from here