Get your AI decision rights in writing before the programme stalls

Two colleagues reviewing a printed document at a meeting table, one pointing to a specific section of the page
TL;DR

If your AI mandate came verbally, it will break down the first time a real disagreement surfaces. Decision rights are the pre-agreed, written list of which calls belong to the delegate and which require the founder. Getting them down in writing, and revisiting them regularly, is what separates a programme that keeps moving from one that stalls in a permanent grey area.

Key takeaways

- AI decision rights are the pre-agreed written list of which calls belong to the delegate and which require the founder. Verbal mandates break down because both parties recall them differently under pressure. - Accountability gaps are one of the main reasons AI programmes see usage rise while business impact stays flat. The gap often traces to an arrangement that was never written down. - Decision authority gaps cluster at three types of call: vendor selection, team-facing communications about AI direction, and spending decisions within the agreed budget. - Operational decisions within the agreed mandate belong to the delegate; decisions affecting client relationships, investor perception, or spend above a set threshold belong to the founder before action is taken, not as a report after. - A one-page written summary, confirmed by both parties, plus a monthly alignment check-in in the early months, is enough to keep the mandate stable and the programme moving.

You make a call on a vendor. Three weeks later, the founder overrules it in a meeting you weren’t invited to. You make another call, more conservative this time, and get told you’re moving too slowly. Nobody says you’re doing it wrong, exactly. They just keep adjusting what you’ve already decided.

That is what a missing decision-rights framework looks like from the inside. A slow drain on your credibility and your programme’s forward motion.

What are AI decision rights?

AI decision rights are the pre-agreed, written list of which calls belong to the person leading the programme and which require the founder or board. They define the boundaries before disagreements surface, not after them. Without that list, every decision sits in a grey area where whoever speaks last wins, and the delegate ends up managing contradiction rather than moving the work forward.

In practical terms, decision rights cover which operational calls the delegate makes independently, which need the founder’s sign-off before action, and where the regular check-in sits for anything close to the boundary.

The written part matters as much as the agreement itself. Verbal mandates feel sufficient when they are given. Both parties mean well. But when the first real disagreement arrives, each side recalls the mandate through the pressure they are under at that moment. The founder remembers a general direction; the delegate remembers permission to act. The gap between those two interpretations is what the programme runs into.

BCG’s 2025 research on AI adoption found that a persistent accountability gap is one of the main reasons organisations see AI usage rise while business impact stays flat. The gap does not always signal governance dysfunction. Often it is simply an arrangement that was never written down.

The delegate who has a written decision-rights agreement has something the delegate with a verbal mandate does not: a common reference point. When a disagreement arises, both parties can return to what was agreed rather than to what each recalls. That reference point is what makes the mandate stable enough to build on.

Why does a verbal mandate almost always break down?

A verbal mandate breaks down because both parties interpret it through the pressure they are under when they need to recall it. The founder who said “you’ve got this” in March means it less literally by June, when a decision touches something they care about. The delegate, who took those words at face value, finds themselves wrong-footed and their authority gradually eroded.

The Korn Ferry research on AI leadership identified a pattern they named the “AI readiness paradox”: organisations place strong operators in AI leadership roles without the accountability structures those roles require. The operator is selected for general delivery credibility, but the specific question of where their authority starts and the founder’s ends goes unresolved.

Spencer Stuart’s research on executive AI sponsorship found that founders who delegate AI leadership while remaining disengaged produce a specific failure mode. The delegate absorbs the risk, escalates cautiously to avoid overstepping, and the pace of the programme drops to whatever the founder is willing to approve on any given day.

Both findings point to the same gap. A mandate without written decision rights assigns accountability without a matching grant of authority. The programme slows not because the delegate lacks capability but because the structure needed to act at pace was never put in place.

Where do the gaps show up in practice?

Gaps in decision authority tend to cluster at three types of decision. Vendor selection is one, where the founder has existing relationships and views on suppliers. Team-facing communications about AI direction are another. Spending calls within the agreed budget are the third, where the scope of what that budget covers may never have been made explicit.

