Twelve principles.
A better way
to decide.

AI demos are unusually cheap to build and unusually convincing to watch. That combination means visible activity can outrun actual performance for a long time — a growing portfolio of impressive pilots with no accountable value anywhere in it. The discipline is to translate every proposal into an owned business outcome with a baseline and a measure, before work starts. Not "we deployed a copilot" — "we cut claim-handling time 18%, and here's the owner who signed up for that number."

The fastest way to burn an AI leader — or a program — is responsibility without decision rights. If you are accountable for outcomes but can't approve, pause, or stop the work, you don't run the program; you narrate it. Authority needs to be written down: decision rights, budget visibility, escalation routes, named decision owners. And it needs to be tested on a real, survivable hard decision before it's tested on an existential one.

AI evidence decays. A model update, a data change, or a shift in how people actually use the system can invalidate a result that was true last quarter. Most organizations treat an evaluation as a one-time gate: passed it in March, cite it forever. The discipline is to capture the sources, assumptions, baselines, and economics behind every claim — and to re-earn confidence after material change, not just re-assert it. Deck claims that outlive their evidence are how programs end up confidently wrong.

Scaling an unproven use case doesn't multiply value — it multiplies cost, complexity, and eventual disappointment. The pressure to scale usually arrives before the proof does, because platform investment is easier to defend when it's serving "the whole enterprise." Set a measurable value threshold and fund the next stage only when the current one clears it. If the pilots can't show material benefit, the platform serving them is overhead, not infrastructure.

Autonomy changes the blast radius from an incorrect answer to an incorrect action. The labs themselves cannot fully keep their agents in the box — OpenAI, Anthropic, and Moonshot have all documented models escaping test environments. So the question inside your company was never "which model is safest." It's which permissions, human involvement, failure modes, monitoring, and stop conditions get defined before an agent touches production. If nobody has agreed what the agent may do and when it must stop, the deployment decision hasn't actually been made — it's just been defaulted.

A policy document cannot compensate for a control that's absent from the path of action. Shadow AI is the proof: usage policies everywhere, and 43% of breaches involving tools no one sanctioned. Controls work when they live in intake, identity, tooling, deployment, logging, and monitoring — the places where a risky action can actually be blocked and evidence actually accumulates. If you can't point to where in the workflow a risky action gets stopped, you don't have a control. You have a hope.

Enterprise AI creates a real tension between centralized control and local context, and neither extreme is safe by default. Full centralization produces a center of excellence that becomes a queue — owning neither adoption nor results. Full federation produces incompatible controls and duplicated spend. The working answer is a thin shared platform for the capabilities that benefit from consistency — gateways, evaluation, standards — with value and risk owned by the business units closest to the work.

Value appears only when a safe capability changes how work is actually performed. Licenses and launch announcements measure procurement, not adoption — and the quiet return to the old workflow is the most common failure mode nobody reports. Workflow redesign, manager reinforcement, enablement, and trust-building are not change-management garnish added after deployment; they are part of the use case itself, and they belong in its plan and its budget from the start.

Not every AI decision deserves the same speed. A bounded experiment you can unwind in a week should move fast — the learning is worth more than the risk. A one-way commitment — a platform standardization, a vendor lock-in, a workflow you can't restore — needs stronger proof and explicit exit criteria before you walk through the door. Organizations fail in both directions: freezing safe learning behind enterprise process, or rushing irreversible commitments because the demo was compelling.

AI fails silently — quality drift, bias, cost creep — and the person who championed the program has a built-in incentive to soften bad news about it. That combination is dangerous. The discipline is to surface limitations, dissent, incidents, and unresolved assumptions early, especially when they threaten the program narrative. Deloitte's fabricated-citations episode is instructive: the failure was expensive, but the disclosure and refund preserved something. Bad news that reaches executives after the customer or the board already has it costs far more than the underlying failure.

No model choice makes unavailable, untrusted, or unauthorized data a safe foundation. When an AI initiative fails on inaccessible, stale, biased, or improperly permissioned data, the model takes the blame — but the data condition was knowable in advance. Use data readiness, lineage, permissioning, and exposure evidence to rule a use case ready, constrained, or not suitable before committing to it. "Constrained" and "not yet" are legitimate answers that save quarters of wasted effort.

AI quality is probabilistic and context-dependent, and a fluent output is not evidence of fitness. A system is ready for production when there is a representative evaluation set, a rubric, a passing threshold, human review where it matters, and a trigger that catches regression afterward. Declared successful "because it demos well" is how fabricated citations end up in delivered reports. If no one can state the passing standard, the system hasn't passed anything.