Workload Saturation · Primary
Everything is in progress. Nothing is finishing.
How this principle feeds it
overhead fills finite capacity, so more work sits in progress and less finishes.
Principles Library / Cut Non-Value Work
Reducing Non-Value Work Increases Value-Creating Capacity
AI signs are on by default. Use the AI switch to exclude them.
For each consequence: Not seen / Sometimes / Persistently / Not sure.
Based on your answers, recognize at most two conditions: No / Partly / Yes, that is us.
Workload Saturation: Everything is in progress. Nothing is finishing.
Quality Fragility: Customers find defects before the team does.
Local Optimization Bias: Every team hits its targets. The product still misses.
Batch Amplification: Problems are found at release, not before it.
Customer Disconnect: Delivery is consistent. Value is not landing.
What else have you observed? Optional. Shared only if you choose to start coaching.
Start a Diagnosis session: review and edit a draft containing your note, conditions you recognized in Step 3 (including whether they match partly), warning signs and consequence ratings before sending it. No scores or principle files are sent.
Reduce work that consumes time, attention, coordination, or resources without meaningfully contributing to the intended outcome or protecting a necessary system constraint.
Removing non-value work increases the capacity available for activities that create, validate, protect, or enable value.
Time and attention go back to work that creates, checks or protects value.
Higher-value work stops waiting behind lower-value demand.
Leaders can see what matters without digging through piles of activity.
Everything is in progress. Nothing is finishing.
overhead fills finite capacity, so more work sits in progress and less finishes.
Customers find defects before the team does.
rework does grow as a share of output, but here it is wasted capacity from unfixed causes, not defects found late.
Every team hits its targets. The product still misses.
rework that lands downstream is how one team's local gain fragments end-to-end value.
Problems are found at release, not before it.
unvalidated output piles up before feedback arrives, so problems surface in large batches.
Delivery is consistent. Value is not landing.
usage and outcome signals get lost under activity reporting, so delivery continues without knowing if value lands.
Showing all 6 practices. Answer the Diagnose questions and the most relevant come first.
Make waiting, rework, duplicate effort and unused outputs visible across team boundaries.
Start by asking your team: Where does work wait, repeat or get handed off for no good reason?
Work moves more than it waits, nobody builds the same thing twice, and rework is rare.
Remove approvals, handoffs and reporting that rarely influence a decision.
Start by asking your team: Which activities take effort but rarely change outcomes?
Work rarely sits waiting for sign-off, and status reporting shrinks as outcomes improve.
Validate that there's real demand for a feature or output before you commit significant effort to it.
Start by asking your team: Which outputs have little evidence of use, adoption or demand?
What ships gets used, and teams can point to the demand behind it.
Reduce repeated work by fixing its known causes instead of patching the symptoms each time.
Start by asking your team: What rework is predictable and therefore preventable?
The same rework stops coming back, and agent work rarely needs redoing.
Review recurring activities by the value or protection each one provides, and stop the ones that provide neither.
Start by asking your team: What would we stop doing if capacity became genuinely scarce?
Meetings and reports stay lean while outcomes move, and work waits less.
In AI-enabled delivery, measure the useful outcomes from generated output instead of how much gets generated.
Start by asking your team: As AI increases output, which activities eat human attention without creating matching value?
AI output has a clear use and owner, costs track the value delivered, and people spend little time filtering it.