Why recurring meetings grow
A standing meeting is a recurring slot on the calendar, such as a daily team check-in or a weekly sync. It usually starts with a clear purpose. Over time, it picks up extra jobs: detailed discussions, announcements, problem-solving and social chat. Because the slot already exists, nobody has to decide whether to hold it, and so it keeps going whether or not there is much to say.
Making these meetings shorter is mostly a matter of narrowing the purpose and building a few habits that protect it.
Start by restating the purpose
Ask the group what the meeting is for. Typical answers for stand-up meetings are to share what people are working on, to surface blockers and to coordinate who needs whom that day. That is a narrow job and it should not take long.
Anything that does not serve that purpose is a candidate to move elsewhere. A written purpose statement at the top of the agenda or invite, ideally one sentence, gives the facilitator something to point to when the conversation drifts.
Practical ways to keep it brief
Fix the length and shorten the default. If the calendar default is 30 minutes, the meeting will tend to take it. A 10 or 15-minute slot sets a different expectation. Many teams find that the standing format works best when it is clearly short.
Use a simple structure. A common pattern is three prompts per person: what I finished, what I am working on, and what is in my way. Keep answers to a sentence or two. Some teams skip the “finished” part when the information is already in a shared task list.
Stand up, literally or figuratively. The name comes from a practice of standing so that people do not settle in. Where physical standing is impractical or uncomfortable, which is true for many people, a visible timer or a rule about speaking time can serve the same purpose.
Take detailed topics offline. When an item needs more than a minute or two, note it and let the people involved continue afterward. The rest of the group can leave. Facilitators can use a simple phrase such as “Let’s take that after this meeting.” This is a core part of good meeting facilitation.
Move updates to writing. If most of the content is status information, consider a short written update posted at a set time. The live meeting can then focus on blockers and questions. Some teams use a written format entirely for a few days a week.
Keep the same order. A predictable sequence lets people prepare what they will say and cuts hesitation.
Start on time and finish early when possible. Ending a few minutes early is a good result, and it signals that brevity is a goal.
Reduce the attendee list
The group that benefits from hearing every update is usually smaller than the group invited. Review the attendees and ask whether each person is needed for the purpose. Optional attendance, with notes shared afterward, can help people who are only loosely connected to the topic. Protecting stretches without meetings can also help, as discussed in the material on meeting-free time.
When to cancel or skip
Not every occurrence needs to happen. Some reasonable situations for skipping:
- Nobody has any updates or blockers.
- Most of the team is out, for example during holidays or an all-hands event.
- The information can be covered in a written update that day.
- A major deadline is close and people need heads-down time.
A simple convention is that the meeting happens by default but the organizer, or any member, can propose cancelling a session when there is nothing to discuss. Another is the reverse: the meeting is canceled by default unless someone adds a topic by a set time. Which approach fits depends on the team.
Cancelling occasionally is a healthy sign. It shows the meeting serves the team rather than the other way round.
Run a periodic review
Every couple of months, ask the group a few questions:
- Is this meeting still useful? What would we lose without it?
- Is it the right length?
- Is it at the right time of day? Some people focus best in the morning and find a mid-morning interruption costly, a point connected to protecting sustained focus.
- Should it run every day, or would two or three times a week do?
- Could part of it be replaced with a written update?
You could run this as a short anonymous poll or a few minutes at the end of a session. Be ready to change the format, reduce the frequency or end the meeting entirely if it has run its course.
Considerations for different teams
There is no single right frequency. Teams with fast-changing work, tight coordination or newer members often value daily contact. Teams with steady, independent tasks may do just as well with a weekly check-in or a written thread. Remote and distributed teams, particularly those across time zones, may rely more on written updates and on shared remote work habits that reduce the need for synchronous time.
Also consider people’s circumstances. A fixed early or late meeting can be hard for those with caregiving duties or health needs, so check what works for your colleagues and your employer’s guidelines.
A quick starting plan
- Write the purpose of the meeting in one sentence.
- Shorten the slot by five or ten minutes and see what happens.
- Adopt a three-question format and a rule for taking detailed topics offline.
- Allow cancellation when there is nothing to report.
- Review after a month and keep only what helped.
Small changes like these often make a recurring meeting more useful, and the time saved adds up across a team over weeks and months.