Process
- Company / team
- Job observed
- Person shadowed
- Date / duration
Step log
Write every step in the order it actually happens. If nobody can say why a step exists, mark it as a suspected workaround.
| # | Step | Who / what / system | Frequency | Why this way? |
|---|---|---|---|---|
| 01 | ||||
| 02 | ||||
| 03 | ||||
| 04 | ||||
| 05 | ||||
| 06 | ||||
| 07 | ||||
| 08 |
Triage
Filters in order: fixed rule → software. Messy judgment → AI. High cost of error or rare business call → human. Cost of error can override a capable model.
| Step | Software | AI | Human | Why |
|---|---|---|---|---|
| 01 | ||||
| 02 | ||||
| 03 | ||||
| 04 | ||||
| 05 | ||||
| 06 | ||||
| 07 | ||||
| 08 |
Trust checklist
- Visible intermediate steps remain (the process still looks like the one people know).
- Rollback path is named.
- Pilot length is longer than the build (weeks of use, not a demo afternoon).
- Unsure cases go to a person instead of a confident wrong answer.
- Known-answer examples exist before anything touches live work.
Value
Pick one. Nothing else counts.
- Revenue in
- Cost out
- Risk reduced
- The number
Print this page and fill it by hand. If you cannot sit next to the work this week, theSafe Refund Agent exercise is a simulated desk for the same audit. Private preview.