Dependency Management

You will never eliminate dependencies between teams. The goal is to make them visible and cheap before they become surprises and blockers.

A dependency exists whenever one team’s ability to deliver value requires something from another team: a capability, a service, a decision, or knowledge. In organizations with multiple business and platform portfolios, dependencies are structural and unavoidable. The goal is not to eliminate them but to make them visible, negotiable, and cheap to manage.

Dependencies come in predictable patterns. Business portfolios depend on each other for shared capabilities. Business portfolios depend on platform teams for infrastructure and services. Platform teams depend on business portfolios to adopt their offerings. And platform teams depend on each other for foundational layers. Each pattern calls for a different interaction mode: collaboration (high-bandwidth joint work for a limited time), X-as-a-Service (stable interface with independent roadmaps), or facilitation (helping a team build capability rather than building it for them). Choosing the wrong mode is where most dependency friction originates.

We find that the biggest lever for reducing dependency pain is surfacing dependencies early and progressively. In a continuous planning cycle, dependencies get identified at T-6 during strategic theme setting, negotiated at T-4 during outcome refinement, and formally reviewed at T-2 before the PI event. By the time teams are in the room together, most dependencies have owners, timelines, and contingency plans. The remaining coordination happens through weekly syncs and mid-PI reviews. Long-term, aligning team boundaries to value streams and investing in platform self-service capabilities reduces the need for synchronous coordination altogether.

Resources

• Continuous Planning Playbook — full dependency management framework with types, interaction patterns, and tracking guidance
• Team Topologies — the team interaction modes (collaboration, X-as-a-Service, facilitation) that shape how dependent teams work together
• Cognitive Load — the constraint that makes dependency management necessary; teams cannot absorb unlimited coordination overhead