Stage 2 · Lesson 4 of 8
Risks and cross-team dependencies
Keep a short, living list of . For each risk, note what could go wrong, how likely it is and how bad it would be. For each dependency, note an owner and a date.
Review the list weekly with the other teams. A dependency that exists only in your plan is a hope, not a commitment. Get the other team's lead, and ideally their manager, to agree that the work is on their roadmap.
When work slips, adding people rarely helps. says adding people to a late software project makes it later. Newcomers need time to get up to speed, and every extra person adds more conversations to keep in sync.
Common trapdiscovering in the final week that another team never prioritised your request.
A question to check yourself, an AI practice session and 2 cheat sheet entries come with the full roadmap. Unlock
Resources for this stage
Start with· follow one of these
- BookFreeShape Up
Ryan Singer, Basecamp · Intermediate
Free book on shaping and scoping work so projects actually finish
- BookFreeGoogle Site Reliability Engineering Book
Google · Advanced
The chapters on managing incidents and blameless postmortem culture