Hook
A faster team can make delivery slower.
Problem
Improving one team, tool, or metric often looks like progress until work hits the next handoff and stalls. When upstream speed increases but downstream capacity does not, you do not get faster delivery. You get bigger queues, more context switching, and more rework.
Why it matters
Delivery is a system. The system throughput is set by its constraints, not by any single team. Local optimization can create global losses by increasing waiting time elsewhere. Flow is what matters: how quickly value moves from idea to safe production.
Signals you are here
- Work is in progress for days, but nothing is actually moving
- One team is celebrated for speed while another is drowning in requests
- Tickets stack up at the same stage (QA, security review, release, approvals)
- Lots of status meetings and chasing to unblock things
- Lead time is high even though everyone is busy
Anti-patterns
- Optimizing for utilization (keep everyone busy)
- Measuring success by tickets closed per team
- Pushing more work into the system to look productive
- Treating downstream teams as blockers instead of designing better flow
Try this
- Map the work end-to-end and measure waiting time
- Limit WIP so queues cannot silently grow
- Improve the constraint first, not the easiest step
- Reduce handoffs with shared ownership (build, test, run together)
- Make bottlenecks visible (queues, time in state, blocked reasons)
Example
A dev team doubles deployment frequency. Great, until QA becomes the queue. Bugs rise, releases slow, and now everyone is context switching between new work and fixes. The team did not fail, the system did. The win was local, but the loss was global.
Reflection prompt
Pick one feature and trace it end-to-end. Where did it wait the longest? Fix that first.
More like this
Heuristic
Avoid Local Optimization
Optimize the system, not the silo.
Heuristic
Limit Work in Progress
WIP is invisible debt on your flow.
Heuristic
Empower Autonomous Teams
Autonomy with guardrails.
Heuristic
Every Output Is Someone Else's Input
Handoff quality sets the pace of flow.
Heuristic
Short Feedback Loops
Fast feedback beats perfect plans.
Heuristic
Work in Small Batches
Small batches make failure cheap and learning fast.