Dependencies won’t kill your Department’s Roadmap — ignoring them will.
Here’s how I manage them at scale:
1/ Surface Early, Prioritize Hard
- Run a pre-mortem to surface hidden blockers
- Catalog who, what & when — don’t assume DRIs + risks
- Rank ruthlessly — delivery plan by business impact and visibility
2/ Engage Before It’s a Blocker
- Embed, pair, and co-design — not just coordinate
- Don’t wait for dependencies to fail — pre-align early
- Engineer-to-engineer syncs beat passive doc handoffs
3/ Milestone Like a Pro
- Ship a flaggable v0 early
- Start with a vertical slice prototype
- Tie each milestone to user value, not just phases
4/ Escalate Before It Stalls
- No movement in 2 weeks? Raise it
- Don’t wait for “we’re behind” updates
- Create issue docs with impact, scenarios, and asks
5/ Make It Visible
- Track: owner, status, ETA, risk
- Use checklists + scorecards weekly
- Keep dependencies as real as features
Dependencies aren’t bad — mismanaging them is.
Strong leadership organizes and unblocks progress before it’s too late.