AI Transformation · Authority
Decision Authority Must Follow AI Economics
Two AI budgets do not create ownership. They can create two partial views of the same unowned decision.
Key Takeaways
- Access spending buys the ability to use a capability and is predictable. Execution spending is what a governed outcome costs, including verification, exception handling and rework, and it is variable, lands elsewhere, and is usually unmeasured.
- Splitting the budget is the easy half. Deciding whether decision rights follow the money is the half organizations skip, and it produces accountability without authority: a function owning an outcome whose determining decisions all sit somewhere else.
- The measure that resolves it is cost per governed outcome, with verification and rework inside the number rather than beside it, and one named economic owner per funded capability.
Two kinds of spending, one of them invisible
Access spending is what it costs to be able to use something: platform, licences, infrastructure, seats. It is forecastable, it lands in one budget, and it is what almost every AI investment review actually reports. Execution spending is what it costs to get an outcome anyone will accept: the inference itself, plus verification, plus the handling of everything the system got wrong or refused, plus the rework, plus the controls that make it acceptable to run at all.
The two behave differently in every way that matters. Access spending is fixed and visible. Execution spending is variable, arrives in a different budget from the one that approved the purchase, and is frequently not measured because no line item was created for it. An organization can therefore report a falling cost per token while the cost per outcome it can actually use is rising, and both numbers are correct.
Four partial views, each locally correct
The failure is not that anyone is wrong. It is that each participant optimizes what they can see, and the thing nobody can see is the tradeoff.
| Function | Sees | And therefore optimizes |
|---|---|---|
| IT | Platform and licence cost | Utilization. An under-used platform looks like waste, so the incentive is adoption regardless of what the adoption produces. |
| The business | Process value | Throughput. Speed is visible and verification is not, so the incentive runs against the control that makes the output usable. |
| Finance | Budget variance | Predictability. Variable execution cost reads as a forecasting failure rather than as the actual shape of the thing being bought. |
| Risk | Exposure | Containment. The cost of a control is borne by someone else, so there is no counterweight to adding one. |
Alchian and Demsetz named this in 1972 as the metering problem of team production: where output is joint, no participant can attribute it, so each optimizes their own measurable contribution. The organizational answer they proposed was a monitor with the residual claim, meaning someone who bears the consequence of the whole. Most AI programs have four monitors and no residual claimant.
A shared budget with no owner is a commons
Hardin's account of the commons is usually invoked to argue that shared resources are doomed. Elinor Ostrom spent a career demonstrating that they are not, and her conditions are unusually applicable here: clearly defined boundaries, rules matched to local conditions, those affected participating in setting them, monitoring by people accountable to the users, and graduated sanctions. Every one of those is a governance design choice that a split AI budget typically leaves unmade.
The relevant one is the first. A commons fails when the boundary is undefined, and an AI platform funded centrally and consumed by everyone has no boundary at all unless someone draws it. Drawing it is not a budgeting exercise. It is an authority decision about who may consume what, up to which limit, and who says no.
Why owning the outcome does not settle it
The standard resolution is to say the business owns the outcome. It sounds decisive and it usually is not, because owning an outcome is not the same as holding the rights that determine it. A function can be accountable for a process result while the model choice, the spend ceiling, the exception policy and the stop condition all sit with someone else. That is accountability without authority, which reliably produces a result nobody can be held to and an argument afterwards about whose fault it was.
Jensen and Meckling made the general case in 1992: decision rights should be co-located with the knowledge needed to exercise them, and the cost of moving knowledge is what determines which way the co-location should run. For AI economics the knowledge is split by construction. The platform economics live in IT and the exception economics live in the business, so neither pure centralization nor pure delegation is right, and the design has to name which specific decisions go which way.
The unowned-decision test
Take one AI capability in production and ask who may decide to run it more expensively in order to make it more accurate. If the answer is a forum, a steering group, or "we would discuss it", that decision is unowned. It is also the decision that determines whether the investment returns anything, and it is being made by default every day the question is not asked.
The AI Economic Authority Map
One row per funded capability. The fourth and seventh columns are the ones that reveal whether anything is actually owned.
| Column | The question it forces |
|---|---|
| Funded asset | What was actually bought, and out of whose budget? |
| Business outcome | Which process result is this supposed to change, stated so that a failure would be visible? |
| Cost owner | Who absorbs the spend, including the execution spend rather than only the access spend? |
| Decision owner | Who may trade speed against control, and cost against quality? One name, not a forum. |
| Risk owner | Who accepts the residual exposure, and did they agree to it in those words? |
| Exception threshold | At what exception rate do the economics stop working? Stated as a number before launch, not discovered after. |
| Stop condition | What ends this, and who is permitted to end it? |
Pricing the parts nobody prices
Verification, exception handling, rework and control are the costs that convert a raw output into a usable one, and they are almost never in the business case. Time-driven activity-based costing is the ordinary tool for this and it applies without modification: estimate the time each activity consumes and the cost of supplying that capacity. The point is not precision, it is inclusion. A cost per outcome that excludes verification is not a conservative estimate, it is a measurement of something the organization cannot actually use.
Your AI Metrics Measure Expense makes the adjacent argument about what adoption metrics leave out, and Measure the Outcome, Not the Interaction takes up the substitution of activity for result.
The Four A's reading
This is Authority presenting as a finance problem, which is what makes it hard to see. Every symptom is budgetary: variance, forecast misses, disputes about which cost centre absorbs an overrun. The cause is that a decision was divided without being assigned, and no amount of better cost allocation fixes an unowned decision.
Alignment is the second half. Four functions holding four partial and locally correct views is not disagreement, it is the absence of a shared picture, and it will not resolve through discussion because each view is right about the part it can see.
About the Author
Dan Flynn
Creator of The Four A's of Organizational Readiness™ · Enterprise Transformation Executive · Author, Builders Build
Dan Flynn has spent thirty years inside federal, defense, and commercial organizations: diagnosing the invisible conditions that determine whether capable people produce extraordinary results. He is the creator of The Four A's of Organizational Readiness™ framework, has reached more than 11,000 professionals across corporate, civic, and national security contexts, and took a federal data platform from one release every six months to seventy-two every two weeks by changing organizational conditions: not people.
His book, Builders Build: The Four A’s of Organizational Readiness™, is forthcoming.