Principles Library / Cut Non-Value Work

Cut Non-Value Work

Reducing Non-Value Work Increases Value-Creating Capacity

Act

Showing all 6 practices. Answer the Diagnose questions and the most relevant come first.

Show where effort is being lost

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?

Avoid · You’ll know it’s working when

Avoid

  • Treating people or roles as waste instead of looking at what the system does
  • Equating utilization or busyness with value creation

You’ll know it’s working when

Work moves more than it waits, nobody builds the same thing twice, and rework is rare.

Cut approvals and reports that change nothing

Remove approvals, handoffs and reporting that rarely influence a decision.

Start by asking your team: Which activities take effort but rarely change outcomes?

Avoid · You’ll know it’s working when

Avoid

  • Removing controls without understanding the risk they protect

You’ll know it’s working when

Work rarely sits waiting for sign-off, and status reporting shrinks as outcomes improve.

Check demand before committing real effort

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?

Avoid · You’ll know it’s working when

Avoid

    You’ll know it’s working when

    What ships gets used, and teams can point to the demand behind it.

    Fix the known causes of repeat rework

    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?

    Avoid · You’ll know it’s working when

    Avoid

    • Making one team more efficient while adding rework or coordination downstream

    You’ll know it’s working when

    The same rework stops coming back, and agent work rarely needs redoing.

    Keep recurring work only if it earns it

    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?

    Avoid · You’ll know it’s working when

    Avoid

    • Cutting necessary quality, security or governance work because it doesn't create customer-visible value
    • Automating inefficient or unnecessary work

    You’ll know it’s working when

    Meetings and reports stay lean while outcomes move, and work waits less.

    Measure AI by the useful outcomes it creates

    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?

    Avoid · You’ll know it’s working when

    Avoid

    • Producing more AI-generated output just because generation is cheap

    You’ll know it’s working when

    AI output has a clear use and owner, costs track the value delivered, and people spend little time filtering it.

    Overview

    Principle intent

    Reduce work that consumes time, attention, coordination, or resources without meaningfully contributing to the intended outcome or protecting a necessary system constraint.

    Read the full intent

    Removing non-value work increases the capacity available for activities that create, validate, protect, or enable value.

    When it holds: what it does for you

    Capacity goes to value

    Time and attention go back to work that creates, checks or protects value.

    Important work moves sooner

    Higher-value work stops waiting behind lower-value demand.

    Clearer signals for decisions

    Leaders can see what matters without digging through piles of activity.

    When it is ignored: from early signs to a lasting condition

    Early warning signs · Visible now, cheap to fix

    • The same rework keeps coming back and nobody fixes what causes it.
    • Features and outputs ship with little evidence anyone uses or asked for them.
    • Meetings, reports and status updates keep growing while outcomes stay flat.

    What happens over time · Accumulates, costly to reverse

    • Lead times grow as coordination and admin take a bigger share of capacity.
    • Rework takes a growing share of effort, much of it landing on downstream teams.
    • Higher-value work keeps getting pushed back by lower-value demand.

    The condition it becomes

    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.

    Quality Fragility · Secondary

    Customers find defects before the team does.

    How this principle feeds it

    rework does grow as a share of output, but here it is wasted capacity from unfixed causes, not defects found late.

    Local Optimization Bias · Secondary

    Every team hits its targets. The product still misses.

    How this principle feeds it

    rework that lands downstream is how one team's local gain fragments end-to-end value.

    Batch Amplification · Primary

    Problems are found at release, not before it.

    How this principle feeds it

    unvalidated output piles up before feedback arrives, so problems surface in large batches.

    Customer Disconnect · Secondary

    Delivery is consistent. Value is not landing.

    How this principle feeds it

    usage and outcome signals get lost under activity reporting, so delivery continues without knowing if value lands.

    Where is your system on this path?

    Diagnose

    Diagnose

    AI signs are on by default. Use the AI switch to exclude them.

    1. Which of these early warning signs are you seeing?

    • Work spends more time waiting, coordinating or getting approved than moving forward.
    • The same rework keeps coming back and nobody fixes what causes it.
    • Features and outputs ship with little evidence anyone uses or asked for them.
    • Meetings, reports and status updates keep growing while outcomes stay flat.
    • Teams duplicate work because ownership or information is unclear.
    • One team speeds up by skipping steps, and the next team redoes them.
    • AI-generated code, tests and docs pile up with no clear use or owner. (AI)
    • Agent work gets redone or regenerated again and again with little improvement. (AI)
    • Compute, token and review costs rise faster than the value delivered. (AI)
    • People spend more and more attention filtering low-value machine output. (AI)

    2. Over the last few months, have you noticed…

    For each consequence: Not seen / Sometimes / Persistently / Not sure.

    • Lead times grow as coordination and admin take a bigger share of capacity.
    • Rework takes a growing share of effort, much of it landing on downstream teams.
    • Learning has slowed because teams produce far more than they validate.
    • Decisions get worse because useful signals are buried in activity.
    • Higher-value work keeps getting pushed back by lower-value demand.
    • AI output nobody asked for piles up faster than people can sort it. (AI)

    3. The condition it becomes

    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.

    Take your Diagnosis to the next level by invoking AI Diagnostic Coaching tool.

    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.

    See what practices will help you