Dependency Density · Primary
The team owns the commitment. Nobody owns the gap.
How this principle feeds it
work waits on other teams' queues, which is how coordination-bound flow shows up as time.
Principles Library / Handoff Cost
More Handoffs Increase Coordination Cost
Reduce unnecessary transfers of work between people, teams, systems and agents.
Every handoff adds some mix of waiting, context loss, coordination effort, unclear ownership and risk of misreading. As handoffs multiply, these costs compound and end-to-end delivery gets slower and harder to manage. Some handoffs are necessary. The goal is to make those explicit, efficient and well-owned.
Work spends less time waiting between stages, so outcomes arrive sooner.
Intent and context reach the next stage intact, so less work comes back.
Someone owns the outcome and the state at every boundary, including between agents.
The team owns the commitment. Nobody owns the gap.
work waits on other teams' queues, which is how coordination-bound flow shows up as time.
The agents are building. Nobody is sure it still matches the plan.
each agent acts on a distorted input that looks correct, and the drift becomes the next baseline.
Customers find defects before the team does.
misreadings found downstream add rework, but the cause is context lost at handoffs, not weak quality design.
Accountability is assigned. Control is not.
whoever answers for the outcome controls only one stage of the work.
Every team hits its targets. The product still misses.
functions tuning their own transfer speed while end-to-end cost grows is the condition.
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.
Dependency Density: The team owns the commitment. Nobody owns the gap.
Implementation Drift: The agents are building. Nobody is sure it still matches the plan.
Quality Fragility: Customers find defects before the team does.
Accountability Fragmentation: Accountability is assigned. Control is not.
Local Optimization Bias: Every team hits its targets. The product still misses.
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.
Showing all 7 practices. Answer the Diagnose questions and the most relevant come first.
Design teams and workflows so one group owns work from start to usable outcome, where that's practical.
Start by asking your team: How many times does this work change hands before it produces an outcome?
Work reaches a usable outcome through fewer hands, waits shrink and someone clearly owns problems when they surface.
Remove handoffs that exist only because of organizational or functional boundaries.
Start by asking your team: Which organizational boundaries create coordination without adding value?
Work changes hands fewer times, waits between stages get shorter and coordination effort stops outpacing delivery.
For each handoff you keep, spell out who owns it, what state the work should be in and what counts as accepted.
Start by asking your team: Who owns the outcome while work is between teams or systems?
Ownership is clear when problems surface and fewer issues bounce back to earlier stages.
When work crosses a boundary, send its context and intent with it.
Start by asking your team: What context keeps getting lost or rebuilt?
People stop re-explaining context and fewer issues come back for clarification.
When work is highly interdependent, build shared understanding by working together instead of passing it along in sequence.
Coordination effort keeps pace with delivery and people stop re-explaining the same context.
Track how much waiting and rework each handoff point adds.
Start by asking your team: Where does work wait after a transfer?
Waits between stages shrink and fewer issues return upstream for correction.
At each agent boundary, define who owns the state, how context transfers, who handles recovery and how output is validated.
Start by asking your team: Where are agent boundaries adding hidden context or ownership risk as automation grows?
Agents carry intent intact, errors get caught at the boundary and people can trace who changed the state.