Dependency Density · Primary
The team owns the commitment. Nobody owns the gap.
How this principle feeds it
commitments that depend on capabilities owned elsewhere are the condition's core.
Principles Library / End-to-end capability
End-to-End Capability Reduces Dependency and Improves Flow
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.
Accountability Fragmentation: Accountability is assigned. Control is not.
Quality Fragility: Customers find defects before the team does.
Governance Drag: Work is done. Approvals are not.
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.
Design the unit responsible for delivering value with enough capability, access, and context to complete most of its work without repeatedly depending on external groups.
The more often work must cross organizational boundaries for routine skills, approvals, or execution, the more waiting, coordination, and handoff cost the system creates. End-to-end capability does not mean eliminating specialization or making every team fully self-sufficient. It means reducing structural dependencies that repeatedly interrupt flow and weaken ownership.
Routine work moves without waiting on other groups for skills, approvals or execution.
One team can carry work from intent to outcome and answer for the result.
Shared services and specialists support routine delivery without turning into recurring bottlenecks.
The team owns the commitment. Nobody owns the gap.
commitments that depend on capabilities owned elsewhere are the condition's core.
Accountability is assigned. Control is not.
groups held to outcomes they can't fully influence is the condition.
Customers find defects before the team does.
defects found after they are cheap to fix are the library's definition.
Work is done. Approvals are not.
finished agent output waits at approval groups.
Showing all 7 practices. Answer the Diagnose questions and the most relevant come first.
Organize work around end-to-end value delivery instead of narrow functional boundaries.
Start by asking your team: Can the group responsible for the outcome influence enough of the end-to-end delivery path to keep work flowing?
One group can move work from intent to outcome and answers for the result.
Embed, develop or reliably provide the capabilities a team needs for routine delivery.
Start by asking your team: What capabilities repeatedly create waiting or handoffs?
Routine work, including its testing, no longer waits on another team for a capability.
Make recurring dependencies visible. Then sort out which are structural and which are temporary.
Start by asking your team: Which external dependencies are structural rather than temporary?
Small changes no longer set off long dependency chains.
Reduce handoffs wherever work repeatedly waits for another group to continue it.
Start by asking your team: Where does work routinely leave the team before value can be delivered?
Teams spend little time managing handoffs and most of it delivering value.
Give teams enough context to make decisions without unnecessary coordination.
Start by asking your team: Which decisions leave the team only because it lacks the context to make them?
The team makes routine decisions, including most approvals, without outside coordination.
Design shared services and specialist support so they keep recurring work moving and don't become bottlenecks.
Start by asking your team: Which dependencies genuinely require specialization, and which exist because of how the organization is designed?
Specialists and shared services no longer hold up recurring work.
As AI takes on more execution, make sure teams can understand, configure and influence the automated capabilities that affect their outcomes.
Start by asking your team: As AI increases execution capacity, which dependencies stay the same or become more concentrated?
Teams can configure agents and diagnose their failures without waiting on a central group.