Skip to content
Français

The governance board

  • Lesson 17
  • 30 min
  • Module 6: Run governance

Where we are

In Module 5, we turned each policy line into a control, a document and evidence that an auditor can check. But controls do not decide. Somebody must still say yes or no to new requests, exceptions and risks, without becoming a gate that never opens. In this lesson, we set up a governance board, the way a town handles building permits.

What you will be able to do

Give every AI decision one clear place where it is made, at a speed that matches its risk. Then keep a record that says who decided, and why.

Before you startWhat to know and to have readyAbout 30 minutes

What you need to know

What you need

You want to build a fence around your garden. You fill in a short form at the town hall. A clerk checks it against the rules, and you have an answer within a few days.

Your neighbour wants to build a block of flats. That goes to the planning committee. The committee meets every two weeks, with a fixed agenda. It reads the plans and hears the people who live nearby. Then it decides: yes, no, or yes with conditions, such as “keep the trees on the street side”. The minutes say who decided and why, so anyone can check it later.

If every fence went to the committee, the flats would wait, and people would start to build fences without asking.

The problem: decisions with no place to happen

Section titled “The problem: decisions with no place to happen”

Before Larkfield had a board, nobody had the job of saying no. In the “last week” of MLOps and LLMOps: Operating AI in Production, version 3 of the triage prompt went to every customer without the release gate. 10 tickets that needed a person reached nobody. The answers are recorded by that course; the situation is constructed.

The check existed. When the course ran the release gate on version 3 afterwards, it passed 0 of 6 checks (calculated from the recorded results and the MLOps course’s gate). But no person had to look at that result before the release. And no record showed who said yes.

The opposite mistake is just as real. If every small change waits weeks for one busy group, teams learn to go around it. A slow gate does not stop risky work; it hides it.

A governance board is a small, named group. It decides what the fast paths cannot decide, on a fixed rhythm, within a time limit, and it writes each decision down. It is the planning committee. The fast path is the clerk at the counter.

A one-page terms of reference says how the board works. Larkfield’s first version is in the labs (constructed). Read it as eight answers:

  • Purpose: decide what the fast paths cannot, keep risks and exceptions under control, and learn from incidents.
  • Chair: Nadia, the executive sponsor. Members: Farida (risk and compliance, and secretary), Grace, Mei, Kwame and the finance lead. The accountable owner of each system on the agenda attends for that item. The outside lawyer and security are asked when needed.
  • It decides: high-tier launches and changes, exceptions to policy, vendors for medium- and high-tier uses, and what to change after an incident.
  • It does not decide: low-tier requests (the fast path: the owner and the risk lead, within 2 working days), or medium-tier changes that pass their checks (the accountable owner, with a decision record).
  • Rhythm: every two weeks, for 45 minutes. A serious incident gets an extra meeting within 2 working days.
  • Time limit: 10 working days at most for a complete request. A request that is not complete goes back within 2 days, with a list of what is missing.
  • Records: minutes, a decision record per decision, and a scorecard each quarter.
  • Quorum: the chair or the risk lead, and at least three members.

One point is easy to miss. The board decides whether a change may happen. It does not take over the system. Grace still answers for the refund workflow after the board says yes, so she attends when it is on the agenda.

A decision flow for one request. Are the papers complete, and is it an AI use? No: back to its owner, within 2 working days with what is missing, or within 1 day if it is not an AI use. Yes: what is the tier? Low: fast path, the owner and the risk lead, 2 working days at most. Medium: is it a vendor or an exception? No: the owner decides after the tier's checks, with a decision record. Yes: the board. High: the board, at the next meeting, 10 working days at most, with a minutes line and a decision record. Fast-path and owner decisions are listed at the board for information.
Where a request goes. Only high-tier requests, vendors and exceptions reach the board; every path ends in a record.
Text description of the diagram

