Ineffective Daily Standup: The 3-Question Test

The symptoms of a daily standup that no longer serves any purpose

You know the scene. Nine thirty. Everyone recites what they did yesterday, what they will do today, and reports that they have "nothing blocking." Twelve minutes later, everyone has spoken. No one has learned anything. The next meeting starts in eight minutes.

A daily standup that does not produce coordination looks like this:

• The duration drifts. Announced as 15 minutes, it lasts 25, then 35.
• The same blockers come back several days in a row, without any action being created.
• Two people monopolize the conversation, the others wait for it to end.
• One participant in three checks their messages during the meeting.
• No one could say, at the end, what has changed compared with the day before.

These signals do not prove that the daily standup is useless. They prove that it is not measured. And what is not measured does not improve.

The 3-question test

The principle is simple: for five working days, one person (on rotation) records three numbers at the end of each daily standup. No complicated tool, a spreadsheet is enough.

Question 1: how long did the meeting actually last?

Stopwatch in hand, from the first word to the last. Not the planned duration: the actual duration. Also note the effective start time, because a daily standup that systematically starts at 9:37 for a 9:30 slot hides a calendar problem, not a discipline problem.

Question 2: how many blockers were removed during the meeting?

A blocker removed is an obstacle that found a solution or an owner in the minutes that followed. Not "we'll talk about it again," not "I'll look into it." A decision, a name, a deadline.

Be careful not to confuse a reported blocker with a removed blocker. Most daily standups report three and remove none.

Question 3: how many actions were created, with an owner and a deadline?

An action without a name is an intention. An action without a date is a wish. Count only the actions that have both.

These three numbers, accumulated over five days, give a clear picture. You will know whether your daily standup produces coordination or theater.

How to read the results: the thresholds that decide

There is no universal standard, but you can reason on orders of magnitude consistent with the size of your team.

Actual duration

For a team of 2 to 8 people, a daily standup that regularly exceeds 20 minutes signals a format problem, not a volume problem. Beyond 25 minutes, it is no longer a daily standup: it is a disguised coordination meeting, and it should have its own slot.

Blocker resolution rate

Count the ratio: blockers removed divided by blockers reported over the week. Below 30%, the daily standup serves to declare problems, not to address them. This is the most reliable signal of a theatrical daily standup.

Actions created

Over five days, a team of five people should produce at least three to five concrete actions per week. Zero actions over the week is not a sign of good health: it is a sign that no one dares ask for anything, or that blockers are being kept quiet.

One special case: a week without blockers or actions can be legitimate (team at the end of a sprint, individual work). Do not draw conclusions from an atypical week. Look at the trend over two to three weeks before deciding.

The one-week protocol: measure, decide, change

Here is how to structure the week so that the decision is made, not postponed.

1. Monday: announce the test to the team. Explain that you are measuring the format, not the people. Designate the person who will record the three numbers.
2. Tuesday to Thursday: measure without changing anything. Do not correct the daily standup along the way, otherwise you distort the data.
3. Friday: present the numbers to the team. Fifteen minutes are enough. Let everyone react before proposing a conclusion.
4. Decision: only three options. Stop the daily standup. Reduce it (frequency, duration, participants). Redesign it (asynchronous format, theme-based format).
5. Commitment: set a reassessment date, for example in one month. A format changed without a review date falls back into its old ways within three weeks.

The non-negotiable rule: the decision belongs to the team. A format imposed from above lasts two weeks. A format chosen by those who live it lasts for months.

The asynchronous format for distributed teams

If your team works across several time zones, or if presence hours overlap for only two hours a day, the synchronous daily standup is expensive. An asynchronous format can replace the meeting, provided it is structured.

The principle

Each person posts, before a fixed time, three lines: what has moved forward, what is blocking, what comes next. The channel can be a dedicated thread in a messaging tool, a comment on a board, or a shared document.

What makes the difference

• A clear deadline, respected by everyone, including the manager.
• A person responsible for reading: someone goes through the thread late in the morning and turns blockers into assigned actions.
• A switch rule: if a topic requires more than three written exchanges, it leaves the thread and becomes a short meeting with two or three people.
• A weekly synchronous checkpoint for topics that cannot be handled in writing.

The asynchronous format is not an admission of weakness. It is a response adapted to a real constraint. It has its own pitfalls: blockers can remain unanswered if no one is explicitly responsible for handling them.

What the tooling must enable (and nothing more)

You do not need a sophisticated tool to measure a daily standup. A spreadsheet does the job. However, if you decide to redesign the format, the tool must follow.

Three concrete requirements:

• See blockers without digging. A kanban board with customizable columns and drag-and-drop makes the state of the work readable at a glance. A blocked card must be visible, not buried in a comment.
• Turn a blocker into an action in a few seconds. Checklists, comments, mentions, and an activity log make it possible to trace who took what, and when.
• Measure the trend over several weeks. Burndown or velocity reports, and the cumulative flow diagram, show whether blockers are accumulating or being resolved.

Ever Earlier, for example, brings these elements together in a single space: a kanban board for visualizing, a backlog and sprints for organizing, reports for tracking the trend. The tool does not replace the team decision, it makes it visible.

One point of caution: do not add one more tool if your team already uses three. Coordination gets lost in back-and-forth between applications. Better a single space, even imperfect, than five perfect tools that do not talk to each other.

What to remember

A daily standup that produces neither decision, nor action, nor removed blocker is not an agile ceremony. It is a habit. The good news: one week of measurement is enough to know.

Three numbers, five days, one decision. If the blocker resolution rate remains below 30% and the actions created are close to zero, stop it or redesign it. If the numbers hold, keep the format and reassess in one month.

Continuous improvement does not require a miracle tool. It requires looking the numbers in the face, and accepting to change what is not working.