Draft, open for argument
Measure the flow
Watch queues and waiting time. They point at the constraint.
The rule
Output per engineer says nothing about where work is stuck. A handful of flow signals does: shipped per day, lead time, open pull requests, CI wait, rework rate, idle coding capacity, incident risk. Look at them after every change.
Signs you are breaking it
- Success reported as lines of code or tokens used.
- No one can say how long a change waits at each station.
- Improvements are declared, and never checked a week later.
In Lights Out
Seven signals with sparklines. A tick marks each purchase so you can see what it did.