What should a CTO report to the board?
Short answer
A CTO should explain how technology supports the business, what has changed, which risks need attention and what decisions the board must make. Connect delivery, product quality, spending and organisational capability to commercial priorities. Report meaningful trends and tradeoffs rather than a catalogue of completed tickets or tools.
Organise the report around decisions
- Outcomes: what changed for customers or the business, and what evidence supports it?
- Delivery: which commitments remain credible, and what has changed?
- Investment: where is money going, and what choices need approval?
- Risk: what could materially disrupt the business, and who owns the response?
- Capability: can the organisation execute the strategy, including leadership and succession?
For each material issue, distinguish a fact, an assumption and a recommendation. Make the requested decision explicit, including the consequence of deferring it.
Explain uncertainty without hiding behind detail
A traffic-light dashboard is only useful when everyone understands the thresholds. If a migration is at risk, explain the customer exposure, options and recommendation. Put detailed implementation material behind the summary so it is available when needed.
For AI investment, explain the customer problem, evidence of value, operating costs and unresolved risks. A demonstration is evidence that something can work; it is not yet evidence that the business should depend on it.
Bring an organisation-wide perspective
I served on the BBC’s digital strategy board, one of approximately 12–15 members overseeing digital strategy across the organisation, including enterprise architecture and software engineering standards. That experience informs how I connect technical detail with wider organisational decisions.
Read about my BBC leadership and strategy work
PwC: questions boards can ask when overseeing technology (opens in new window)
Related questions
Should the board see engineering metrics?
Yes, where they explain a material outcome, trend or risk. Include enough context to interpret them and avoid asking the board to manage the engineering backlog.
What if the news is bad?
Raise the issue early, explain what is known and present the options. A credible account of uncertainty and a clear decision are more useful than an optimistic status that conceals a problem.