Remote Daily Stand-Up
Align a small team around progress, priorities, and blockers
- Difficulty
- Starter
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 98%
A remote daily stand-up is a brief coordination meeting built around three signals: recent progress, today's priority, and blockers. Each person gives a concise update so colleagues can see where dependent work stands and where help is needed. The meeting is not a workload contest or a detailed status review. Its value comes from exposing dependencies early and making the next day's work legible to the group. Spiden's team uses a roughly 15-minute version that sometimes resolves a small issue immediately, but longer discussions should move to a separate conversation. Keep the group small and relevant; once attendance becomes large, the meeting shifts from interaction to one-way information sharing and should be split into departmental or workstream groups.
Origin
Lisa Spiden adopted daily stand-ups when an external software team brought agile methods into one of her businesses.
Core principles
- 01A stand-up coordinates work rather than measures busyness
- 02Short updates make dependencies visible
- 03Blockers should surface early
- 04Large groups should split into relevant working teams
How to run it
- 1
Form the working group
Invite a small set of people whose work is connected. Split a large organization into departments or workstreams rather than putting everyone on one call.
Pro tip Spiden suggests groups of roughly seven people.
Watch out A 50-person call is likely to become an update broadcast rather than an interactive stand-up.
- 2
Report recent progress
Each participant briefly states what they completed since the previous stand-up. Include only information that helps the group coordinate.
Pro tip Aim for seconds per person in the classic format.
Watch out Do not use the update to rank who appears busiest.
- 3
Name today's priority
Each participant states the work they intend to move forward that day. This clarifies ownership and dependencies.
Watch out Avoid turning the update into a detailed task recital.
- 4
Surface blockers
Ask what help or decision is needed. Resolve a genuinely short issue immediately and move anything deeper into a smaller follow-up.
Pro tip End with clear ownership for each follow-up.
Watch out Letting one issue consume the meeting removes the benefit for everyone else.
In the wild
A seven-person product team meets each morning. Members state what moved yesterday, what they will move today, and any help they need. A quick dependency is clarified on the call; two people take a larger technical issue into a follow-up.
→ The team starts the day with visible priorities and blockers without creating a long status meeting.
Common mistakes
Measuring busyness
The stand-up exists to coordinate interrelated work, not to compare workloads or perform productivity theater.
Inviting the whole company
A large group reduces interaction and makes concise, relevant updates difficult.
Solving every issue live
Deep problem-solving turns a short alignment ritual into a long meeting for people who are not involved.
Is it for you?
Best for
Small teams whose members depend on one another's progress to keep work moving.
Not ideal for
Large all-company calls or teams whose work has few daily dependencies.
From the transcript
“what they got done the day before and what they're working on that day and any blockers”
“it's not intended to be a how busy is everyone”
“break it down instead of doing smaller teams of seven or seven or so people”
From the episode
333: The Top Mistakes to Avoid when Managing Remote Teams with Fibre HR Foundr Lisa Spiden
Lisa Spiden