Six months ago, your COO took on the AI mandate. It sat alongside their existing role, which was already full. They ran a few tool trials, got one workflow rebuilt, and by month three were spending four or five hours a week on it. Now two departments have started buying subscriptions without telling anyone, the board is asking about ROI, and your COO is stretched thin enough that the AI work gets whatever’s left of their week.
You know the arrangement is fraying. The question is whether that means it has failed, or whether it has simply run its course.
What is the side-of-desk AI model?
The side-of-desk model means your AI mandate lives inside an existing role rather than a dedicated one. A COO or senior director carries it alongside their main responsibilities, with no ring-fenced headcount and typically no budget beyond individual tool approvals. It is the arrangement many owner-managed businesses land on first, usually after an early pilot or a department-level win gives someone the credibility to own the space.
The delegate typically comes from the operations or technology side of the leadership team. They run evaluations, set informal guidelines, and field questions from departments. The founder makes the strategic calls, signs off on material spend, and stays available when something escalates. The whole arrangement rests on the delegate having enough bandwidth and enough authority to keep things moving.
There is no formal job description, no defined scope, and often no explicit decision-rights boundary. That ambiguity is workable at the start. It becomes expensive later.
Why is starting this way the right call?
At the start, no one knows what AI will actually do for the specific business. Early adoption is exploratory. Half the tools trialled don’t stick, the processes that look ready for AI often need redesigning first, and the learning happens through doing it. Bolting the mandate onto someone who already understands the operation is a sensible hedge. It keeps the commitment proportional to what the work genuinely requires at that stage.
BCG’s 2025 research on AI adoption found roughly half of companies remain stuck in early or stagnating stages, unable to scale past proof-of-concept. The barrier in those cases is rarely the technology itself. MIT’s NANDA research found around 95% of generative AI pilots fail to show measurable P&L impact, with the cause being a gap in workflow integration rather than model quality. Those findings are not arguments for investing less. They are arguments for investing appropriately, which at the exploratory stage means not hiring ahead of the problem.
The side-of-desk model earns its keep precisely because it doesn’t overcommit. What tips the balance is whether the conditions have changed since it started, and whether anyone has noticed.
Where does the side-of-desk arrangement start to crack?
The arrangement holds well while AI is exploratory, but four signals tend to cluster when it has outgrown the setup. The founder becomes the bottleneck on AI decisions, departments stop waiting and start buying tools independently, shadow AI spreads without governance, and the board asks ROI questions that take a week to compile. Any one of these can be absorbed; all four together points to a problem the arrangement cannot solve.
The bottleneck signal usually shows first. When the delegate cannot make a call without returning to the founder, the business learns quickly that AI decisions sit with the owner after all. The delegate’s authority erodes, and departments start routing around both of them.
Independent tool buying follows from the same logic. If the central point of contact is too stretched to help, people solve the problem themselves. Research from Kyndryl found around 70% of leaders say their workforce is not ready for AI adoption. In practice, the readiness gap more often reflects the governance arrangements than the individuals involved. Employees who find their own solutions are telling you the official channel isn’t working for them.
Shadow AI builds from there. When employees are using personal tools that no one in the business has visibility over, the formal programme becomes irrelevant to the people doing the actual work.
The board question lands last and tends to cost the most. A founder who cannot answer a direct AI ROI question without a week of preparation has lost strategic visibility over a programme that is meant to be generating value. At that point the delegate is doing the work without the authority to move it, and the founder carries the authority without the information to use it.
When does side-of-desk need to become a real seat?
When the hidden cost of the part-time arrangement exceeds the visible cost of a salary. That crossover happens earlier than it looks. A senior operator carrying AI on top of a full role does neither at full capacity, and the programme runs on whatever bandwidth remains. Research consistently finds that visible, sustained sponsorship is among the strongest predictors of AI adoption. A delegate squeezed between two roles cannot provide that consistently.
A useful diagnostic is the gap between what the AI mandate is supposed to deliver and what anyone is actually accountable for. If the role holder is measured on operational performance, the AI work will consistently lose when priorities conflict. BrainStorm’s research on technology rollouts found that organisations reaching meaningful adoption levels showed active leadership sponsorship, role-specific workflow guidance, and sustained communication. Those things require dedicated time, not just a title.
Spencer Stuart’s research makes a case that the answer is not always a new hire. Sometimes the right move is a clearer decision-rights conversation with the existing delegate, backed by genuine authority rather than a role expansion. If the four signals are present but the mandate has never had real scope, a real budget, or real decision rights, the arrangement has not been properly tested. Fixing the conditions before changing the headcount is often the faster path.
When the conditions are right and the signals persist, the work has genuinely outgrown the role. At that point, a staged transition reduces the risk: fractional or part-time before full-time, sized against the actual work rather than the aspirational scope.
What does the transition cost on both sides?
Staying side-of-desk too long has compounding costs. Tool sprawl, duplicated spend, and ungoverned data accumulate. M&A advisors identify owner dependency as one of the largest discounts applied to exit multiples, and an AI mandate that deepens founder bottlenecks works against that. The cost of moving too early is a dedicated role without enough genuine work and an operator who becomes a gatekeeper rather than a driver of adoption.
The staged path reduces exposure on both sides. The first move is to give the existing arrangement proper conditions: a defined scope, a real budget, and decision rights that don’t require the founder’s sign-off on every tool or policy question. That change alone addresses a meaningful share of the breakdown signals without a single new hire.
If those conditions are in place and the four signals persist, the work has genuinely outgrown the arrangement. A part-time or fractional role may be the right first step before a full-time hire. The worst version of this decision is hiring for what you hope the programme will become rather than what it currently is. An over-resourced AI function with insufficient scope creates its own problems: a new hire who fills their time with reports and process rather than implementation.
The practical question is straightforward. If you mapped out everything the AI mandate actually requires each week, does that amount to a full-time role? If the honest answer is no, the problem is governance and scope, not headcount.
The side-of-desk model works until it doesn’t, and that shift tends to be gradual. The signals are there before the arrangement fails; they need someone paying attention to see them. If you’re reading this wondering whether your own arrangement has run its course, the fact that you’re asking is usually the signal itself.
