Knowing what is happening without a daily standup
The daily call exists to answer a question that a written format answers better and without occupying fifteen minutes of everyone's morning.
The daily standup survives in distributed teams largely by inertia. It was designed for a co-located group standing near a board, and translated to a video call it becomes a sequence of monologues that most attendees do not need. For broader context on distributed asynchronous work, GitLab’s all-remote handbook is a useful reference.
The underlying question is legitimate: what is happening, and is anyone stuck. The format is the part worth replacing.
What a written check-in has to contain
Three lines, at a fixed time, in one channel.
- What moved since the last one — outcomes, not activity.
- What is next.
- What is blocked, and by whom or by what. This is the only line that requires anyone else to act.
The blocked line is the entire point of the exercise. Everything else is context. A format that buries it in a paragraph of narrative has lost the reason it exists. For a practical software-side reference on aggregate visibility into team activity, workforce analytics software adds useful detail.
A check-in read by a manager scanning fifteen entries should surface blockers at a glance. Putting them at the top costs nothing and is the difference between a blocker resolved today and one resolved on Thursday.
Fixed time, not fixed hour
In a spread team, a single deadline for check-ins is an unfair one. The workable version is relative: within the first hour of your own working day, whenever that is.
The team then reads them when they start, and the effect is a rolling picture rather than a synchronised snapshot — which is a more accurate description of how a distributed team actually works anyway.
Write for the reader, not for the manager
Check-ins written to demonstrate effort become a performance: long, activity-focused, and useless. This is a predictable response to being read by someone who might judge, and the cause is upstream of the format.
The correction is to use them visibly for coordination — responding to blockers, connecting two people working on related things — and never for assessment. A check-in referenced in a performance conversation is the end of honest check-ins.
Keep the synchronous version for the team that needs it
Some groups genuinely benefit from a short daily call: people new to each other, work with heavy interdependence, or a period of crisis. This is a legitimate exception rather than a failure of discipline.
Where it is kept, keep it short and keep the written version too, for whoever could not attend. A call that replaces the record recreates the problem it was meant to solve.
Delete it periodically
Any recurring ritual should be stopped occasionally to see whether anyone notices. Skip the check-in for a week and observe what breaks.
Frequently nothing does, in which case the format was serving a need that has passed. Occasionally something breaks immediately, which is the best possible justification for keeping it.