For a delayed project, use the status meeting to settle one management decision rather than collect every task update. Bring the milestone, its unfinished dependencies and the evidence behind the suspected delay. End with an action owner, a baseline and a date to check whether the change helped.
Prepare before the meeting#
Choose one result that is late or at risk. Ask the project owner to update its dependencies, blocked reasons and commitment dates. Invite the people who can explain the work and the sponsor who can authorize the needed tradeoff.
Share the evidence before the meeting. If nobody can name the decision or supply the relevant records, use the session to repair that gap rather than force a diagnosis.
Use this 30-minute agenda#
| Time | Question | Output |
|---|---|---|
| 0-5 minutes | Which commitment is exposed? | Result, date and consequence |
| 5-12 minutes | Where is the required work waiting? | Tasks, owners and readiness |
| 12-20 minutes | Which explanation best fits the evidence? | Working hypothesis and alternatives |
| 20-26 minutes | What will we change? | Action, owner and authority |
| 26-30 minutes | What should move before we meet again? | Baseline, signal and review date |
These are suggested time boxes. A consequential decision with weak evidence may need another session, not a rushed conclusion.
Worked example: protect one customer approval#
In a hypothetical review, a customer milestone depends on a ready technical approval. The same reviewer is receiving unplanned work from two other projects. The group confirms the input is complete and agrees to protect a review slot.
The sponsor owns the priority tradeoff. The project owner checks whether approval finishes and updates the customer milestone. The other project owners receive the revised expectations. The next meeting checks these outcomes rather than repeating the original status discussion.
Write the decision in a reusable format#
Record: “Because these tasks show this waiting pattern, this owner will make this change by this date. We expect this measure to move from the recorded baseline. We will review the result on this date.” Fill it with actual records, not an invented improvement target.
Include the explanation that would make you reconsider. If inputs turn out to be incomplete, the response may need to shift from protecting capacity to repairing readiness.
Use the same records next week#
Commandix’s dashboard, projects and Constraints view provide work context for this review. Record the chosen action and inspect later task movement. A completed action is not enough: check the affected commitment and any new delay.
This internal 30-minute agenda is separate from Commandix’s offered 45-Minute Delay Review, which helps scope one late result and assess whether the available records support a useful investigation.
Related guide: Prepare a one-page executive status report.
Frequently asked questions#
Who should attend?#
The result owner, people who can explain the relevant work and a sponsor authorized to resolve the cross-team tradeoff. Avoid requiring every contributor to attend a decision that does not need them.
What if the team cannot agree on the cause?#
Record the competing explanations and identify the smallest evidence check or reversible test that can distinguish them. Do not turn disagreement into false certainty.