Each of these three areas shares a characteristic. The founder did not necessarily intend to retain authority over them, and the delegate did not necessarily intend to overstep. The conflict emerges from a category of decision that was never discussed.

Harvard Law School’s research on AI risk disclosures found that reputational risk is the leading AI concern for a significant share of large companies, yet many organisations lack an accountable lead with the authority to install safeguards. The pattern appears at a different scale inside owner-managed businesses. The person responsible for AI outcomes often has no formal authority over the decisions that determine those outcomes.

A useful test before acting: ask whether the founder would be surprised by the decision in a week’s time. If yes, it belongs in the conversation before action is taken, not after. If no, make the decision and note it at the next check-in. This handles the majority of ambiguous calls without requiring a formal escalation for every decision.

When should you act alone, and when do you bring the founder back in?

A working rule that holds up under pressure is this. Operational decisions within the agreed mandate are yours to make and own. Decisions that touch the founding team directly, commit the business to a new supplier relationship above a defined spend level, or change how AI is described to clients or investors belong to the founder before they happen, not as a report after.

The threshold amount matters less than the agreement that a threshold exists. Many founders will not overrule a decision made within a clear mandate, even if it was not precisely what they would have chosen. What they respond badly to is surprise. Putting something on the shared agenda before a decision is made, even briefly, lands very differently from reporting a done deal.

McKinsey’s 2025 research on AI programme effectiveness found that organisations producing measurable AI outcomes consistently had named ownership combined with cross-functional authority to act on it.

Giving the delegate enough autonomy to decide in real time, then aligning with the founder regularly to confirm the boundaries hold, is the working structure. A monthly check-in in the early months of the programme keeps the arrangement calibrated. The agenda is a two-way reset, short enough to stay on the founder’s calendar and specific enough to give the delegate a refreshed mandate to carry back into the work.

How do you start the conversation without it reading as a power grab?

Frame the conversation around the founder’s time, not the delegate’s authority. “I want to make sure I’m bringing the right decisions to you, not adding to your week with things I should own” lands very differently from “I need to know what my authority is.” The first version is already aligned with what the founder wanted from the delegation. The second sounds like a territorial negotiation.

The document that comes out of the conversation does not need to be formal. A one-page written summary, shared by email and confirmed as agreed by both parties, is enough. It just needs to exist outside anyone’s memory.

NACD’s AI governance guidance emphasises that accountability without corresponding authority is the condition that generates AI risk, not the technology itself. The delegate who agrees their decision rights in writing has addressed that gap at the programme level, without needing a governance framework built for an enterprise.

On paper, the useful categories are which calls the delegate owns outright, which decisions need the founder before action is taken, and the spend threshold above which anything escalates. Once those are agreed, the question about any specific decision shifts from “whose call is this?” to “does this fall inside or outside what we agreed?” That is a much shorter conversation, and one the programme can hold at pace.

The Paro research on effective delegation found that the delegation trap, in which a delegated lead absorbs risk without authority over the decisions that shape outcomes, is most reliably broken by a written accountability map. The map needs to be agreed, not elaborate.

The conversation is worth having before the programme starts. The later it runs, the more decisions have been adjusted in ways that shift the shape of the mandate, often without either party realising it until something breaks. An hour spent agreeing what is yours to decide, and writing it down, is the most direct investment you can make in a programme that keeps moving.

Sources

