Every few weeks I sit across the table from a different seat inside a live enterprise AI rollout — a board member, a CIO, a CFO, a COO. Each one asks a slightly different version of the same handful of questions. This is the first in that series, written from what I've actually heard in those rooms, not from a framework I built afterward. This one is for the board.
Most boards get the same three updates every quarter. IT says the rollout is deployed and adoption is climbing. Finance says spend is inside budget, mostly. Operations says the workflows are being modernized, one initiative at a time.
Each of those reports is true. Taken together, they still don't answer the one question you actually need answered: did the thing you approved change an outcome, or did it just get installed? Somewhere along the way, boards started accepting "we deployed it" as if it answered that question. It doesn't. It's a status update, not a result.
Here's the part that isn't your fault, even though it lands on you.
You're not getting three different stories because someone below you is hiding something. You're getting three different stories because no one in the building has been given the job of reconciling them. That job was never supposed to be optional — it just never got assigned to anyone.
I recently asked several CIOs and COOs who they thought was doing the blaming when an AI initiative underperformed. One answer stuck with me: "I don't see as much finger pointing and blaming as I do see a lot of confusion. Leaders are looking at each other for the guidance that no one in the org has to give."
That's not incompetence. It's an org chart with no "seam" owner. And it means your board inherited the confusion without anyone telling you that's what you were actually looking at.
In seven years selling ServiceNow, I watched a version of this play out long before AI made it fashionable to talk about.
A CIO had a real target: cut mean time to resolution by 15%, using automation to close more tickets without adding headcount. Leadership approved the initiative, watched the demo, and moved on to the next priority. The project team inherited it. Nobody had told them the number was the point, so they built the new workflow to look familiar instead of building it to be impactful.
Six months passed. The number hadn't moved. They blamed the vendor.
We got on a call and asked them to demo back what they'd actually built. The CIO watched his own team walk through it, live, and caught the problem himself — mid-call, before anyone on our side said a word.
That's the CIO's version of the gap: real approval at the top, and no owner standing between that approval and the outcome it was supposed to produce.
Finance's version of the gap looks different, but it's the same gap. I've had close to this exact call, almost word for word, from several CIOs and COOs this year: "We've spent a ton of money and have nothing to show for it." Usage is fine. The bill keeps climbing. Nothing has moved — not cases closed, not revenue, not output. Somewhere along the way, adoption and token spend became the metric. That might be the only category in business where success gets measured by an expense going up.
Here's the image that's stuck with me since I first heard it: it's mileage counted as arrival. Picture someone burning a full tank of gas driving in circles on a roundabout. The bill for the gas is enormous. They haven't gone anywhere.
Operations has a version too. Workflows get "modernized" one at a time. Each change is defensible on its own. None of them add up to the initiative the board actually funded.
Same failure. Three departments. Three vocabularies. From where you sit, three unrelated line items on three separate updates.
Most boards go straight to the governance question. How many committees. Who signs off. What's the review cadence.
Those are the wrong first questions. The real question underneath all of them is simpler: what level of risk is this organization actually willing to carry, in concrete terms? Most boards never answer that one before they start building the structure that's supposed to manage it.
Undefined risk appetite doesn't produce caution. It produces ceremony. Reviews multiply because nobody defined what didn't need reviewing, so everything becomes an exception, and every exception gets escalated. A governance consultant will tell you the review process is the control. I think it's usually the symptom.
There's a diagnostic here that costs nothing and doesn't require hiring anyone: look at your own change management process. If everything in it gets escalated, nobody has defined what's acceptable. Your AI governance structure is about to inherit that same bloat, for the same reason.
Here's my answer, for what it's worth: the number of committees matters less than you think. What matters is whether one person owns reconciling IT's fix, Finance's fix, and Operations' fix against the same outcome. Committees don't produce alignment by existing. A named owner does.
That answer will look different at a 2,000-person telecom than at a 200-person fintech — the shape of the seat changes, not the requirement that someone sit in it. What I'd ask at your next board meeting isn't "is it deployed." It's this: what risk tolerance did we actually approve, and where would we see it if we looked at our own change process? Watch who in the room can answer that cleanly. That's your "seam" owner, whether the org chart says so yet or not.
— Isaac