The leader who can't delegate
The most common question I got before joining Sonetel as CAIO: "Why do you need to be inside the organization? Can't you just consult?"
The question is reasonable. I had built up a consulting practice. I had clients who wanted more hours. Taking the role of an employed executive meant lower hourly rates, a clearer mandate, and much more responsibility.
It took me a few months to articulate the answer clearly. But it's actually simple.
A consultant gives recommendations. An executive owns the outcome. Those are not the same thing.
What delegation actually creates
I've seen the pattern many times. A company brings in a consultant or agency for AI transformation. Reports are delivered, recommendations made, roadmaps built. The presentations are polished. The leadership team nods.
Then nothing happens. Or everything happens — but in the wrong place. A pilot launches in one team that was enthusiastic enough to contact the consultant. The rest of the organization barely knows it exists.
Six months later: the project is "successful" by the consultant's measurement. But outside that room, nothing has moved.
That's not the consultant's fault. It's the structure's fault. The consultant doesn't own the decision. Doesn't own the culture. Doesn't own what happens Monday morning when the pilot needs to scale and meets the daily friction of an unchanged organization.
The report confirms it
AI Sweden recently published their Leadership Report 2026 — one of the more thorough analyses of what actually separates organizations that succeed with AI transformation from those that don't.
The clearest pattern: transformation succeeds almost exclusively when it is owned by someone with real mandate at the top. Not an AI lead at middle management level. Not an external advisor. The person responsible for the whole.
"A very clear mandate from the highest leadership is required to break through old structures, and consensus was seldom reached at the initiation of the shift." — AI Sweden Leadership Report 2026
That's exactly what I've observed. And exactly why I no longer consult on this type of engagement. It doesn't work.
The difference in practice
It's not about the title. It's about what happens when it gets difficult.
As a consultant, I can recommend that a leader make a certain decision. As CAIO, I own that decision. I'm in the management team meeting. I formulate the questions. I drive the follow-through.
That means I can meet resistance directly — not report on it in a PowerPoint.
It means that when a team doesn't adopt a new way of working, it's my problem to understand why and do something about it.
It means the AI agenda can't be deflected with "we'll take it up with the consultant." The consultant is in the room.
What it actually requires
The report describes it as "actively understand, guide, and take responsibility." Three verbs, all active. Not "approve" or "delegate" or "follow up on."
That requires the leader — CAIO, CEO, CDO, whatever the title — to actually understand what is happening. Not at the detail level. But enough to ask the right questions. Enough to see when a technical solution is solving the wrong problem. Enough to not be dependent on someone else interpreting reality.
AI literacy at the top is not a luxury. It is a prerequisite for mandate to have substance.
Not for everyone
This is not an argument that every organization needs a full-time CAIO. It is an argument that whoever drives AI transformation must have real ownership — whether that's a full-time role, a shared focus, or a fractional engagement.
What doesn't work is when ownership is absent. When the AI question is handled as a side project, without someone who can break consensus and drive through what actually needs to happen.
The report is clear: those who wait for the organization to solve it on its own wait in vain. Change requires a person who takes personal responsibility for it.
That's not a new insight. It is an old leadership responsibility — applied to a new domain.
See also: Personal accountability as the root (series 1) and It was never a technology question (series 10).
AI Sweden Leadership Report 2026: ai.se/sv/ai-sweden-leadership-report-2026