Reading path
Reading for the person accountable, not for the room: answer on authority, record, testing and stewardship without notice.
One page gives you the parts, the next three are the questions a board asks in the order it asks them, the next three are what happens to the thing over time, and the last four are how ownership actually goes wrong.
11 pages, in order. About 79 minutes in all.
A board occasions two kinds of reading. One is the material you send into the room, a handful of pages a director can read cold on the train and arrive having understood. That is a separate path, and if what you want is something to forward, take it and do not start here.
This is the other kind. You have told a board you are doing this, or you are about to, and from that meeting onward somebody asks you about it roughly every quarter for as long as it runs. Nothing you forward covers that. What covers it is being the person in the room who understands the thing rather than the person relaying a vendor, and that takes eleven pages over more than one evening.
The order follows the shape of accountability rather than the shape of the system. A designer would start at the loop; a board starts at permission. So the reading opens with the parts, because the eleven words used by every later page otherwise read as branding.
The three pages after that are the questions, in the order a board reaches for them. What may it do on its own. Who is it permitted to know and address. What waits for an approval, and what survives afterwards as evidence that it did. Each closes a gap the one before leaves open, and at the end of the three you can say which setting refuses a given thing and whose decision that setting was. The second half of that sentence is what matters in the room: a director is rarely testing the design and is usually testing whether you know who chose.
Then three pages about time, the part no forwarded document covers, because a document is read once and the thing you have bought keeps running. How a department reports a goal gone at risk without being asked. Who may change a specialist’s written instructions, and what stops that being a quiet edit. How a change is examined before it reaches your company, and what the examination cannot see. These turn a quarterly question from an ambush into a status report, and they hold the limits you want to be quoting yourself before a director finds them for you.
The last four are failures, and they sit last because they only make sense once you know what was supposed to happen. Two are short accounts of a control nobody set and a control set without a bound. Two are longer: how these programmes actually die, quietly and with no incident to point at, and the first ninety days, where who looks after it turns out to be three jobs wanting three different people. That page is the answer you will be asked for first and have thought about least.
If you have one evening rather than several, read the parts, the authority setting and the first ninety days. That is about half an hour, and it leaves you able to say what the thing may do unattended, who granted it that, and which of your people are now carrying a piece of it. It does not leave you able to answer on evidence or testing, so do not stop there before a meeting where either will come up.
Cost is not here, and neither is the vendor conversation. A board asks what this will bill, and that answer comes from mechanisms deserving their own sitting; a path on the bill covers them. What you would put to a supplier before any of this becomes yours to own sits in Questions for the Vendor. This path assumes the decision is going ahead and you are the one who will answer for it.
The certification teaches your own people to build and govern what these pages describe.