Scott Wueschinski
← All articles

Insight

Pilot governance is the bottleneck, not pilot funding

Most retail AI pilots don't fail at the model. They fail at the gate. Three governance moves separate pilots that scale from pilots that quietly die — all upstream of any AI investment.

· 5 min read

Most retail AI pilots in 2026 don’t fail at the model.

They fail at the gate. Specifically, they fail at one of three governance moves that separate pilots which graduate to production from pilots which quietly die in steering committee.

The conversation in the boardroom is usually about funding — should we approve another $5M for AI pilots? — but the pilots already running are stuck for reasons that have nothing to do with money. They’re stuck because nobody owns the graduation criteria, nobody owns the kill criteria, and nobody owns the decision rhythm that should connect the two.

This article is the operating model fix. It assumes you already have AI pilots in flight; the question is what’s stopping them from compounding.

Why “more funding” is the wrong answer

The retail CDO instinct when pilots stall is to ask for more pilot money. More pilots, more vendors, more proofs-of-concept. The thinking goes: if we run enough pilots, one will work and we’ll scale that one.

The data does not support that thinking. The retailers I see compounding AI wins in 2026 are not the ones running the most pilots. They’re the ones whose pilots graduate to production at higher rates. The funnel between pilot and scaled deployment is what matters; pilot count is secondary.

What governs that funnel is governance, not funding. Specifically, three moves:

Move 1: Define graduation criteria before the pilot starts

The most common pilot-governance failure I see: nobody wrote down what “graduate to production” means before the pilot started.

Without explicit graduation criteria, every pilot defaults to “we learned a lot, let’s try another version.” The vendor produces a deck. The team produces talking points. The CDO defends the pilot at the next steering committee. Six months pass. The pilot is “still running” — which is a polite way of saying it has neither graduated nor been killed.

The fix: every pilot has a one-page brief, signed before kickoff, that names:

  • The KPI the pilot must move (one number, not three)
  • The threshold that constitutes graduation (e.g., “8% lift on conversion in the test cohort, statistically significant at p<0.05”)
  • The threshold that constitutes failure (e.g., “less than 3% lift, or null result”)
  • The named executive who owns the graduate-or-kill decision
  • The date by which that decision happens (90 days from kickoff, in most cases)

Without all five, the pilot has no gate, and ungated pilots run forever.

Move 2: Run pilots against real organizational gravity

The second governance failure: pilots run against synthetic data, sandbox environments, or carved-off cohorts that don’t reflect the operating reality of the business. The pilot succeeds inside the sandbox; the production deployment fails because the production environment has constraints the sandbox didn’t.

This is more common than retail leaders admit. Vendors prefer sandboxes because sandboxes don’t have the messy data-quality issues, change-management resistance, and integration debt that the real environment has. Pilots in sandboxes look good on slides.

The fix: pilots run against a real slice of operations from week one. A real store. A real customer cohort. A real merchandising team using their real systems. The pilot’s success isn’t whether the model works on clean data — it’s whether the operational layer absorbs the model’s output and acts on it inside the real workflow.

This rules out a class of vendors that rely on sandbox demos. That’s a feature, not a bug. The vendors whose models can survive the real environment are the ones worth scaling; the ones that need a sandbox to look good are the ones that fail at production deployment.

Move 3: Name a single executive who owns the decision

The third — and most often violated — governance move: every pilot has a single named executive who owns the graduate-or-kill decision.

Not a steering committee. Not “the AI council.” Not “the CIO and the CMO and the CDO will discuss it.” A single person whose name is on the brief, whose calendar has the decision date blocked, and whose performance review references the outcome.

The reason this matters: ungated decisions default to “extend the pilot.” A steering committee’s median behavior, when faced with a pilot that’s neither obviously winning nor obviously dying, is to ask for another quarter of data. That’s the failure mode. Single-owner decisions force a binary outcome.

The objection retail CDOs raise is that AI decisions feel too consequential to land on one executive. The answer is that ungated decisions are more consequential, not less, because they let the pilot drift indefinitely. The cost of ambiguity dwarfs the cost of a wrong decision made on time.

What governance looks like when these three moves are in place

A retail organization that has graduation criteria, real-environment pilots, and named decision owners produces a different funnel:

  • ~35-50% of pilots graduate to production within their stated decision window. (Industry default without governance: 5-15%.)
  • ~30-45% are explicitly killed at the decision date. (Industry default: ~15%.)
  • ~15-25% are extended for one specific, time-boxed reason. (Industry default: ~70% — and most of those extensions become permanent.)

The kill rate is the underrated number. A team that kills 35% of pilots on time is healthy. A team that kills 5% is running pilot theater — extending everything because nobody owns the decision.

What this means for the AI investment case

When the board asks the CDO for another $5M of AI funding in 2026, the wrong answer is to defend the pipeline of pilots in flight. The right answer is to defend the governance funnel: how many pilots graduated last quarter, how many were killed on time, how many are extended and why.

If the governance funnel is healthy, the board approves the funding because the dollars compound. If it isn’t, more funding makes the problem bigger — more pilots stuck in the un-graduated middle, more vendor relationships sitting in maintenance mode, more steering committee time spent on extensions.

The governance fix is upstream of the funding fix. It almost never is the fix the board asks for, and it almost always is the fix that changes the trajectory.

The CODN angle

The cost of the un-governed pilot funnel is not the pilot dollars. It’s the compounding gap against the cohort that fixed governance two cycles ago.

That cohort:

  • Has 2-3 production AI deployments compounding feedback data the un-governed retailer doesn’t have.
  • Has institutional muscle memory for the graduate-or-kill decision, so the next pilot moves faster.
  • Has freed up CDO and steering-committee attention because pilots don’t drag on indefinitely.

By the time the un-governed retailer is ready to ask the right question — “why aren’t our pilots graduating?” — the governed retailer has been compounding for 12-18 months. The CODN of un-governed pilots is roughly: 2x the AI investment for half the production capability, plus a structural attention drag at the executive layer.

The bottom line

Pilot governance — graduation criteria, real-environment exposure, single-owner decisions — is the bottleneck, not pilot funding.

Fix the governance funnel and the same dollar of AI investment yields 3-5x more production capability. Don’t, and more funding makes the pile of un-graduated pilots bigger.

This is the question the next board memo on AI investment should answer. Most CDOs are still answering the wrong one.