Dependency
Last updated:
What is Dependency?
A Dependency is a relationship between two OKRs (or initiatives) where one cannot be achieved without another being completed first or in parallel. In organizational OKR systems, dependencies often cross team lines: Product cannot launch a feature without Engineering building it, Sales cannot expand enterprise deals without Product supporting the use case, etc.
Surfacing dependencies during planning is critical because unmanaged dependencies are a major source of project delay and risk. During OKR planning, teams should explicitly identify: "What other teams' work do we depend on?" and "What teams depend on our work?" These can then be mapped, sequenced, and coordinated.
Healthy OKR systems have visible dependency management: dependencies are mapped before the cycle starts, backup plans exist for high-risk dependencies, and cross-team check-ins happen regularly. A blocked dependency should trigger immediate escalation and problem-solving rather than silent waiting.
Also known as: Dependency, Cross-team dependency, Work dependency
Learn OKRs with interactive lessons
4 short lessons, a quiz, and a free certificate — no account needed.
Put these concepts into practice
Track your objectives and key results with pegore — a minimal, focused OKR tracker.
Comparing tools?
See how pegore compares to Notion, Habitica, and spreadsheets for personal goal tracking.