Incomplete papers go back within 2 working days, with what is missing. A request that is not an AI use goes back to its owner within a day. Otherwise the tier decides. Low tier: the fast path, where the owner and the risk lead decide within 2 working days. Medium tier: the accountable owner decides after the tier’s checks, with a decision record. Vendors and exceptions go to the board. High tier: the board, at its next meeting, within 10 working days, with a minutes line and a decision record. The board sees fast-path and owner decisions for information only.

A tiny example: three requests, three paths

Section titled “A tiny example: three requests, three paths”

Farida follows the flow for three requests from the board’s first quarter (a constructed log).

  1. R-07: let the document assistant answer the partner shop’s new staff. It is an AI use, and the document assistant is low tier. So it takes the fast path. Farida and the owner said yes in 2 working days. The board sees one line about it, for information.
  2. R-08: raise the workflow’s monthly budget. The workflow is medium tier, and this is not a vendor or an exception. So the owner decides after the checks, and writes a decision record. It took 1 working day.
  3. R-06: change the triage prompt to version 3. The triage service is high tier, so the board decides. It took 7 working days, and the decision was rejected.

The third request needs a record that a stranger can read in a year. Farida wrote this one (written for this lesson; the gate result is calculated):

Field R-06
Decision Do not release version 3 of the triage prompt.
System and tier Ticket triage service; high
Requested by Amira, the developer
Decided by The board: Nadia (chair), Farida, Grace, Mei, Kwame; Amira attended for the item
Options considered Release to all; release to a small share of tickets first; not yet; no
Evidence used The release gate on version 3: 0 of 6 checks passed, with one blocker ticket (T-65663)
Conditions None
What would change this decision A new version that passes all 6 checks
Review When a new version is ready

And the minutes need only one line: R-06 · rejected · the release gate passed 0 of 6 checks · no conditions · decision record R-06. The minutes say what was decided. The record says why, and what would change it.

A board meeting is short because the papers do the work. A request without its papers moves to the next meeting.

The board's agenda. Papers go out 2 working days before. One meeting of 45 minutes, every two weeks: 1 incidents and complaints, 10 minutes; 2 decisions only the board can make, 20 minutes; 3 fast-path and owner decisions, for information, 5 minutes; 4 scorecard, risks and exceptions near their end, 5 minutes; 5 rule watch, 5 minutes. Then minutes, one line per decision with the decision, the reason and the conditions with an owner, and a decision record for each decision.
One board meeting: 45 minutes, in a fixed order. Incidents come first, because they show what the earlier decisions missed.
Text description of the diagram

Papers go out two working days before. The 45 minutes have five items: incidents and complaints (10 minutes); decisions only the board can make (20); fast-path and owner decisions, for information (5); the scorecard, risks and exceptions near their end (5); and the rule watch (5). The minutes have one line per decision, with its reason and its conditions, and each decision gets a decision record.

Item 3 is “for information” on purpose. If the board approved fast-path decisions again, the fast path would become a slow path with one extra step.

Farida shows the draft terms to the team.

  • Omar: “Every new committee slows us down. Let each team decide for its own systems.”
  • Tomás: “Governance is the legal team’s job. The lawyer should chair it.”
  • Sam: “Why does the accountable owner come only for their own item? Shouldn’t the owners all be members?”

Before you read on, answer these:

  1. What goes wrong with each of the first two proposals?
  2. Why is Nadia the chair, and not Farida?
  3. Answer Sam’s question.

The course’s answer. Omar is right for most requests, and the flow already lets teams decide them: low tier on the fast path, medium tier by the owner. But a team should not be the only check on its own high-tier change. The person who asks for a change cannot be the only check on it.

Tomás’s board would ask the wrong questions. Most of Larkfield’s decisions are about customers, data and money, so the board asks the lawyer only when it needs a legal answer. Nadia chairs because she sponsors the work and can weigh speed against risk with authority. Farida is the secretary: she prepares the papers and checks them, so she cannot also be the final judge.

Sam: a board of every owner would be too large to decide in 45 minutes. The owner attends for their item because they know the system and still answer for it afterwards.

