Organization under AI
DE EN

Cheap to Make, Costly to Check · Volume One

Tools

Eleven tools, twenty-six handholds, and where each one is built. The worksheets are in Part Five of the book.

The eleven tools

ToolBuilt in
The inventory — what is actually runningChapter 2
The three failure modesChapter 2
The five triggers — does this need a rule at allChapter 8
The four zones — how strictly handledChapter 8
The constitutional-rank testChapter 9
The pattern reviewChapter 9
The duty to challengeChapter 9
The pace ruleChapter 11
The coupling pointsChapter 11
Configuration powerChapter 13
Unassisted practiceChapter 14

Twenty-six things to do

A handhold produces a finding. A commitment sets something that stands afterward. None of them is a project.

Ch.FormWhat to doTime
1HandholdOne pair of numbers: items per week at a checkpoint against minutes for a serious checktwo hours
2HandholdThe list of your systems, sorted into three layers — count before you explainan afternoon
3HandholdThe same pair of numbers on your longest-running AI usefifteen minutes
4HandholdThree things that were true about your last significant decision and appear in no filetwenty minutes
5HandholdMark where a standard tone would be noticedhalf an hour
5HandholdWhat work did you learn to judge on — and who gets that practice now?ten minutes
6HandholdTwo phone calls: who stands behind the last thing you relied on, and for what exactlyfifteen minutes
7HandholdWrite down who signed the maintenance agreement and who installed the last updatefifteen minutes
7HandholdRun the last AI decision through all five perspectives
7HandholdApprovals issued last week against those where you saw the material yourselften minutes
8CommitmentApply the five triggers before every new use and every new rule
9HandholdThe pattern review: who was invited, who was not, what separates the groupshalf an hour, quarterly
11HandholdAssign each process one of the four paces, with a date and a namea morning
11HandholdMeasure one coupling point instead of estimating — three numberstwo hours
12HandholdThe load check: four questions, with the people affectedhalf a day
12HandholdNot only what a tool saves — what happens to the time it saved
13HandholdWrite a name behind every pre-sorting systemone hour
13CommitmentFix your own position before looking at the system; log dissenting viewsten minutes
14CommitmentSet a recurring date on the calendar at which work happens without the system
14HandholdMark ten decisions where your information advantage actually decided
15HandholdWrite the actual pace next to each zone
15HandholdCount the empty fields where no name stands for the configurationtwenty minutes
16HandholdHold a reviewed decision against the five conditions and cross off whatever fails
16HandholdWrite the question you would ask a colleague — then look for who can answer ittwenty minutes
16CommitmentWrite the one sentence on update review, and ask for two numbers
16HandholdLook for a review hours figure in your last business case

Where no time is given, the chapter gives none — usually because it depends on the size of the organization.