Workshop · Strategy & planning
Every team posts what it needs from others and what others need from it, pairs agree dates live, and risky dependencies get resolved or escalated.
Free to open and edit. Running it live needs Pro, free for 14 days on every new account.
Dependency mapping shows what each team needs from other teams, and by when, so plans don't break at the hand-offs. This template runs a 60-minute session: every team posts dependencies in both directions from their phones, pairs agree dates live, and at-risk dependencies are dot-voted and resolved, owned, accepted or mitigated.
01Inside
Dependencies with 4 areas, and a 60-minute agenda that runs it.
“Post a dependency: our team, their team, what's needed and by when”
By the end of this meeting, every cross-team dependency is agreed with a date or flagged, and each risky one is resolved, owned or escalated.
02In the room
The shared screen, every phone and the summary afterwards, drawn from this template.
On the shared screen
Ideas land on the board from every phone, with no names on the notes. Then everyone dot-votes what matters most.
On every phone
People scan the code or tap their invite and answer in the phone's browser. No app to install, no account to make.
Afterwards
Decisions and actions are captured as they're said. When the meeting ends, everyone gets the summary, and one link shares it.
03How to run it
Get a representative from every team in the room, or on the call, with the dates in scope.
Each team posts its dependencies in both directions from phones.
Match pairs live and move cards to Agreed or At risk, then dot-vote the riskiest.
ROAM each risky dependency before people leave. In SAFe, it pairs naturally with PI planning day 2, when teams finalize plans and review risks.
04Questions
Still deciding?
Run your next meeting on it. Every new account gets Pro free for 14 days, no card.
Listing and visualizing the work one team needs from another, with dates, so conflicts and risks show up before they delay a plan.
Teams show dependencies on a program board, agree dates with the teams they depend on and treat unresolved ones as risks to discuss in the management review.
A way to handle risks in SAFe: Resolved, Owned, Accepted or Mitigated. Every risk raised in planning should end up in one of the four.
Keep going
Change anything in the editor. When you're ready, press Run live: everyone joins with a scan and answers on their phone.
Free forever · Pro free for 14 days · No card needed · Guests never sign up
Dependency mapping boardRuns with Pro