The Short Daily Coordination Meeting: When It Helps and When It Doesn't

Why the daily round relieves some teams and annoys others

Hardly any method from the agile world has spread as widely as the daily stand-up. Every morning the team gets together for a few minutes, everyone says what they are working on and what is holding them up, and then they get to work. In many companies this has become a fixed habit, even far away from software development. Just as widespread is the frustration with it: the round lasts longer than planned, everyone reports, nobody listens, and problems are raised but not solved.

This leads to the guiding question of this article: when does a short daily coordination meeting help a small team, and when is it wasted time? To answer it, we first clarify the terms, then present a thinking model on the interdependence of work, look at the findings, weigh two perspectives, and finally describe a decision rule and a 15-minute round.

A daily round is only as useful as the dependencies it makes visible.

What is a stand-up meeting?

The daily coordination meeting, called a daily stand-up or simply daily, is a short, daily meeting of a team at the same time. It became known as the daily scrum in agile software development, where the Scrum Guide limits it to a maximum of 15 minutes. The name stand-up comes from participants standing so that the round stays short. Traditionally, everyone answers three questions: what have I done since yesterday? What am I planning until tomorrow? What is holding me up?

The distinction from the article on fewer meetings, better decisions helps place it. Meetings have three purposes: informing, coordinating, deciding. The stand-up belongs to coordinating. It is not a place for status reports that can also be passed on in writing, and not a place for decisions that need preparation. Problems are named there; they are solved afterwards by those affected.

The thinking model: Thompson's three types of interdependence

The organizational researcher James D. Thompson (1967) distinguished three ways in which work in a group can depend on each other. His model explains why the same round is indispensable in one team and superfluous in another. With pooled interdependence, everyone works on their own and contributes to a common result, such as several field sales reps with their own territories. With sequential interdependence, one step needs the result of the previous one, such as site measurement, costing, production. With reciprocal interdependence, contributions constantly mesh, such as an installation on a construction site where electricians, fitters, and site management react to one another every day.

Thompson showed that each type needs a different form of coordination. Pooled interdependence can manage with rules and common standards. Sequential interdependence needs planning, so that everyone knows when it is their turn. Reciprocal interdependence needs ongoing mutual adjustment. The daily round is one form of this mutual adjustment.

An analogy from sport makes the difference tangible. A track and field team of sprinters, jumpers, and throwers rarely confers during the competition, because each competes on their own. A soccer team, by contrast, constantly shouts instructions to one another during the game, because every move depends on the others. Nobody would accuse the track athletes of talking to each other too little.

What studies show about daily coordination rounds

The most thorough study comes from Stray, Sjøberg, and Dybå (2016). They followed twelve software teams in three companies with sites in Malaysia, Norway, Poland, and the United Kingdom, conducted 60 interviews, and observed 79 daily rounds. Two things were rated most positively: sharing information within the team and the opportunity to discuss and solve problems. Rated most negatively were reporting to the manager, too high a frequency, and too long a duration.

Singh and Strobel (2023) interviewed 19 developers from the United States and India in depth about their experiences. Those who worked on their own module and hardly depended on others experienced the round as superfluous and a waste of time. The content rarely concerned their own work, and by their own account, obstacles could be better resolved directly with the responsible person. Many reported that they only listened to topics that concerned them. Experienced and junior developers also experienced the round differently: junior developers listened more attentively but sometimes felt intimidated and preferred to stay silent. Many found the participation of managers of little help.

On form, an older experiment provides a clear finding. Bluedorn, Turban, and Love (1999) had 56 groups of five people discuss a task standing and 55 groups sitting. The seated meetings lasted 34 percent longer, but the decisions were no better. Differences also appeared in satisfaction with the meeting and in the use of the available information.

A more recent finding completes the picture. Benlian, Pinski, and Adam (2025) surveyed 149 agile developers daily over several weeks, 1,510 times in total. What mattered for their well-being was not how many agile practices such as daily rounds the team used, but whether this matched their own needs. Too much was just as stressful as too little.

Coordination or ritual? Two perspectives

There are two readings of the daily round. The first sees it as a coordination tool: problems become visible early, nobody waits a whole day for information, and the team knows what the others are doing. The positive findings of Stray and colleagues speak for this, where the round shared information and solved problems.

The second sees it as a ritual: a mandatory meeting that mainly gives management an overview, costs attention, and interrupts work. The findings of Singh and Strobel among independently working developers speak for this, as do the negative assessments of status reports to managers.

I consider both readings correct, and Thompson's model explains when each applies. With reciprocal interdependence, the daily round is an effective tool. With pooled interdependence, it becomes a ritual, however well it is run. Most small teams have phases of both. It follows that the round should not be introduced permanently, but for the period in which the work meshes closely.

Decision rule and a 15-minute procedure

Whether a daily round makes sense can be clarified with a simple test. For one week, count how often someone in the team waited for a colleague's information, approval, or result. If there are several cases a day, the round is worthwhile. If there are few a week, weekly team planning and direct agreements are enough. How limiting parallel work makes bottlenecks visible is described in the article on Kanban in sales.

1. Fixed time and fixed place

   Every day at the same time, at the board or where the work happens. Whoever is absent is not informed afterwards but reads the agreements on the board.

2. At most 15 minutes, standing

   With five to eight people, ten minutes are usually enough. The time runs visibly.

3. Three questions, addressed to the team

   What is finished since yesterday that others need? What am I planning today? Where can I not move forward without help? People speak to the team, not to the manager.

4. Name problems, do not solve them

   Whoever names an obstacle gets a slot right after the round with those affected. The others go to work.

5. Review after four weeks

   Ask the team: has the round shortened waiting times? If not, it becomes less frequent or is abolished.

• The round regularly lasts longer than 15 minutes.
• Participants look at the manager, not at each other.
• Problems are discussed in the round instead of being solved afterwards.
• More than half of the contributions concern nobody but the speaker.
• Nobody could say what the round prevented or sped up last week.

If two or more of these warning signs apply, the round has become a ritual. For teams that work in different locations, the article on leading from a distance describes a form that also works as a short voice message in the morning: ten minutes daily to align on the most important tasks and obstacles.

The bigger picture

The daily round is a good example of a method that is confused with its origin. In software development, teams often work in close coordination on a shared product, and there it fits. In a company where everyone looks after their own customers, it does not automatically fit. How to choose methods by the type of work rather than by their popularity is also described in the article on agile or traditional.

For the owner, this calls for restraint. When they take part in the round, its character easily shifts from coordinating to reporting. That does not argue against their participation, but for listening rather than questioning.

Conclusion: when does the daily coordination meeting help?

We began by asking
a short daily coordination meeting helps a small team and when it is wasted time. The answer follows from the interdependence of the work. Where contributions mesh closely and colleagues wait on each other every day, the round makes obstacles visible early and saves time. Where everyone works on their own, it becomes a ritual, however short and disciplined it is.

As shown, the studies confirm both sides. The round is valued when it shares information and solves problems, and rejected when it runs as a report to management or is too long. For the small company this means: introduce the daily round when the work requires it, keep it short, solve problems afterwards, and abolish it again when nobody is waiting on anyone anymore.

The next step

1. For one week, count how often someone in the team waited for a colleague's information, approval, or work.
2. Use the number to decide whether a daily round is needed or weekly planning is enough.
3. If so: set the time, place, and three questions, and limit the round to 15 minutes standing.
4. Agree that problems are only named and are solved directly afterwards by those affected.
5. After four weeks, review together whether the round has shortened waiting times.