Why a dependency standup is not a status meeting

A status meeting asks everyone to describe what they did last week. A dependency standup asks a narrower question: which piece of work is waiting on another team, and who will move it today. That difference matters because status updates can fill an hour without changing a single date. A dependency standup ends with named people taking named actions before the next check.

The operations coordinator runs the format, not the work. The coordinator keeps the list current, invites the people who own the waiting items, and writes down what each owner promises. The meeting lasts fifteen minutes because the scope is deliberately small. Anything that needs a longer discussion moves to a separate call with the two or three people involved.

Invite owners, not delegates

Keep the attendee list to people who can commit their team's time. A project manager who must check with a delivery lead cannot resolve a dependency in the room. A named owner who can say yes, no, or a specific date can. If an owner cannot attend, ask them to send a decision in writing before the meeting rather than a colleague who will relay it later.

Six to eight attendees is a workable ceiling for a fifteen-minute call. Above that, the coordinator should split the session by workstream or move the discussion to the register. Attendance should follow the dependency list, so the invite changes as items open and close. A fixed attendee list slowly turns the standup back into a general status meeting.

Show the register, not a slide deck

Put the live dependency register on screen and read from it. The register already holds the item, the owning team, the waiting team, the promised date, and the last update. A slide deck duplicates that data and goes stale the moment the call ends. The shared screen also lets every attendee see the same version of the truth.

Sort the register by promised date and show only open items. Closed items belong in the archive, where they can be reviewed later without slowing the meeting. Highlight anything whose promised date has passed and anything with no named contact. Those two flags usually produce the most useful conversation in the fifteen minutes available.

Three questions per open item

Each owner answers the same three questions for every item they own. What is the current promised date? What changed since the last check? What will you do before the next check? The answers go straight into the register while the person is speaking, so nobody has to reconstruct them from memory afterward.

The format keeps answers short because each question has a bounded answer. A date, a change, and a next action fit in a few sentences. It also exposes the difference between activity and progress. "We are still working on it" is not an answer to the third question, and the coordinator can ask for a concrete step before moving on.

Handle blockers that need another owner

Some items cannot move because the blocker sits in a different team. When that happens, do not let the current owner carry the item indefinitely. Name the team that holds the blocker, name a person in that team, and ask that person for a date. If the person is not on the call, the coordinator records the request and follows up within one business day.

Escalate only when a promised date has been missed twice or when the delay threatens a dated commitment. Escalation is a specific act: a short message to the two managers naming the item, the impact, and the decision needed. A standup that escalates every week trains people to treat the meeting as a threat. Escalation should be rare enough that it still means something.

Protect the fifteen minutes

Start on time even when key people are missing. Waiting rewards lateness and punishes the people who showed up. If an owner is absent, read their item from the register, mark it as unconfirmed, and move on. The coordinator can collect the missing answer afterward without holding the group hostage.

End at fifteen minutes regardless of how many items remain. Unfinished items carry to the next session with a note explaining why. That constraint forces the group to spend time on the items that can actually move. It also protects the rest of everyone's calendar, which is the reason people keep showing up.

Close with one written summary

Before the call ends, the coordinator reads back the changes: dates that moved, owners that changed, and actions due before the next check. One summary in one place is enough. A summary in the meeting chat, another in email, and a third in a private note creates three versions that will disagree by Friday. Read the list aloud while people can still correct it, then publish the corrected version once.

Send the summary within an hour and link to the register rather than pasting the whole table. Each owner should be able to see their own commitments without opening a long document. The weekly blocked-work review then uses the same register to decide which items need a deeper conversation. Two short rituals on one data source beat five meetings on five spreadsheets.

Sources