The Human and Machine Company Free → Read it
← Writing

You Don't Have an AI Problem. You Have an Authority Problem.

The companies that say they can't figure out AI can usually figure out AI just fine. What they can't figure out is who is allowed to say yes. Authority structure, not tool selection, is the binding constraint on AI value capture in the mid-market.

I run a diagnostic tool that scores companies across five dimensions of AI readiness: how widely you have adopted AI, who gets to make decisions about it, how deeply it fits into your actual work, how fast those decisions move, and whether the results show up in your financials. I’ve run enough of these now to know which dimension predicts the whole score.

Adoption predicts almost nothing, because almost everyone has already adopted. McKinsey’s 2025 State of AI survey found that 88 percent of organizations report regular AI use in at least one business function, up from 78 percent the year before. The tools are in the building.

The bottleneck is who gets to say yes. Specifically: who is allowed to approve an AI initiative, how many people have to agree, and what happens when two of them disagree.

The tools are in the building. The bottleneck is who gets to say yes.


The sign-off chain

Count the number of approvals an AI initiative needs between the moment someone identifies a use case and the moment a production budget is released. I call this decision distance. In the mid-market companies I work with, the number is usually four to seven. In Fortune 100 companies, it is twelve or higher.

The number matters because every sign-off is a potential stall. And AI initiatives stall differently than other technology programs. A CRM migration stalls because of data quality or change management. An AI initiative stalls because the person three levels up doesn’t really get what it does, and gets nothing for taking the risk of approving it.

RAND Corporation research found that 80 percent of enterprise AI projects fail to deliver promised business value. Of those failures, a third are abandoned before reaching production. The easy read is that the technology wasn’t ready. I don’t buy it. The organization wasn’t ready, and the piece that wasn’t ready is the one nobody wants to say out loud: who actually gets to decide.

80%of enterprise AI projects fail to deliver promised business valueRAND Corporation, 2025

The takeaway: every sign-off between a use case and a production budget is a place to stall, and mid-market chains run four to seven approvals long. Count your own decision distance before you blame the technology.


Governance is not the same as authority

Companies often respond to AI anxiety by building governance. A steering committee. A responsible-AI policy. An intake form. A quarterly review cadence. That’s all reasonable. None of it is the problem I’m describing.

Governance tells you what the rules are. Authority tells you who can say yes within those rules. The companies I see struggling have plenty of governance. What they lack is a clear, short path from “this workflow should change” to “here is the budget to change it.”

Governance tells you what the rules are. Authority tells you who can say yes within those rules.

ISS Corporate’s 2026 governance report found that only 22 percent of S&P 500 companies have disclosed board-level oversight of AI. The number for the mid-market is almost certainly lower. That means in most companies, AI decisions are being made by people who do not have explicit authority to make them. The work happens anyway, in gaps between job descriptions, and the results are invisible to the people who control budget.

The takeaway: governance sets the rules and authority names who can say yes inside them, and most companies built the first without the second. Put a name on the yes before you write another policy.


What the authority problem looks like in practice

Here is the pattern I see repeatedly. A director-level leader identifies a workflow that AI could meaningfully improve. Donor communications at a nonprofit, say, or renewal quoting at an insurance company, or proposal generation at a professional services firm. The leader does the research, maybe runs a pilot on a free tool, and gets promising results.

Then they try to scale it. They need budget, IT approval on the vendor, legal review of the data handling, and their VP’s sponsorship in the quarterly planning cycle. The VP needs to explain it to the CEO, who needs to feel confident enough to mention it to the board without sounding naive.

Each of those conversations gives the initiative a new place to die. Nobody says no. The yes just never comes fast enough, and the window closes, and the next quarter’s priorities take over.

Grant Thornton’s 2026 AI Impact Survey found that three out of four organizations admit their governance has not kept pace with AI adoption. The mechanism is diffuse authority, not strict governance. When everyone has to agree, nobody has to decide.

The takeaway: an AI initiative dies of slow yeses, one stalled conversation at a time. Cut the conversations between pilot and production budget before you launch the next one.


The mid-market version of this problem

Large enterprises have the authority problem for structural reasons: complex org charts, matrix reporting, and multiple P&L owners. The mid-market has it for a different reason, and the reason is more fixable.

In most mid-market companies I work with, the senior team is small enough that authority could be clear. Five to fifteen people make every important decision. The problem is that AI does not fit neatly into any one person’s domain. It touches IT, operations, and strategy without belonging to any of them. So it floats between the three, and each of those leaders assumes someone else is driving it. Nobody is.

The fix is specific and unglamorous: name one person who owns AI outcomes. Governance and policy are different jobs. Give that person a budget, a kill threshold, and a reporting line to the CEO. The RSM 2025 Middle Market survey found that 91 percent of mid-market executives have adopted generative AI, but only 25 percent have it fully integrated into core operations. The gap between those two numbers is an authority gap.

91%of mid-market executives have adopted generative AIRSM, 2025
25%have it fully integrated into core operationsRSM, 2025

The takeaway: AI floats between IT, operations, and strategy until one person owns the outcomes. Name that person, then hand them a budget, a kill threshold, and a reporting line to the CEO.


The test

Here is how to know whether you have an authority problem. Answer three questions honestly.

If someone on your team found an AI tool tomorrow that could save $200,000 a year in a single workflow, how many weeks would it take to get a production budget approved? More than six weeks means you have an authority problem.

If that same person’s pilot failed after eight weeks, would anyone formally kill it and reallocate the resources? When the answer is “it would probably just quietly stop,” you have an authority problem.

Is there one person in your company whose job title or written mandate includes the phrase “AI outcomes” or “AI value capture”? If the answer is no, you have an authority problem.

The companies that close the gap between adopting AI and getting paid for it have the same tools you do, plus one person who’s allowed to make the call, funded to run with it, and on the hook for the number. That’s the whole difference.

The Authority Test

  1. How many weeks to approve a $200K AI savings opportunity? More than six = authority problem.
  2. Would a failed pilot get formally killed and resources reallocated? “It would quietly stop” = authority problem.
  3. Does anyone’s written mandate include “AI outcomes” or “AI value capture”? No = authority problem.

How RLK Can Help

My AI Diagnostic scores how decisions get made in your company alongside four other dimensions and shows you exactly where the friction sits. If the score confirms what you already suspect, the AI Strategy Session is a focused engagement that maps authority to outcomes and builds the decision framework your team is missing. Get in touch.


Sources

Ryan King

About the author

Ryan King

Fifteen years in technology strategy at McKinsey and Deloitte. Now running RLK Consulting: enterprise-caliber tech strategy, one strategist doing every hour of the work. Over $10B in documented value capture across 50+ engagements and 12 industries.