Contents · 7 min read
01 / 05 · The shift
When does AI leave the CIO's roadmap?
In short
AI becomes a management-team concern when it starts changing which company priorities get money. The CIO can lead the tech work, but cannot decide those priorities alone.
At your next management meeting, an AI plan competes with another company need for funds. The CIO can explain the tech work, but your leadership team must decide which priority moves because the choice determines what your company does next.
This setup can work while each project serves a priority that management has set. The CIO then enables work that the company has already chosen.
The line moves when an AI plan competes with other company needs for funds. At that point, the choice affects what your company will do next. It is no longer just a tech choice.
Your leadership team needs enough first-hand experience with AI to judge which work should receive money.
Keeping the funding choice inside tech may still feel quick. But it asks the CIO to set a business priority that management must fund and judge.
Delegating AI strategy to the people who know the tech creates this gap when leaders lack enough first-hand use. Without that experience, management cannot properly evaluate the plans it must fund.
That is why the next choice belongs with the CEO and management team.
02 / 05 · Company choice
What must the CEO and management team decide?
In short
Your management team must decide what AI should change in the business and which plans get funds. It owns company direction, so it must choose between AI work and other needs.
Sales sees demand, while operations sees what your teams can deliver. Finance sees what the plan can bear. Each leader tends to guard the needs they know best. That is why decisions weaken when each function only defends its own work. The CEO still owns the whole result.
Your team must make one choice for the whole company. Use the next management meeting to do it:
Have the CEO name the change
Write one plain line on what AI should change in the business.
Have the team compare competing requests for funding
Set each plan against the same company priorities.
Have management choose what moves now
Fund the chosen work and name the result it must produce.
Your leaders need enough use of AI to judge these choices. Without it, they may back only plans framed around speed or lower cost.
The board needs to judge the company's position and the choices management has made, rather than count tools. AI strategy for boards starts with the company's position and the choices that directors must judge.
The CEO does not need to run each funded plan. Once management funds one move, ownership shifts to the leader whose business result must change.
03 / 05 · Business result
Who owns the result after launch?
In short
The business leader responsible for the result must own delivery and recovery after launch. A working AI tool does not move that duty to the CIO or a central AI team.
Your company already holds leaders to account for the work they run. AI should not break that link just because the work now uses new tech.
The approved plan should name its intended business result and owner. It should also state the main steps and assumptions that could make the plan fail. Then set dates to test those assumptions again.
This matters when the first plan falls short. The named leader must find the cause and lead the recovery. That leader stays accountable because the result still sits in that part of your business.
Finance can own the numbers in the review. The business leader then explains what caused them and what must change. This keeps the facts clear, but it does not move the result away from its owner.
An AI-augmented management team can keep the facts and past choices close at hand. But your leaders still make the calls and own what follows.
The CIO enables that leader by setting the security and data requirements. The CIO then makes sure the work fits the company's systems.
04 / 05 · Tech role
What should the CIO own?
In short
The CIO should set the security and data requirements for funded work. The CIO should also make sure it fits the company's systems. Management retains the funding choice, while the named business leader retains the business result.
The CIO often sees new tools first and knows what the current tech can support. That makes the CIO vital to the work even though the business priority comes from elsewhere.
The CIO should set the security and data requirements before work starts. Tech leadership should then make sure the chosen plan fits the company's systems and continues to meet those requirements.
The business owner stays focused on the result. Meanwhile, the CIO makes sure the work meets the security and data requirements. The CIO also makes sure it fits the company's systems.
A sound IT plan can still serve the wrong company priority. In the same way, a useful tool can fail to produce the result that won its funds.
The CIO should not be left to prove the business gain after launch. That would let the business leader treat AI as someone else's project.
The final step is to make these roles clear before each new AI plan receives funds. Name who decides, who delivers and who enables the work.
05 / 05 · Scale
How do you keep ownership clear as AI scales?
In short
Apply the same split each time your company funds AI work. More teams can use AI, but company priorities and funding choices should stay with management.
| CEO and management team | Business leader | CIO and tech leadership |
|---|---|---|
| Funding choice. Decide what AI should change and what receives funds. | Business result. Accept the intended result and own what must improve. | Technical requirements. Set the security and data requirements, then make sure the work fits the company's systems. |
| Review. Compare actual results with what management approved and test the assumptions behind the plan. The team decides what changes next. | Delivery. Lead the work and its recovery. The result stays with the leader after launch. | Support. Keep the work within the security and data requirements, and make sure it continues to fit the company's systems. |
Use the table before you approve the next AI plan:
Have the CEO put the business change on the agenda
State why the choice belongs at company level.
Have management decide whether to fund it
Name the business leader before any work starts.
Have that leader state the intended result
Then set review dates and testable assumptions.
Have the CIO set the technical requirements
Cover security and data, then make sure the plan fits the company's systems before delivery.
Review the result through your normal management rhythm
Finance owns the numbers, while the business leader explains what changed.
This split can work as more functions take on AI work. Each leader can run a funded plan, but management still decides which priorities get money.
Keep the review tied to results because faster work alone says little about the choice. A team can move faster without making better decisions, so judge whether funded work delivers what management approved.
That review shows what management must decide next.
Make ownership real
The next task is to apply this ownership split to a real management-team decision: choose what AI should change and which work receives funding, then name the business leader who owns the result. See The Opportunity brings the management team through three workshops, combining hands-on use of AI with custom agents for each leader. It ends with a ranked roadmap of opportunities, so the team has a shared basis for choosing the first funded moves while keeping the decision with management.
Three to four weeks, three workshops with your management team: hands-on use of AI, custom AI agents for each leader, and a ranked roadmap of opportunities. Fixed fee, and no IT project to get started.
Questions CEOs ask about this
Who should own AI in a mid-market company: the CEO, CIO or business functions?
The CEO and management team should choose what AI changes and gets funded, while the business leader owns the result and the CIO owns security, data and system fit. When an AI funding request reaches your management meeting, leaving it with tech asks the CIO to set a company priority that your team must judge. Assign these roles before funds move so ownership stays clear after launch.
Which decisions must remain with the CEO and management team?
They decide what AI should change at company level and which plans get funds. They also review whether funded work still fits company priorities.
What should technology leadership own?
Tech leadership sets the security and data requirements, then makes sure the funded work fits the company's systems. The funding choice stays with management, while the business gain stays with the named business leader.
Who owns benefits after an initiative launches?
The named business leader owns the intended result and leads delivery. If the work falls short, that same leader leads the recovery.
How should responsibilities change as adoption scales?
Keep the same split even as more functions start AI work. Functions can run funded plans, but management still chooses the company priorities. The CIO still owns the technical requirements.
What role should the board play?
The board evaluates the ambition the CEO brings. Management must know the work well enough to explain the choice and the funds behind it.
Founder, GRAIL
Johan has spent fifteen years in management consulting and executive leadership, including as Chief Product Officer of a SaaS company. He founded GRAIL to help European leadership teams work out what AI changes at the core of their business. He is the author of The Execution Revolution and the host of the ThinkRoom podcast.
Related reading
Sources
- AI consulting for the Nordics: why a mid-market CEO and leadership team can move fast. (accessed October 29, 2026)
- The Delegation Problem: why leaders must understand AI before they decide what it should change. (accessed October 29, 2026)
- You Don't Rise to Your Strategy: why the CEO must turn functional priorities into one decision for the whole company. (accessed October 29, 2026)
- AI Strategy for Boards: why the board needs a company position rather than a list of tools. (accessed October 29, 2026)
- What does an AI-augmented management team look like?: how leaders keep choices while the company picture stays current. (accessed October 29, 2026)
- Copilot Is Not an Agent: why funded results matter more than speed alone. (accessed October 29, 2026)
Next scheduled review: January 30, 2027