What would change the answer: a company with five staff and one low-tier tool needs no board; the owner and one reviewer are enough. A board is worth its cost when there are high-tier systems, vendors or exceptions.

Six people for 45 minutes cost four and a half hours of work every two weeks, plus the papers. That is cheap if the board decides only what needs it, and expensive if it spends its time on fences. So write the fast paths into the terms and set a time limit.

Common mistake

The board that decides everything

Symptom: the agenda is full of small requests, decisions take weeks, and the board approves almost all of them with no change.

Cause: the fast path exists on paper, but people send low-tier requests to the board “to be safe”.

Fix: make the path a rule: a low-tier request goes to the fast path, and the board sees it only in item 3. Then measure the time to decision by tier, so that the next quarter shows whether the rule works.

Guided practice: check where each request went

Section titled “Guided practice: check where each request went”
  1. Open the first-quarter log in a spreadsheet.

  2. Add a column “path by the terms”.

  3. For each request, follow the decision flow, and write the path it should have taken.

  4. Compare your column with the “Path” column.

    Check: five requests took a different path from the terms.

  5. Write the five IDs and the reason for each.

    Check: four are low tier at the board (R-01, R-03, R-09, R-11). One is not an AI use (R-05).

  6. Look at R-04. It is medium tier, but it went to the board.

    Check: that is right. It is a vendor for a medium-tier use, and the board decides vendors.

The next meeting has two requests for review (R-12 and R-04 again), incident INC-07 and complaint CMP-14. They are in the labs as requests for review. Write the agenda: put each item under its number, list the papers it needs, and name who must attend for it. You decide on these items in the next lesson.

Show one possible answer
  • Item 1, incidents and complaints: INC-07 and CMP-14. Papers: the incident and complaint records and Grace’s weekly sample. Grace attends, as accountable owner of the refund workflow.
  • Item 2, decisions: R-12 (high tier after the change). Papers: the impact assessment from Module 3, the system card and the evidence from the agents course; Grace and Amira attend. R-04 (a vendor for a medium-tier use). Papers: TicketHarbor’s answers (a vendor made up for this course) and the vendor questionnaire. Grace attends as the proposed accountable owner, and the finance lead, who owns the contract, is a member.
  • Items 3 to 5: the list of fast-path and owner decisions; the scorecard and the two exceptions past their end date; the rule watch.

Check your understanding

Omar says: 'Once the board approves R-12, the board owns the refund workflow, so Grace is no longer responsible.' What is wrong?

Show the answer

The board decides whether the change may happen, and on which conditions. It does not take over the system. Grace is still the accountable owner: she answers for the refunds, owns the conditions given to her and can stop the workflow. That is why she attends the board for this item.

Check your understanding

Predict: Mei asks to give the document assistant the new price list. Which path does the request take, how long should it take, and what does the board see?

Show the answer

The document assistant is low tier, and new content is a small change. So the request takes the fast path: the owner and the risk lead decide within 2 working days. The board sees it as one line in item 3, for information, not for approval.

Check your understanding

The board rejects a request. Which two fields of the decision record matter most to the person who asked, and why?

Show the answer

The reason, with the evidence used, and what would change the decision. The reason shows that the board read the evidence; for R-06, the release gate passed 0 of 6 checks. “What would change it” tells the person what to do next: bring a version that passes all 6. A rejection without these two fields only says no.

Recap

  • A governance board is a small named group that decides what the fast paths cannot decide, on a fixed rhythm, within a time limit.
  • Its terms of reference say its members, what it decides and does not decide, its rhythm, its time limit, its records and its quorum.
  • Low tier takes the fast path; medium tier is decided by the owner; high tier, vendors and exceptions go to the board. The owner stays accountable after the board decides.
  • Every decision gets a minutes line and a decision record, with its evidence and what would change it.

You can now decide on the changes that people plan. But some events are not planned. A result has already reached a customer, and the customer is not happy. Next, you handle an AI incident and a customer complaint.

Next: Incidents, complaints and redress