Thursday, 16:20.
An AI model starts sending bad recommendations.
The steering committee meets on Monday.
The governance chart says, “The committee owns the decision.” The operating team now has two bad options. Wait four days while the problem continues, or act without authority.
On the operating floor, the governance chart has become a delay mechanism.
This is how sensible governance fails. The policy exists. The committee is senior. Everyone agreed on the process. Nobody can answer the question that matters at 16:20:
Who can stop the system now?
Committees set boundaries. People exercise rights.
Committees matter. They approve budgets, set risk tolerance and review the portfolio. They create the conditions for good decisions.
Operating events rarely respect meeting calendars.
A live initiative needs individual decision rights inside those conditions. Pause may belong to an operations leader. Funding may sit with the CFO. Rollback may belong to a technology owner. The holders can differ because the decisions require different evidence, speed and expertise.
Good governance distributes these decisions deliberately. Assign funding to the CFO, pause to operations, rollback to technology and escalation to risk when that matches the work. Concentration happens within each right. One person decides a specific question under agreed conditions.
The distinction between a role and a person matters.
The role makes the system durable. “Head of Customer Operations” survives a reorganization better than one employee’s name in a policy. The named person makes the right usable today. A live initiative must record who currently occupies the role, who receives the evidence and who is expected to act before the clock expires.
Record both the durable role and its current holder to avoid ambiguity during reorganizations or absences.
The committee can debate the evidence and review the result. One authorised person still makes the call within the agreed time.
Map seven rights before launch
For each material AI initiative, put a durable role, its current named holder, the activating evidence and the decision clock beside seven rights:
- Start. Move the initiative into active delivery.
- Fund. Release or withhold the next tranche of money.
- Review. Decide whether the evidence supports continued work.
- Pause. Halt activity while the team resolves uncertainty.
- Stop. End the initiative when its kill criteria are met.
- Rollback. Restore the previous live state when production performance becomes unacceptable.
- Escalate. Break a deadlock within an agreed time.
Filling the list exposes gaps that policy language can hide.
Teams often know who can start. They can name the sponsor, budget owner and delivery lead. Stop and rollback are weaker. Authority dissolves into “the business,” “technology,” “risk” or “the committee.” Those labels describe groups. They do not identify a decision holder.
Speed also reveals the design. If a team can launch within a day but must wait several days to stop, governance has optimized for expansion and delayed control. Stop authority should move at least as fast as Start. A live system needs pre-delegated rollback authority, with a clock that matches the harm it can cause.
Pressure-test the map
Consider NorthWave, a fictional telecom company testing an AI retention model.
Its role-level structure looks credible. The commercial leader sponsors the initiative. The CFO controls the next funding gate. The technology leader owns deployment. The team has a previous production state it can restore.
Then the pre-launch review asks who can act during a bad Thursday afternoon.
The rollback row says “engineering,” but names no current engineer. Pause has no decision clock. Stop has a role but no deadline. The escalation route does not distinguish a technical incident from a disagreement about the pilot’s economics.
NorthWave must repair the map before launch. The team needs to name the current holders, set the missing clocks and define where each type of deadlock goes. Its existing authority must become usable during the incident.
A worked example should expose a failure that a blank template lets you overlook.
Give the initiative a verdict
Read every row aloud as if the incident happened this afternoon.
The holder should recognize the decision as theirs. The evidence should tell them when the right activates. The clock should state the latest acceptable decision time. The team should know what happens if the holder is unavailable.
If every right works under that pressure, the map is Usable. One or two gaps that can close before launch produce Repair. Missing, committee-only or slower-than-Start stop and rollback authority means Redesign.
These verdicts do not replace your policy, control framework, legal review or operating model. They answer a narrower question: can your governance act when the system needs a decision?
Take one live AI initiative. Start with Stop and Rollback. Put the role, current person, activating evidence and decision clock on one page.
The first empty field shows where “committee-owned” will fail under pressure.
The instrument: AI Decision Rights Map. One page, fillable, free with your email.
Your move.