Accountability Through Open Questions: A Team Guide to Asking Better Follow-Through Questions
Most teams do not fail because people are careless. They fail because commitments made in a hallway, a call, or a late-night thread never get a shared home, and by the time anyone notices a promise has gone quiet, the window to recover has closed. Accountability, in the healthy sense, is the habit of making commitments legible: who said they would do what, by when, and what would count as done. This article takes a different angle from tool-first advice. Instead of starting with columns or labels, it starts with the questions a leader can ask in a short recurring review. Those questions work on any workboard, on paper, or in a shared document, and they respect the people doing the work.
Why questions beat status reports
A status report asks people to narrate their effort. A question asks them to state a fact. The difference matters because narration tends to drift toward reassurance, while a well-formed question forces a concrete answer. When a lead asks 'Is this card still owned by the person whose name is on it?' the answer is either yes or no. When a lead asks 'How's the onboarding work going?' the answer is usually 'Good, mostly.'
Questions also distribute responsibility more evenly. In a status meeting, the most articulate person often sets the tone while quieter members stay silent. A short set of standard questions, asked of every commitment in the same order, gives everyone the same opening. People learn that the review is about the work, not about performing confidence, which lowers the temptation to hide slippage.
The five follow-through questions
Start each review by asking about each open commitment in turn. First: what is the commitment, stated in one sentence that a stranger could understand? Vague items like 'improve checkout' cannot be checked, so rewrite them until they name an output, such as 'publish the revised checkout copy for review.' Second: who is the single owner? A commitment with two owners usually has none, so if the answer is 'us,' ask who will make the next move.
Third: what is the next concrete action, and when does it happen? This question separates real progress from a card that has been 'in progress' for a month. Fourth: what, if anything, is this waiting on? Ask the owner to name the person or input they need, and note whether that party has acknowledged the request. Fifth: what would make you change the date? Asking this early gives the owner permission to raise a risk before it becomes a miss.
These five questions take about thirty seconds per item when the card is well-maintained, and longer when it is not. That time cost is itself useful information. If a team cannot answer the first question about a card, the card probably should not exist yet.
Spotting silent commitments
The most dangerous commitments are the ones nobody has questioned recently. A useful habit is to scan for items that have not been discussed, moved, or updated within your normal review window. Those items are not necessarily failing, but they have stopped being visible, and invisible work is where expectations quietly diverge. Two people may each believe the other is handling a task.
When you find a silent item, do not treat it as an accusation. Ask whether the commitment is still wanted, whether the owner still agrees to it, and whether it should be dropped, reassigned, or split. Dropping an item explicitly is a form of accountability too, because it closes a loop that would otherwise sit open and make the board look busier than the team actually is.
A practical checklist for your next review
Before the meeting, confirm that every open item has a one-sentence description, a single named owner, and a date or explicit 'no date yet' marker. Remove or archive anything the team agreed is finished or no longer relevant, so the review covers live work only. Note any item that has not been touched since the last review.
During the meeting, ask the five questions of each live item, in the same order every time. Record answers in the card or document itself rather than in private notes, so the next review starts from shared facts. Where an owner gives a vague answer, ask for the next concrete action and its date before moving on.
After the meeting, send a short summary listing only changed commitments: new owners, moved dates, dropped items, and any requests that are waiting on someone. Keep the summary under a page. Teams that consistently end reviews with a clear list of changes tend to find that the next review is shorter, because fewer questions remain open.
Keeping the habit humane
Accountability systems fail when they feel like scorekeeping. To keep the practice useful, separate the question 'Is this on track?' from the question 'Whose fault is this?' When a commitment slips, the productive response is to learn which of the five questions was unanswerable, whether the scope was too large, or whether a dependency arrived late. Those are process problems that the team can fix together.
Rotate who leads the review occasionally so the questions do not feel like one person's interrogation. Ask owners to name their own risks first, and reserve your own follow-up for items where the owner stays silent. Over time, a team that routinely says 'this will be late, here is why' is healthier and more accountable than one that reports green until the day it does not.