Course 3
Directing an Outcome with Software
What to hand over, how to describe it, what to check, and where a person still signs.
Machinery can be carried by software. That sentence is only useful once somebody has sorted the work into the part that is machinery and the part that is judgement. This course is about that sorting, about describing work well enough that a system can carry it, about the checks worth setting up, about the places a person must still sign, and about the one failure that makes all of the rest worthless: work that happens and is never looked at.
5 lessons
Lessons in this course
- 3.1 What to hand overMachinery travels well. Judgement does not. Sorting one from the other is the whole skill.
- 3.2 Describing the workTrigger, source, rule, output, exception. A description a stranger could follow.
- 3.3 What to checkSpot checks, thresholds and the checks worth setting up before anything goes wrong.
- 3.4 Where a person must signApproval is not a formality. Deciding where it belongs is a design decision.
- 3.5 The failure modeIt did it and nobody looked. Why silence is the most expensive result of all.