A daily standup meeting is a short, same-time check-in where a small team shares what moved yesterday, what is planned for today, and what is stuck. Run well, it can replace a scatter of status pings with one predictable moment of coordination. However, run badly, it can turn into a long round of updates that nobody listens to. This guide gives a 15-minute format you can copy, a script for the facilitator, and fixes for the problems that can creep in.
Who this guide is for
This guide is for small business owners, studio founders and small-team leads who coordinate three to ten people on client work. It suits design studios, agencies and service businesses where projects overlap and a stuck task can hold up client work. You do not need to run Scrum or any formal method to use it.
What a daily standup meeting is (and is not)
The practice is closely associated with agile teams. Atlassian’s guide to standups describes it as a short daily meeting to discuss progress and identify blockers, and compares it to a sports team’s huddle. The same guide recommends keeping it to no more than 15 minutes and suggests smaller teams aim even shorter.
The formal version is the Daily Scrum. The Scrum Guide sets it as a 15-minute event held at the same time and place every working day, with the purpose of inspecting progress toward the current goal and adjusting the plan. It also lets the team choose whatever structure it wants, as long as the meeting focuses on progress toward that goal and produces an actionable plan for the next day.
That last point matters for small businesses, because you can borrow the timebox and the focus without adopting the rest of the framework. A standup is not:
- A planning session. Larger planning belongs in a separate weekly or project meeting.
- A performance review. Atlassian’s standups guide notes it is not for justifying job descriptions.
- The only time to raise a blocker. If someone is stuck at 2 p.m., they should ask then, not wait for tomorrow.
- A problem-solving workshop. Problems get named in the standup and solved afterwards by the people involved.
The 15-minute daily standup meeting format
This format keeps the classic three questions and adds a short opening and a clear close. The timings assume five to seven people; with fewer people, finish early rather than filling the time.
| Segment | Time | What happens |
|---|---|---|
| Open | 1 minute | Facilitator states today’s focus: the key client deadline or project goal for the week. |
| Round of updates | 8–10 minutes | Each person answers three questions in about a minute. |
| Blocker sort | 2–3 minutes | Facilitator lists each blocker and names who will help and when. |
| Close | 1 minute | Confirm follow-up huddles and end on time. |
The three questions
Atlassian’s standups guide lists three questions:
- What did I work on yesterday?
- What am I working on today?
- What issues are blocking me?
For client work, however, a small tweak helps. Ask people to name the client or project with each item, for example “Finished the homepage wireframe for the bakery site; today I’m on the menu page; blocked waiting on their logo files.” As a result, everyone hears where effort is going without a separate report.
The “parking lot” rule
A simple rule that helps keep a standup short is this: any conversation that involves only two or three people moves to the parking lot. The facilitator writes it down, and those people meet straight after the standup. Meanwhile, everyone else gets back to work. Say this rule out loud for the first few weeks until it becomes habit.
A facilitator script you can copy
Rotating the facilitator can spread ownership and help stop the meeting from becoming a report to the boss. Atlassian’s guide suggests rotating who keeps time, and the same idea works for running the whole meeting. Here is a script the facilitator can read from:
- “Morning. Our focus this week is [deadline or goal]. Let’s keep this to fifteen minutes.”
- “[Name], you’re first. Yesterday, today, blockers.”
- If someone starts problem-solving: “Good point. Let’s park that and pick it up right after with [names].”
- After everyone has spoken: “Blockers I heard are [list]. Who can help with each, and when?”
- “Parking lot: [topics and names]. That’s it, thanks everyone.”
In addition, keep a simple running note of blockers and parking-lot items in a shared document or on your task board. This gives you a light record without anyone writing minutes.
Worked example: a five-person design studio
Consider a hypothetical studio with a founder, two designers, a developer and an account manager. They run three client projects at once and meet at 9:30 each morning on a video call, because two people work remotely.
The founder opens: “Focus this week is the launch of the clinic website on Friday.” The first designer says she finished the service page layouts yesterday, is starting the contact page today, and is blocked on final photography. The developer says he built the booking form yesterday, will connect it today, and has no blockers. The second designer is on a separate branding project and needs feedback on two logo directions. The account manager chased the photography yesterday and expects it by noon.
In the blocker sort, the facilitator notes two items. First, the photography blocker is already being handled by the account manager, who will message the designer when it lands. Next, the logo feedback goes to the parking lot, and the founder and second designer meet for ten minutes after the call. Overall, the whole standup takes eleven minutes.
Notice what did not happen: no one walked through every task in detail, the logo debate did not take over the meeting, and the founder did not use the time to give instructions to each person. Together, those choices help keep the format useful week after week.
Running a daily standup meeting for remote and hybrid teams
If your studio mixes office and remote staff, Atlassian’s standups guide offers a useful rule: if one team member is remote, treat every team member as remote, so everyone joins individually by video. As a result, this helps avoid a situation where people in the room chat among themselves while remote colleagues struggle to follow.
When time zones make a live meeting impractical, the same Atlassian guide mentions written or recorded asynchronous updates as an alternative. If you go this route:
- Set a deadline, such as updates posted by 10 a.m. in each person’s time zone.
- Use the same three questions so updates are easy to scan.
- Assign one person each day to read all updates and follow up on blockers.
- Hold a short live check-in once or twice a week so the team still talks.
Common daily standup meeting problems and how to fix them
| Problem | Likely cause | Fix |
|---|---|---|
| Meeting regularly overruns | Discussions happen inside the round | Enforce the parking-lot rule and use a visible timer. |
| Updates are vague (“working on stuff”) | No link to projects or goals | Ask people to name the client or deliverable with each item. |
| Nobody raises blockers | People worry it looks like failure | Have leaders share their own blockers first and thank people who raise them. |
| It feels like reporting to the owner | The owner always runs it | Rotate the facilitator weekly. |
| People zone out | Updates irrelevant to most listeners | Order updates by project so related work is heard together. |
| Standup is skipped on busy days | Not anchored to a fixed time | Keep the same time daily, as the Scrum Guide describes, and keep it short. |
Setting up your first week
Use this checklist to launch a daily standup meeting without fuss:
- Pick a fixed start time that suits everyone’s working hours and protect it in calendars.
- Decide on the format: in person, all on video, or written updates.
- Share the three questions and the parking-lot rule in advance.
- Choose the first facilitator and a rotation order.
- Create a shared note for blockers and parking-lot items.
- After two weeks, ask the team what to keep, drop or change, and adjust.
Finally, standups can work well as one part of a wider set of team routines. For more on building those routines, browse our business systems articles.
Key takeaways
A daily standup meeting can give a small team one short, predictable moment to see progress and clear blockers. Keep it to 15 minutes or less, use the three questions with a project name attached, move side conversations to a parking lot, and rotate who facilitates. Adapt the format for remote staff by putting everyone on equal footing, and review how it is working after a couple of weeks. In short, the aim is a meeting that saves more coordination time than it costs.
Written by the Design Productive Editorial desk. Disclosure: this guide contains no affiliate or sponsored links.
