Standup and retrospective formats that actually work

Parabol's catalogue of standup variants runs to fourteen; six cover nearly every real team. The one to avoid defaulting into is the first, which is also the one nearly everyone uses.

If you change one thing, switch from three questions to walking the board. It fixes the two failure modes at once: it removes the incentive to justify your day, and it surfaces the item nobody has touched in a week, which person-by-person updates are structurally unable to reveal.

The timebox is the format's load-bearing constraint, and it fails in predictable ways. Four rules hold it:

• Take discussions offline, by name. "Let's take that after — Sam, Priya, five minutes?" The naming is the part that works; "let's take it offline" without names means it does not happen.
• Stand up, or use a visible timer. The original reason for standing was that discomfort ends meetings. Remote teams need the timer to do the same job.
• Cap attendance at the people whose work interlocks. A twelve-person standup is a status meeting. Two teams of six standing separately is two standups that finish.
• Start on time regardless of who is missing. Waiting punishes the punctual and teaches everyone that the start time is decorative.

If a standup consistently runs long, it is usually not a discipline problem. It is a signal that the team needs a longer coordination meeting once a week, and the standup is absorbing the demand for it.

Retros vary by what they are good at surfacing. Rotating between two or three prevents the format itself becoming the ritual — a team that has run Start/Stop/Continue eleven times in a row produces the same three items every time.

Choose by what the cycle was like. A cycle that went fine but slowly wants Start/Stop/Continue. A cycle with visible tension wants Mad/Sad/Glad. A cycle with one bad incident wants 5 Whys on that incident and nothing else. Picking the format after looking at the cycle, rather than before, is most of what separates a useful retro from a recurring one.

The common retro failure is a wall of sticky notes, general agreement that things could be better, and no change by the next cycle. Four rules fix it, and the first two do most of the work:

• Cap at two or three actions. A retro producing nine actions produces zero. Vote, take the top two, and let the rest go — if they matter they will come back.
• Every action gets a named person and a date. "The team will improve estimation" is not an action. "Priya adds a sizing step to refinement by the 14th" is.
• Open the next retro with the last one's actions. Five minutes. This is the single change that makes people take the actions seriously, because it is the only moment when not doing one becomes visible.
• Separate what you control from what you don't. Keep a short list of the second kind and escalate it, rather than relitigating it every cycle. A retro that spends 40 minutes on a company-wide constraint is how teams learn retros are pointless.

Psychological safety is the precondition for all four. If the retro is attended by someone who writes performance reviews and the team has not agreed how that works, you will get a polite retro with no information in it, and no format will fix that.

Standups and retros are both retrospective, over different windows, and both are limited by the same thing: people remember the last two days vividly and the previous twelve barely at all. A two-week retro run from memory is in practice a retro about last Thursday. Whatever went wrong in week one has faded, which is a shame, because the problems that take a week to become visible are usually the structural ones.

This is where a record changes the meeting rather than just documenting it. Earkeep records mic and system audio continuously while it runs and transcribes locally on your device, so the standups, planning sessions and reviews of an entire cycle are searchable when the retro comes — no bot to invite, no start/stop to remember. Meetings are defined afterwards by selecting a span on a timeline, or automatically from a connected calendar. Audio is processed only in memory and never written to disk, and transcripts are plain files, so "when did that blocker first come up?" is a search across the cycle rather than a question the room guesses at. See meetings after the fact.

It also fixes the smaller, daily version: a blocker raised in Tuesday's standup and forgotten by Thursday is one of the most common ways a standup wastes its own output.

The principles behind these ceremonies — timeboxing, WIP limits, inspect-and-adapt — are in agile, Scrum, and Kanban principles for better meetings. For turning any meeting into recorded outputs, see never leave a meeting empty-handed, and for the whole loop, meeting workflows.

Download Earkeep free for macOS and give your team a record that outlives its memory.