- BCG (2025). The AI Adoption Puzzle: Why Usage Is Up But Impact Is Not. Analysis of the accountability and governance gaps that prevent AI from generating business impact despite rising usage. https://www.bcg.com/publications/2025/ai-adoption-puzzle-why-usage-up-impact-not - Spencer Stuart (2025). Don't Delegate AI: A Power User Playbook for CEOs. Research on how founders who disengage from AI oversight create governance vacuums that reduce their delegate's operating authority. https://www.spencerstuart.com/research-and-insight/dont-delegate-ai-a-power-user-playbook-for-ceos - Korn Ferry (2025). 6 Signs Leaders Lack AI Readiness and How to Fix It. Identifies the AI readiness paradox, in which strong operators are placed in AI leadership roles without the accountability structures the mandate requires. https://www.kornferry.com/insights/featured-topics/gen-ai-in-the-workplace-articles/6-signs-leaders-lack-ai-readiness-and-how-to-fix-it - McKinsey (2025). Superagency in the Workplace. Research finding that organisations producing measurable AI outcomes consistently had named ownership with cross-functional authority to act. https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/superagency-in-the-workplace-empowering-people-to-unlock-ais-full-potential-at-work - OECD (2025). AI Adoption by Small and Medium-Sized Enterprises. International evidence on the governance challenges accompanying AI adoption in owner-managed businesses, including accountability structures and decision authority. https://www.oecd.org/en/publications/2025/12/ai-adoption-by-small-and-medium-sized-enterprises_9c48eae6.html - National Association of Corporate Directors (2025). Implementing AI Governance: Director FAQs and Essentials. Guidance on the board-level principle that accountability without corresponding authority is the condition that creates AI risk, not the technology itself. https://www.nacdonline.org/all-governance/governance-resources/governance-research/director-faqs-and-essentials/implementing-ai-governance/ - Harvard Law School Forum on Corporate Governance (2025). AI Risk Disclosures in the S&P 500: Reputation, Cybersecurity and Regulation. Documents reputational risk as the leading AI concern for a significant share of large companies, while noting that accountable leads often lack authority to install safeguards. https://corpgov.law.harvard.edu/2025/10/15/ai-risk-disclosures-in-the-sp-500-reputation-cybersecurity-and-regulation/ - ESG Dive (2025). Executives Fear Job Loss Due to AI. Survey finding that approximately 61% of senior operators handed AI mandates report significant professional exposure when the scope of their authority is unclear. https://www.esgdive.com/news/execs-fear-job-loss-due-to-AI/818075/ - Paro (2025). Redefining Ownership: Effective Delegation. Analysis of the delegation trap, in which a delegated lead absorbs risk while the founder retains control of the resources and decisions that shape outcomes. https://paro.ai/blog/redefining-ownership-effective-delegation/

Frequently asked questions

What should a decision-rights framework for an AI lead include?

A written decision-rights framework should cover three categories. The first is which calls the delegate makes independently. The second is which decisions need founder sign-off before action. The third is the spend threshold above which anything escalates, regardless of category. It should also name communication domains where the founder keeps approval rights, such as investor-facing statements about AI. One page is sufficient.

How often should a delegated AI lead revisit their decision boundaries with the founder?

Every four to six weeks is a useful cadence in the early months of a programme, before the mandate has had time to settle. The purpose is less about reporting progress and more about resetting the shared understanding of what falls inside and outside the delegate's authority. As trust builds and the programme finds its rhythm, these check-ins can move to quarterly without losing their value.

What do you do when the founder keeps overriding decisions that were agreed as yours to make?

Surface the pattern explicitly and frame it as a question rather than a complaint. A phrase such as 'I've noticed a few of the calls I made last month have been adjusted, and I want to make sure I understand where the line should sit' opens the conversation without accusation. If the founder's boundary keeps moving despite the conversation, that signals a deeper issue with the mandate itself, which needs addressing before the programme can progress.

This post is general information and education only, not legal, regulatory, financial, or other professional advice. Regulations evolve, fee benchmarks shift, and every situation is different, so please take qualified professional advice before acting on anything you read here. See the Terms of Use for the full position.

Ready to talk it through?

Book a free 30 minute conversation. No pitch, no pressure, just a useful chat about where AI fits in your business.

Book a conversation

Related reading

If any of this sounds familiar, let's talk.

The next step is a conversation. No pitch, no pressure. Just an honest discussion about where you are and whether I can help.

Book a conversation