Commitment Reviews: Checking Whether Promises Survived Contact With the Week
Most teams do not fail because people are lazy. They fail because commitments made in a meeting drift away from the work that actually gets done. A promise to ship a draft on Thursday is said with good intentions, then competes with interruptions, new requests, and unclear ownership. By Friday nobody can say exactly when the promise was broken, only that something slipped. This article focuses on a narrower angle than general accountability: the commitment review, a short recurring check that compares what was promised against what happened, with the goal of learning from the gap rather than assigning blame.
What Counts as a Commitment
A commitment is a statement that someone will do something by a stated point in time. It has three parts: an owner, a deliverable, and a date. If any of these is missing, the statement is closer to a hope than a commitment. 'Someone should look at the pricing page' is not a commitment. 'Dana will review the pricing page copy and reply in the thread by Wednesday noon' is.
Before a team can review commitments, it needs a consistent place to record them. Many teams use a dedicated section of their task board, a running list in a shared document, or a dated entry in their weekly meeting notes. The location matters less than the habit of writing down every promise at the moment it is made, including the ones made in hallways or chat threads. Undocumented commitments cannot be reviewed, and the ones that go missing are usually the ones nobody wrote down.
Running a Short Weekly Review
A commitment review works best as a fifteen to twenty minute block near the end of the week or at the start of the next one. The agenda is simple. Read each commitment logged during the period. For each one, record one of three outcomes: delivered on time, delivered late, or not delivered. Then ask the owner a single question for any late or missed item: what was the first thing that got in the way?
The purpose of that question is diagnostic. Answers tend to cluster. Some commitments slip because the deliverable was vaguely defined, so the owner could not tell when they were done. Others slip because the owner was waiting on someone else, which points toward a dependency problem. Still others slip because the owner took on too much in the same week, which points toward capacity. Each cluster suggests a different fix, and a review that only tallies misses will never reveal which fix applies.
Questions Worth Asking in Every Review
Certain questions produce more useful answers than others. Asking 'Who let you down?' invites defensiveness and gets little information. Asking the following produces a clearer picture:
Was the deliverable specific enough that everyone would agree on whether it was finished? Was the date chosen by the owner, or assigned to them without discussion? Did the owner know the commitment was at risk before the date arrived, and if so, did they say so? Was any part of the work waiting on something outside the owner's control? Did the commitment get quietly reshaped into something smaller without anyone deciding to do that?
The last question is especially valuable. Scope often shrinks silently. A promise to publish a full comparison becomes a promise to publish a draft, and the draft quietly becomes a few bullet points. The review should surface these changes so the team can judge whether the reduced version still serves its purpose.
A Checklist for Keeping Reviews Honest
Use this short checklist to keep the review focused. First, confirm every commitment has an owner, a deliverable, and a date before the review begins, and fix any that do not. Second, mark each item as delivered on time, delivered late, or not delivered, without debate. Third, for each late or missed item, record the first obstacle the owner named. Fourth, group the obstacles into categories such as unclear scope, dependencies, or overload. Fifth, choose one change to try for the coming week, aimed at the most common category. Sixth, note any commitments that were renegotiated mid-week and confirm the new date with the owner.
The discipline matters more than the format. A team that reviews honestly for six weeks will know far more about how it actually works than a team that holds an elaborate quarterly retrospective it never follows up on. Review what was promised, look at what happened, and adjust the process rather than the person. Over time, the gap between commitment and delivery tends to narrow, not because anyone is watched more closely, but because the team understands its own patterns.