Follow-Through Questions: Testing Whether Team Commitments Are Real
Most teams do not have an accountability problem so much as an evidence problem. People say they will do something, leaders assume it is happening, and nobody notices the gap until a deadline has already passed. The fix is rarely more check-ins or closer observation of individuals. It is a set of specific questions a team can ask about its commitments, answered from the shared record of its work. This article looks at a narrower angle than general accountability advice: how to test whether a commitment is real by asking questions that a board or log can answer, and what to do when the answers are missing.
Start With Commitments That Can Be Tested
A commitment is only testable if it has three things: a named owner, a concrete outcome, and a date. Work that says 'improve onboarding' fails all three tests. Work that says 'Dana drafts the onboarding checklist and posts it to the shared folder by Thursday' passes them. The difference matters because vague commitments cannot be checked, so they drift quietly while everyone believes they are moving.
When a team reviews its commitments, the first pass should be a filter rather than a judgment. For each item, ask whether someone outside the conversation could tell, from the record alone, whether it happened. If the answer is no, rewrite the item until it is answerable. This is not bureaucracy. It is the minimum needed for a team to know what it has agreed to.
Ask the Four Follow-Through Questions
Once commitments are testable, four questions reveal most of the drift. First, is there an owner who has acknowledged the work, or only someone who was assigned it? An assignment that was never confirmed is a common source of silence. Second, has the item moved since it was last discussed? A card that has sat in the same column for two weeks is telling you something, even if nobody is saying it aloud. Third, is the item blocked, and if so, is the blocker named and owned? A block with no owner is a commitment that has already slipped. Fourth, is the date still realistic given what has happened since it was set? Dates made before a scope change or a new interruption often stay on the board long after they stopped being true.
These questions are about the work, not about the person. A card that has not moved is an observation about the card's state and the dependencies around it. Framing the review this way keeps the conversation useful and reduces the instinct to defend individuals.
A Short Checklist for a Weekly Follow-Through Pass
Run this pass once a week, ideally before the team's regular planning conversation, and keep it under twenty minutes. Pull every open commitment with a date falling within the next two weeks. For each, confirm that it has a named owner who has acknowledged it. Note any item that has not changed column or status in the past seven days. List every block and confirm that each one has an owner and a next step. For anything whose date has passed or is clearly unrealistic, decide explicitly: renegotiate the date, reduce the scope, or drop the item. Do not leave it sitting in limbo.
Record the outcome of this pass in a simple log: the date, the items reviewed, and the decisions made. Over several weeks this log becomes the team's own history of how it keeps promises, which is far more useful than any impression of who is working hard.
Compare Commitment Records, Not People
A useful comparison is between two ways a team can run this process. In the first, follow-through is judged by memory: the leader recalls who said they would do what, and asks about it when things look off. This approach depends on who remembers and tends to favor the loudest updates. In the second, follow-through is judged by a shared record: each commitment has an owner, a date, and a status that anyone on the team can read. The second approach is slower to set up but does not require anyone to hold the full picture in their head.
The shared-record approach also changes the tone of accountability. When the question is 'what does the board say about this item,' the conversation is about a fact everyone can see. When the question is 'why didn't you do this,' the conversation becomes personal and defensive. Teams that want accountability without surveillance usually end up choosing the first framing deliberately.
What to Do When the Answers Are Missing
Sometimes the review turns up commitments with no owner, no date, or no record of progress. Treat these as information about the process rather than failures of effort. Ask whether the item was ever really agreed to, whether the owner knows about it, and whether the team has the capacity to hold it at all. Often the right move is to remove the item from the active list, either by closing it or by moving it to a holding area with a clear note, so that the board continues to reflect what the team is actually doing.
Missing answers also point to where the process needs strengthening. If many items lack owners, the team may need a clearer rule about how work gets assigned and acknowledged. If many dates slip, the team may be setting dates without checking capacity. The follow-through questions are not only a way to catch individual items. They are a way to learn how the team's commitments tend to break, so the next round of commitments can be made with that knowledge in hand.