Capabilities are not a strategy — how the CTO-CEO translation gap turns ambitious AI roadmaps into stalled board conversations.

Axel Tombereau, Odyssey
CEO Briefings

Most AI roadmaps are developed by technical teams focused on capabilities rather than value creation. This disconnect often prevents progress at the board level.
The Signal
A pattern I am seeing with increasing frequency in advisory conversations: the CEO asks the CTO for an AI strategy. The CTO delivers a roadmap. The CEO presents it to the board. The board asks: What is the return? The CEO cannot answer, because the roadmap describes what the technology can do, not what business value it creates. The initiative stalls. Six months pass. The cycle repeatThis is not the CTO’s fault. It reflects a structural issue in how most organizations develop AI strategy. According to PwC’s 2025 Global CEO Survey, fifty-six percent of companies report getting “nothing out of” their AI investments.nts.
The Strategic Read
There are three common failure modes for AI roadmaps that fail to gain board support. The feature-led roadmap lists potential AI capabilities without linking them to revenue, margin, or competitive advantage. The vendor-led roadmap follows the AI vendor’s product releases instead of aligning with company strategy. The POC-as-strategy roadmap treats pilots and proofs of concept as a strategy, even though there are no production deployments or clear paths to implementation.
The core issue is a translation gap. CTOs focus on technical capabilities, while CEOs prioritize outcomes such as revenue growth, margin expansion, competitive advantage, and risk reduction. Most organizations lack the ability to translate capabilities into measurable outcomes.
A CEO can assess an AI roadmap’s strategic quality by asking four questions: What specific business outcome does each initiative produce, and how will it be measured? Which initiatives create a competitive advantage that competitors cannot replicate within twelve months? What is the total investment required, and what is the expected return over twenty-four months? What is the impact on our competitive position if we do none of this?
If an AI roadmap cannot answer “what business outcome does this produce?” for every item, it is a technology wishlist, not a strategy. Do not present it to the board.
The CEO Move
Schedule a focused ninety-minute session with your CTO this month. Use the four stress-test questions to structure the discussion. Review the AI roadmap line by line, and require reframing or removal of any initiative without a clear, measurable business outcome.
Then rebuild the roadmap from the top down. Begin with the three business outcomes most important to the board, such as cost reduction, revenue growth, risk mitigation, or competitive positioning. For each outcome, identify relevant AI capabilities. For each capability, specify the targeted process, the metric to improve, and the required investment.
The resulting roadmap will be shorter, with fewer initiatives, and will be the first AI document your board is likely to act on.
