Local Optimization
One team improves its own metric while creating or worsening bottlenecks in the wider system.
- Also known as
silo efficiencyteam-level goodhartthe throughput illusionsub-system maximization
- First noticed by
architectdirectorengineering manager
- Mistaken for
- efficiency
- Often mistaken as
- strong team performance
Why it looks healthy
Concrete external tells that make the pattern read as responsible behavior.
- Each team's own metrics move in the right direction
- Team leads can point to clear improvements under their control
- Reviews celebrate per-team efficiency gains
- Retrospectives focus on what each team shipped
Definition
What it is
Blast radius delivery operations team business
A team's performance on its own metrics improves, but the changes harm or ignore system-wide flow and outcomes.
How it unfolds
The arc of the pattern
-
Starts
A team is given a metric and improves it.
-
Feels reasonable because
Teams are meant to own their numbers and improve them.
-
Escalates
Downstream teams absorb the cost invisibly. The handoff gets worse. Queue lengths grow elsewhere.
-
Ends
The system slows while each team reports improvement.
Recognition
Warning signs by stage
Observable signals as the pattern progresses.
EARLY
Early
- Team celebrates throughput while downstream pain rises.
- Metrics are team-level, not end-to-end.
- Handoffs are not tracked.
MID
Mid
- Queue length or wait time grows in adjacent teams.
- Downstream teams describe getting too much, too fast, or in the wrong shape.
- System-level lead time is not improving despite local gains.
LATE
Late
- Incidents arise at team boundaries.
- No one owns the full flow.
- Each team defends its numbers while the product suffers.
Root causes
Why it happens
- Silo incentives
- Poor system-level metrics
- Local autonomy without coordination
- Goodhart's Law applied at team level
Response
What to do
Immediate triage first, then structural fixes.
First move
Trace one real user-value flow end to end, and measure total time through every team boundary - not each team's internal cycle time.
Hard trade-off
Accept that some team metrics will stop improving (or visibly regress) so the system can improve.
Recovery trap
Adding a cross-team metric on top of the existing team metrics, which creates reporting work without changing incentives.
Immediate actions
- Map end-to-end flow from request to user value
- Identify where work queues between teams
- Add a cross-team outcome metric alongside local metrics
Structural fixes
- Align incentives to end-to-end outcomes
- Make handoff quality a first-class metric
- Review system flow in addition to team velocity
What not to do
- Do not remove local metrics entirely
- Do not assume good local numbers mean a healthy system
AI impact
How AI distorts this pattern
Where AI-assisted workflows accelerate, hide, or help with this failure mode.
AI can help with
- AI can reveal system-wide flow bottlenecks if connected to data across team boundaries.
AI can make worse by
- AI can hyper-optimize local workflows and make teams look even more efficient in isolation, deepening fragmentation.
Relationships
Connected patterns
Causal flows inside Failure Modes, and related entries across the site.
Easy to confuse with
Nearby patterns and how this one differs.
-
Metric myopia is measuring the wrong thing. Local optimization is optimizing a local thing well while the system degrades.
-
Feature factory ships without learning. Local optimization ships efficiently while the end-to-end outcome gets worse.
- Adjacent concept Healthy team autonomy
Autonomy lets teams own their work. Local optimization lets teams own their metric while disowning the handoff.
Heard in the wild
What it sounds like
The phrase that signals the pattern is about to start, and who tends to say it.
Our team's velocity is up 20% this quarter.
Said byengineering manager in a planning review
Notes from practice
What experienced people notice
Annotations from engineers who have worked this pattern before.
- Best momentWhen intervention actually changes the trajectory.
- When team metrics are celebrated without checking downstream impact
- Counter moveThe specific action that breaks the pattern.
- Measure the handoff, not just the output.
- False positiveWhen this pattern is actually the correct call.
- Strong team metrics are not the problem. Metrics that ignore system impact are.