Standup Meeting¶
Coordination ritual — instantiates Cadence Design
A short, daily, synchronous huddle for the people doing the work to surface blockers and sync the next stretch — no decisions, no artifact, just alignment.
A Standup Meeting is a short, frequent, synchronous huddle whose only job is to keep the people actually doing the work aligned on the immediate stretch — surfacing blockers, flagging dependencies, and re-pointing effort for the day or shift. Its defining constraint is deliberate poverty of purpose: it makes no decisions, produces no artifact, and holds no one but the doers. The value is the live, high-frequency touch itself — everyone hears the same picture at the same moment and leaves knowing where the friction is. Kept short and kept to the working team, it is coordination; let it grow decisions, spectators, or length and it becomes the empty ritual it is most at risk of.
Example¶
A hospital medical-surgical unit starts each day shift with a ten-minute safety huddle at the nurses' station. The charge nurse and the on-shift nurses and techs stand — chairs would invite a meeting — and each person answers a tight script: what's the state of my patients, what could go wrong today, what do I need from someone here. A tech notes the ceiling lift in room 12 is down; a nurse flags a patient at high fall risk who keeps trying to walk; the charge nurse hears a staffing gap at the afternoon handoff.
The huddle ends in ten minutes with no minutes taken and nothing decided by committee — the charge nurse simply now knows to chase facilities on the lift, pair the fall-risk patient with a closer eye, and pre-arrange coverage before it becomes a crisis. Nobody left to write a report or wait for an approval. The value was that the whole team surfaced the day's friction out loud, together, before it turned into a fall, a missed handoff, or a broken lift discovered at the worst moment.
How it works¶
A standup is distinguished from an ordinary recurring meeting by what it refuses to be:
- Short and boxed. A hard, small time budget (often standing, literally, to enforce it). The frequency, not the depth, carries the coordination.
- High-frequency and forward-looking. Daily or per-shift, aimed at the next short interval — today, this shift — not at review or retrospection.
- The doers only, no spectators. Bounded to the people whose work actually interlocks. Anyone who is there to listen rather than coordinate is a sign the huddle is drifting toward a status meeting.
- Blockers over reports. The point is to surface friction and hand it off, not to narrate progress. Deep problems are taken offline — named here, solved after.
The cadence's value is cheap, frequent re-synchronization: small enough to run every day, tight enough that it stays worth the daily cost.
Tuning parameters¶
- Frequency — daily, per-shift, or a few times a week. More frequent keeps the team tighter but taxes attention; too rare and coordination gaps reopen between huddles.
- Time box — the hard cap. A tight box forces focus and protects the day; a loose one lets the huddle sprawl into the status meeting it's meant to replace.
- Attendee boundary — strictly the interlocking doers versus a wider circle. Widen it and you gain visibility but lose the candor and speed that make it work.
- Script tightness — a fixed round-robin prompt versus open floor. A script keeps it fast and even; open floor surfaces more but risks a few people dominating.
- Offline-it threshold — how quickly a surfaced problem is deferred to a smaller conversation. Aggressive deferral protects the box; timid deferral lets one issue swallow the huddle.
When it helps, and when it misleads¶
Its strength is a very low-cost, very high-frequency coordination touch: friction and dependencies surface daily, before they compound, without the overhead of a real meeting.
Its failure modes are the ones the parent archetype warns of most sharply. It becomes empty ritual when it outlives its coordination need — preserved on the calendar after the work stopped interlocking, so people recite status to no purpose. It bloats into a status meeting when spectators and managers join and the huddle turns into serial reporting to an audience rather than syncing among peers. And it can swallow real problems when a hard issue is debated on the spot instead of taken offline, blowing the time box and losing the rest of the team. The discipline that guards against these is to keep it short, keep it to the doers, take deep problems offline, and retire the huddle honestly when the work no longer interlocks — repetition is not coordination.
How it implements the components¶
A Standup Meeting owns the live-sync corner of the archetype — the frequent, tightly-bounded coordination touch:
cadence_purpose— the recurrence exists to surface blockers and re-synchronize near-term work; that explicit, narrow purpose is what keeps it from becoming ritual.recurrence_interval— daily or per-shift, matched to how fast coordination drift accumulates in fast-moving work.participation_boundary— strictly the people whose work interlocks; spectators and decision-makers are deliberately excluded to preserve candor and speed.
It deliberately produces no expected_output and no cadence_artifact — a standup surfaces friction and dissolves; the durable-plan output belongs to Weekly Review and the published, broadcastable artifact to Status Digest. Its nearest twins are those two recurring check-ins: unlike Weekly Review's solo reflective audit and unlike the async Status Digest, a standup is a live, synchronous team sync — and unlike Governance Meeting Cycle, it makes no decisions.
Related¶
- Instantiates: Cadence Design — the standup supplies a cheap, high-frequency synchronous touch that keeps interlocking work aligned.
- Sibling mechanisms: Weekly Review · Status Digest · Governance Meeting Cycle · Budget Cycle · Release Train · Recurring Inspection · Training Cycle · Maintenance Schedule
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Standup Meeting operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it a short, daily, synchronous huddle for the people doing the work to surface blockers and sync the next stretch — no decisions, no artifact, just alignment.
Independent corroboration: The frozen evidence defines Standup Meeting as 'A short, daily, synchronous huddle for the people doing the work to surface blockers and sync the next stretch — no decisions, no artifact, just alignment', so its operative form is Communication, Facilitation & Learning.
Nearest alternative: Organization, Role & Governance — Standup Meeting includes features of an enduring role, team, authority, channel, or governance body that allocates responsibility, but its defining operation is a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: The short daily synchronization huddle is agile work-management practice.
Related originating lineages:
- Computer Science & Software Engineering — Software teams popularized daily standups.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a short, daily, synchronous huddle for the people doing the work to surface blockers and sync the next stretch — no decisions, no artifact, just alignment.
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin disagreement, domain reach disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain single_lineage because the combined evidence shows one traceable formative lineage. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=false preserves the affirmative synthesis judgment where either reviewer identified one.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The single most common way a standup fails is silent: it keeps happening long after the work stopped interlocking, because no one owns the decision to end it. A standup is worth its daily cost only while there is genuine, frequent coordination to do — which is why the honest move, when the huddle goes quiet, is to retire or re-scope it rather than let attendance decay into a hollow ritual.