A commitment was missed. The team knows it. The question is what happens next. In many teams, either nothing happens, because raising it feels awkward, or the conversation turns to who is at fault. Neither response helps the next commitment hold.
A short, structured review can change that. It aims to understand what happened in the system, restore a workable plan, and make accountability a normal part of how the team works. The format below takes about twenty minutes and applies to commitments that affected other people.
Principles before the format
- Accountability and blame are different. Accountability asks the owner to explain and act. Blame asks who deserves criticism. The first makes teams better at keeping promises. The second teaches people to hide problems.
- Look at conditions as well as choices. A missed commitment often involves unclear scope, a dependency that moved, or a priority conflict. Those are system issues worth fixing.
- Keep the owner at the center. The person who made the commitment explains first. Others add information afterward.
The five questions
- What did we commit to, and what happened? (3 minutes) The owner states the commitment as it was made and the actual result. Stick to observable facts: the date, the deliverable, and what was delivered.
- What was the impact? (3 minutes) Who was waiting, and what did the delay or gap cost them? Hearing this from the affected person makes the commitment real in a way a status field cannot.
- What got in the way? (5 minutes) Discuss conditions: Was the scope clear? Did a dependency shift? Did a higher priority displace this work? Did the owner know early that the date was at risk, and what stopped them from saying so?
- What is the recovery plan? (5 minutes) A new date, a revised scope, or a decision to drop the item. The owner proposes, affected parties respond, and the group agrees on one version.
- What do we change? (4 minutes) Choose one practice adjustment, such as an earlier at-risk flag, a clearer definition of done, or a dependency check at the start. Assign an owner for the change.
The question under question three
The most useful part is often the early-warning question. If the owner knew two weeks ahead that the date was at risk and said nothing, ask what made silence feel safer than speaking. The answer may point to how previous misses were handled. If bad news met criticism, people learned to wait until the last moment. A leader who hears this should take it seriously and change the response.
An illustrative example
This scenario is hypothetical.
A team commits to delivering a customer training plan by the end of the month. The plan arrives two weeks late, and the customer-facing team had to postpone sessions. In the review, the owner explains that the scope doubled after a late request and that it was unclear who could approve a reduction. The recovery plan is a smaller first version and a new date. The practice change is that any scope increase on a commitment requires the owner and requester to agree on date or scope before the work continues.
What leaders should model
Leaders set the tone through the first response to bad news. A calm question like "What do you need to get this back on track?" encourages early reporting. If a leader owns misses of their own using the same format, the team sees it as a shared practice and not a punishment.
When a pattern emerges
One miss is an event. Three misses from the same person or on the same type of work form a pattern, which calls for a different conversation about role fit, workload, or capability. That should be handled privately and directly, outside the team review. For leaders preparing that kind of conversation, one-on-one leadership coaching offers a private place to plan it.