Directory · T
New here? Start with the premise →
Throughput
2 min read · 437 words
Throughput is the rate at which the system actually completes operations — distinct from intentions, plans, or theoretical capacity.
The hardware has finite processing capacity. The inhabitant who attempts to run more operations simultaneously than the capacity allows produces less actual throughput than the inhabitant who runs operations sequentially. The mind processing several open loops at once allocates fragmented attention to each, with each loop receiving less than it would have received in isolation. The result is more apparent activity and less actual completion.
APPEARANCE VS ACTUAL THROUGHPUT
Most of what looks like high throughput isn’t.
The continuous activity, the long lists, the multiple projects in flight, the appearance of busy-ness — these can all run while actual completion is low. The system reports activity. The inhabitant interprets activity as productivity. The actual completion rate falls below what less activity, more focused, would have produced.
LIMIT WORK IN PROGRESS
The functional configuration is counterintuitive: holding fewer operations active produces more throughput, not less.
The inhabitant who keeps two or three operations active at once, completing them before opening new ones, produces more throughput than the inhabitant who keeps ten or fifteen active. Each active operation consumes some background capacity continuously, even when not being worked. Limiting the active count returns capacity to whatever is currently being worked. The mechanism is real even when the feeling is that more open loops mean more output.
THE DIAGNOSTIC
How many operations are currently in flight, and what is the actual completion rate per week?
The honest count often surfaces that many more operations are in flight than the inhabitant had registered, and that the completion rate is lower than the activity level suggested. The gap between the two is the cost of the configuration.
DESIGNING FOR FOCUS
The continuous-interruption environment most inhabitants run in is hostile to throughput.
Protected blocks of uninterrupted time produce dramatically higher completion rates per minute than the equivalent time fragmented across many short blocks. The arrangement matters more than the hours. The inhabitant who finds three uninterrupted hours per day often completes more than the inhabitant working ten interrupted ones.
ACTIVITY AS PERFORMANCE
Some configurations of activity exist to be seen — by other people, by the inhabitant themselves through the appearance of productive busy-ness.
These produce the appearance but not the substance. The honest internal accounting of what was actually completed reveals which configurations are running. The activity that has no completion attached to it, repeated daily, is performance, regardless of how tiring it is.
Throughput is what gets finished. The activity is incidental to the finishing.