Stand-Up

A stand-up — or daily stand-up — is a short, time-boxed team meeting, usually held at the same time each day, in which team members briefly share what they have done, what they plan to do next, and anything blocking their progress. It is meant to be quick, typically around fifteen minutes, and the name comes from the practice of holding it standing up to keep it short and focused — sitting invites it to sprawl. The classic format has each member answer three questions: what did I do since the last stand-up, what will I do before the next one, and what is in my way. The stand-up's purpose is alignment, not detailed problem-solving: it surfaces progress, plans, and blockers quickly so the team stays coordinated and impediments are raised early, with deeper discussions taken offline afterward.

The stand-up originates in agile software development, and specifically in Scrum, where the equivalent ceremony is the daily Scrum — a short daily event for the team to inspect progress toward its goal and adapt its plan. From those agile roots the daily stand-up has spread widely beyond software, into marketing teams, operations, and many other kinds of work, wherever a team benefits from a quick daily sync. Its value is in lightweight, frequent coordination: instead of letting work drift and problems fester until a weekly meeting, the team checks in briefly every day, so misalignment and blockers are caught fast. The discipline of keeping it short and focused is what makes it useful — a stand-up that turns into a long status meeting or a problem-solving session has lost the point.

A stand-up is deliberately different from a traditional status meeting, and the difference is the whole idea. A status meeting tends to be longer, often less frequent, and frequently a one-way reporting of status up to a manager. A stand-up is short, daily, time-boxed, and for the team's own coordination — members sync with each other, not just report to a boss. The three-question format keeps it tight, and the standing-up convention keeps it from sprawling. Detailed discussions are explicitly deferred ("let's take that offline") so the stand-up stays a quick alignment ritual rather than a working session. When a stand-up drifts into long updates, deep problem-solving, or manager-directed reporting, it has effectively become the status meeting it was meant to replace.

The agile and Scrum roots explain both the format and the intent. Agile methods favor frequent inspection and adaptation over heavy up-front planning and infrequent check-ins, and the daily stand-up is that principle applied to daily coordination — a small, regular feedback loop that keeps the team aligned and surfaces impediments early enough to act on them. In Scrum it is one of several events with a defined purpose and time-box. As the practice spread beyond software, the core idea traveled with it: a brief, regular, team-owned sync focused on progress, plans, and blockers. Teams adapt the details — some skip the rigid three questions, some run it remotely or asynchronously — but the essence remains a short, frequent, lightweight alignment ritual, distinct from the longer, heavier status meeting it was created to improve on.

Running a stand-up well means protecting what makes it useful — keeping it short, regular, and focused on alignment, not turning it into a status report or a problem-solving session. That means time-boxing it firmly, keeping to a tight format (progress, plans, blockers), having the team sync with each other rather than report to a manager, and deferring any detailed discussion to a follow-up with only the relevant people. It means surfacing blockers as the priority — the whole point is to raise impediments early so they can be cleared — and adapting the format to the team (in-person or remote, strict three questions or looser) while preserving the brevity and focus. A good stand-up leaves the team aligned and unblocked in fifteen minutes, then gets out of the way.

The failures are letting the stand-up sprawl into a long meeting, turning it into one-way status reporting to a manager, diving into detailed problem-solving that should be taken offline, reciting activity without surfacing real blockers, and holding it out of ritual when the team gains nothing from it. The discipline is to keep the stand-up true to its agile purpose — a short, time-boxed, team-owned daily sync of progress, plans, and blockers — protecting its brevity and focus so it delivers fast alignment and early blocker-surfacing, rather than degrading into the kind of long, low-value status meeting it was designed to replace.

Stand-up — a short, time-boxed daily team sync rooted in agile and Scrum — keeps a team aligned by surfacing progress, plans, and blockers fast, distinct from the longer status meeting it was made to replace.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where stand-up is a core concern: