Straight answer
When should a board replace the CIO?
Rarely on the board's own initiative, and rarely for one failed project. Replacing the CIO is mainly the CEO's call. The board should press for it when trust has gone, meaning bad news arrives late or the same problems repeat after support, or when the role has outgrown the person and more support will not close the gap.
How can the board tell whether it is under control?
Signs it is under control
- Problems are reported early and honestly, even when the news is unwelcome.
- Lessons from past setbacks show up in how the next programme is run.
- The CEO can describe the CIO's strengths and gaps, and what is being done about the gaps.
Signs it is not
- The board has more than once learnt of a serious problem from someone other than the CIO.
- The same failings recur across programmes despite agreed support and changes.
- The CEO defends the CIO in public but works around them in practice.
What is the one question to ask?
If the CIO left tomorrow, what would we lose, and what would we be glad to change?
A strong answer
A specific, balanced account from the CEO, naming the strengths that would be hard to replace and the gaps, with a view on whether the gaps can be closed and by when.
A weak answer
“The CIO knows our systems better than anyone; we could not manage without them.”
What should actually trigger a change?
A failed or late programme is not on its own a reason to replace the CIO. Large technology change is hard, and a leader who has been through a difficult programme has often learnt the most. The stronger signals are about trust and judgement. The board hears bad news late. Reports turn out to have been more hopeful than the facts. The same mistakes recur after the CEO and the board have offered support. Or the company has changed, for example through growth or a major new strategy, and needs a different kind of leader.
Dependence on one person is a separate risk. If nobody else understands the critical systems or the main supplier relationships, that needs fixing whether or not the CIO stays.
What might the board be getting wrong?
Boards sometimes want a change because a change is visible. Replacing the CIO in the middle of a troubled programme can feel decisive, but it often costs months while a newcomer learns the work, and the underlying causes stay. Those may include an unrealistic budget or date the board approved, too little executive attention, or unclear ownership in the business. Ask honestly how much of the problem the next CIO would inherit, and whether the board helped create it.
How should the board handle it?
Work through the CEO, who owns the decision and the relationship. Ask the CEO for a frank assessment, the support already given, and a date by which things must improve. If a change is needed, ask for a succession plan first: who covers the role in the interim, how knowledge is kept, and how critical programmes are protected during the handover. Treat the departing CIO fairly, and make sure the reasons are understood, so the next appointment fixes the real problem rather than repeating it.