Commitment Gaps: Testing Whether Promises Survive a Full Week
Most teams do not lack commitments. They lack a reliable way to learn, midweek, which commitments are still moving and which quietly stopped. A promise made in a Monday planning conversation can be fully intact by Tuesday and forgotten by Thursday, not because anyone is careless, but because nothing in the week forces a second look. This article focuses on a narrow question: how do you test whether a team's stated commitments are still real before the deadline makes the answer for you? The approach below relies on written records, a few standard questions, and a short review rhythm. It does not require monitoring individuals or tracking activity minute by minute. It only asks whether the promised outcome is on course.
Separate the promise from the activity
A commitment and a task are not the same thing. A task is something a person intends to do. A commitment is a statement that a specific outcome will exist by a specific time, and it names an owner who is accountable for that outcome. Teams often record tasks and call them commitments, which makes the record look fuller than it is. A card that says Draft pricing page tells you someone is working on something. A commitment that says Pricing page draft reviewed by Priya on Thursday tells you what finished looks like and when you will know.
Before you can test follow-through, rewrite each important item so it has three parts: the outcome, the owner, and the date the outcome is due. If any of the three is missing, the item cannot be tested later, because there is no clear answer to whether it happened. This rewriting step is often uncomfortable, since vague items feel safer. But vagueness is what allows commitments to drift without anyone noticing.
Ask four follow-through questions
Once commitments are written with outcome, owner, and date, you can test them with a small set of questions. Ask whether the owner has acknowledged the commitment in writing. Ask whether the work has moved since it was assigned. Ask whether any dependency the owner needs has been resolved or is clearly named as blocked. And ask whether the due date is still realistic given what the team now knows.
These questions are about the work, not the person. A missing acknowledgment often means the commitment was assumed rather than agreed to, which is a planning problem. A stalled item often means a hidden dependency, not a lack of effort. A date that no longer fits usually reflects new information that nobody recorded. Treating each answer as a signal about the system, rather than a verdict on someone, keeps the review honest and keeps people willing to report bad news early.
Build a simple commitment ledger
A commitment ledger is a plain list of active promises, kept in the same place your team already works. Each entry records the outcome, the owner, the due date, the date the commitment was made, and its current state: confirmed, in progress, blocked, or at risk. Keep the ledger short. A list of forty items is not a ledger, it is a backlog. Most teams can meaningfully track ten to fifteen active commitments at once, and the ones that matter most are usually visible within that range.
Update the ledger when something changes, not only at review time. When an owner confirms, change the state. When a dependency blocks work, note what is blocked and who is waiting. When a date moves, record the new date and the reason. Over several weeks, the ledger becomes a history of how your promises actually behave, which is far more useful than any single snapshot.
Run a short weekly commitment review
A review only works if it is short and predictable. Thirty minutes once a week is enough for most teams. Go through the ledger from top to bottom, asking the four follow-through questions of each item. Spend most of the time on items marked at risk or blocked, and only briefly confirm the ones that are clearly on track. Close the review by deciding, for each at-risk item, whether to adjust the date, reduce the scope, reassign the owner, or accept the slip explicitly.
The explicit decision is the most important part. A commitment that slips without a decision is the most common failure pattern in busy teams. The review should end with every at-risk item either resolved or consciously accepted, with the reason written down. That record is what makes next week's review meaningful, because you can see which promises were renegotiated and which were quietly dropped.
A practical checklist for your first review
Start with a short checklist you can run before your first review. First, confirm that every active commitment has an outcome, an owner, and a due date. Second, check that each owner has acknowledged the commitment in writing. Third, mark any item with a dependency that is not yet resolved. Fourth, flag any item whose due date falls within the next five working days and whose state is not confirmed. Fifth, for each flagged item, write one sentence describing the decision you need to make.
After the first review, compare what you found against what you expected. Most teams discover that a handful of commitments were carrying most of the risk, and that a few supposedly important items had never been acknowledged at all. Those findings are the real value of the exercise. They show you where your planning process leaks, so you can fix the process rather than chase individual promises through the week. Run the same checklist for four weeks before judging whether the rhythm is working, since the first review usually reveals more about your intake habits than about your team's follow-through.