The Dirty Laundry Meeting

A dependency can be at risk while every team involved reports that its own work is on track. One lead assumes a decision is settled. Another is waiting for a conversation that has never been scheduled. Everyone is busy, but the gap between them has no owner.

Adding another status meeting does very little for that problem. The team needs somewhere to make the gap visible and decide what to do about it.

One mechanism I have found consistently valuable is a weekly blocker review. I call it the Dirty Laundry Meeting. It is built around one question:

What could prevent us from succeeding next week?

The name is memorable, but the operating discipline matters more. Concerns must be safe to raise. Previous commitments must be reviewed. Every issue that needs action must leave with an owner, a next step, and a follow-up date.

Without those conditions, the meeting becomes another place where people describe problems they will describe again next week.

Start with last week

Begin by reviewing the previous meeting's actions. New problems are usually more interesting than old commitments, which is exactly why the order matters.

For each open action, establish what happened. If it is complete, check whether the blocker actually moved. Sending a message may complete a task without resolving the dependency that prompted it. If the action is incomplete, ask what prevented progress and what should change now.

An unchanged follow-up date should be a conscious decision. Quietly moving dates teaches everyone that the log is a record of intentions rather than commitments.

This review should be direct without becoming prosecutorial. An owner may have discovered that the original action was wrong, that another decision is required, or that the work exceeds their authority. Those are useful findings. The response should make it easier to surface them early.

Record the revised action and the help required. If the same item keeps returning, investigate the underlying obstacle. Repeating “please follow up” is unlikely to solve an unresolved priority conflict.

Make the name safe to live with

“Dirty laundry” must never become an invitation to embarrass people.

The meeting is for exposing delivery obstacles, uncertainty, and dependencies. Individual performance concerns, sensitive personal circumstances, and interpersonal complaints belong in an appropriate private conversation. The shared review may need to know that capacity has changed; it usually does not need to know why someone is unavailable.

The facilitator has to protect that boundary in real time. If someone says, “We are blocked because they never deliver,” ask for the observable situation: What was expected? What has arrived? What is now at risk? What decision or help is needed?

That change in language makes the issue actionable without deciding, in public, who is at fault.

Psychological safety also depends on what happens after someone raises a concern. Thanking them in the meeting and criticizing them later for making the team look bad will undermine the whole mechanism. Respond to early uncertainty with curiosity and useful follow-through.

Accountability still matters. People should explain missed commitments and agree on recovery. When a pattern requires a performance conversation, handle it through the proper management process rather than turning the blocker review into that conversation.

Use an agenda that produces movement

The following is a suggested 35-minute format. Adjust it to the number of teams and the decisions they need to make.

Before the meeting: Ask leads to add concerns to a shared list. A useful entry states the risk, its likely impact, the date it becomes consequential, and the help needed. Reading the list beforehand gives quieter participants a route into the discussion and lets the facilitator spot connected issues.

Minutes 0–8: Review previous actions. Close completed items, test whether their underlying blockers are resolved, and revise anything that is stuck. Address overdue decisions before opening a fresh list.

Minutes 8–23: Surface next week's obstacles. Invite each lead to answer the central question. Focus on dependencies, uncertain decisions, capacity, technical assumptions, and changes in priorities. A concern does not need to be a confirmed failure to deserve attention.

Minutes 23–30: Agree actions and escalations. Decide what the group can resolve now, what needs a smaller working session, and what requires somebody with different authority. Keep long technical investigations out of this meeting while giving each one a concrete next step.

Minutes 30–35: Read back commitments. Confirm the owner, next action, and follow-up date for every new item. Check that each owner understands and accepts the action. Identify who else needs an early update.

Do not fill the time simply because it is reserved. If the actions are clear and no further discussion will change them, finish. If the list consistently cannot fit, examine its scope before making the meeting longer.

Keep the action log small and specific

The log needs enough detail to support follow-through, without becoming a second project plan. This fictional example shows the level of specificity I recommend:

These are illustrative roles and situations, not a record of an actual team.

Notice that the owner is the person responsible for moving the issue forward. They do not have to perform every task or hold every decision right. They do need to know where the next conversation goes and when to return with an update.

“Discuss offline” is not an adequate next step. Name the discussion's purpose, the people whose input is required, and the decision it should enable. Otherwise, the meeting has only relocated the ambiguity.

Facilitate disagreement before it becomes blame

Some blockers are disagreements in disguise. One team needs stability; another needs an interface change. Both positions may be reasonable within their own constraints.

Give each side enough time to describe its constraint and the consequence of the competing choice. Then identify the shared outcome and the person authorized to decide. A facilitator should not manufacture consensus when the real issue is a trade-off that somebody must own.

Separate facts from assumptions. “The change will delay testing” should lead to a concrete question: Which tests, by how much, and based on what dependency? If nobody knows yet, the next action may be a short investigation rather than a decision.

Watch who is not contributing. Silence might mean agreement, but it can also mean uncertainty or reluctance to challenge a senior person. Offer a written route to raise a concern, and follow up privately when someone's participation changes. Do not force a public explanation for their silence.

The leader should also make their own constraints visible. If an unresolved leadership decision is blocking the team, it belongs in the same action log. Accountability becomes more credible when it applies upward as well as outward.

Escalate while there are still options

The weekly review is a predictable checkpoint. It cannot be the only route for raising an urgent problem.

Agree which conditions require immediate attention: active service disruption, a material security concern, an irreversible commitment, or a deadline that will pass before the next review. Use the team's established incident or escalation process for those situations.

For other escalations, make the request specific. Explain what is happening, what remains uncertain, the likely impact, what has already been tried, and the decision or support required. Include the latest useful decision time. This gives the recipient something they can act on.

Tell affected people early rather than letting the escalation become their first encounter with the issue. Early communication preserves room to change the plan. A surprise at the point of decision makes even a manageable problem harder to handle.

Judge the meeting by what changes afterward

A full action log does not prove that the mechanism works. Look for evidence that people get help earlier, dependencies gain clear owners, and decisions stop returning unchanged.

Ask the team whether the review has made difficult concerns easier to raise. Check whether completed actions remove obstacles or merely generate more activity. If a recurring item belongs in an existing decision forum, route it there and keep only the necessary follow-up.

The most useful test is simple: What would stop working if this meeting disappeared?

If the answer is only that leadership would receive fewer updates, redesign it. A good Dirty Laundry Meeting gives the team a reliable way to surface what could go wrong, get the right help, and return next week knowing what happened.

That reliability is what makes uncomfortable conversations worth having.