Principles Library / Optimize the Whole

Optimize the Whole

Optimizing the System as a Whole Improves and Sustains System Outcomes

Act

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

Measure how the whole system performs

Define and measure outcomes that reflect the performance of the overall system.

Start by asking your team: Which metrics tell us how individual components are performing, and which tell us whether the system is improving?

Avoid · You’ll know it’s working when

Avoid

  • Treating local productivity as evidence of overall performance
  • Treating utilization as evidence of overall performance

You’ll know it’s working when

Team targets and overall outcomes move up and down together.

Judge local improvements by their system impact

Evaluate each local improvement by what it does for broader system outcomes before you invest further in it.

Start by asking your team: Which step limits the whole system right now, and does this improvement touch it?

Avoid · You’ll know it’s working when

Avoid

  • Assuming that improving every component will automatically improve the system

You’ll know it’s working when

Local productivity gains show up in system performance.

Tie incentives to system-level objectives

Align team, functional and leadership incentives with system-level objectives.

Start by asking your team: Where are incentives encouraging teams to protect local performance at the expense of shared outcomes?

Avoid · You’ll know it’s working when

Avoid

    You’ll know it’s working when

    Decisions get made on shared outcomes more than functional KPIs.

    Make dependencies, queues and downstream effects visible

    Make dependencies, constraints, queues and downstream effects visible to the people making improvement decisions.

    Start by asking your team: What local improvements have created unintended consequences elsewhere?

    Avoid · You’ll know it’s working when

    Avoid

    • Optimizing individual teams without examining downstream effects

    You’ll know it’s working when

    A fix in one area no longer piles delays or rework onto another.

    Check whether fixes remove problems or move them

    Regularly examine whether improvements are removing problems or simply shifting them elsewhere.

    Start by asking your team: When a constraint is removed, where does the next limiting condition emerge?

    Avoid · You’ll know it’s working when

    Avoid

    • Solving constraints in isolation without considering where they may reappear

    You’ll know it’s working when

    When a constraint is fixed, the team already knows where the next one will appear.

    Give agents system-level goals and feedback

    Have agents and automation optimize within system-level goals, constraints and feedback instead of isolated performance targets.

    Start by asking your team: As AI increases the speed or volume of work in one area, what happens to the rest of the system?

    Avoid · You’ll know it’s working when

    Avoid

    • Applying automation to accelerate individual steps without understanding system consequences
    • Allowing agents to optimize narrow objectives without system-level goals and feedback

    You’ll know it’s working when

    Agents in a workflow pull toward the same outcome, and someone can see how their decisions interact.

    Overview

    Principle intent

    Optimize decisions, improvements and resources based on their effect on the overall system rather than the performance of individual teams, functions, processes or components.

    Read the full intent

    Improvements in one part of a system don't necessarily improve the whole. They can create delays, excess work, dependencies, rework or other unintended consequences elsewhere. Sustainable performance comes from understanding how the parts interact and judging local improvements against broader outcomes such as value, quality, reliability, responsiveness and flow.

    When it holds: what it does for you

    Gains that count

    Local improvements show up as better results for the whole system.

    Honest progress signals

    Leaders judge progress by system outcomes instead of component metrics.

    Bottlenecks stop moving

    A fix in one place stops pushing delays and rework onto another team.

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

    Early warning signs · Visible now, cheap to fix

    • Teams hit their own targets while overall outcomes stay weak.
    • A fix in one team's area creates delays, queues or rework in another's.
    • Local productivity goes up, but system performance doesn't move.

    What happens over time · Accumulates, costly to reverse

    • The constraint keeps moving as each team's local fix creates a new bottleneck.
    • Teams protect their own numbers and resist changes that help the whole.
    • Component metrics tell leadership things are improving when they aren't.

    The condition it becomes

    Local Optimization Bias · Primary

    Every team hits its targets. The product still misses.

    How this principle feeds it

    each fix is judged on its own step, which is the condition's core pattern.

    Workload Saturation · Secondary

    Everything is in progress. Nothing is finishing.

    How this principle feeds it

    work piles up in front of each new bottleneck, so more is in progress and less finishes.

    Dependency Density · Primary

    The team owns the commitment. Nobody owns the gap.

    How this principle feeds it

    work that can only move with constant cross-team coordination is how the condition is defined.

    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?

    • Teams hit their own targets while overall outcomes stay weak.
    • A fix in one team's area creates delays, queues or rework in another's.
    • Local productivity goes up, but system performance doesn't move.
    • Decisions get made on functional KPIs more than shared outcomes.
    • Agents speed up single steps toward their own targets while overall results stall. (AI)
    • One agent's extra output creates queues, rework or resource pressure downstream. (AI)
    • Agents in the same workflow chase conflicting objectives. (AI)
    • Nobody can see how agent decisions interact beyond task completion counts. (AI)

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

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

    • The constraint keeps moving as each team's local fix creates a new bottleneck.
    • Teams protect their own numbers and resist changes that help the whole.
    • Dependencies and coordination effort between teams keep growing.
    • Improvement effort goes to steps that don't limit the system.
    • Component metrics tell leadership things are improving when they aren't.
    • Narrow agent optimizations spread fast and compound across connected workflows. (AI)

    3. The condition it becomes

    Based on your answers, recognize at most two conditions: No / Partly / Yes, that is us.

    Local Optimization Bias: Every team hits its targets. The product still misses.

    Workload Saturation: Everything is in progress. Nothing is finishing.

    Dependency Density: The team owns the commitment. Nobody owns the gap.

    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