Daily Standup Guide

The standup has one job: keep the team aligned on what is happening, what is blocked, and what comes next. That is it.

It is not a status report to a manager. It is not a problem-solving session. It is not optional when the team is heads-down. The daily cadence is the point. A team that skips standups when "nothing is happening" is a team that will consistently be surprised when something is.

Fifteen minutes. Same time every day. Structured format so it does not drift.

Sync vs. Async

Both work. Neither is inherently superior. The choice depends on how the team operates.

Synchronous standup: The team meets, live or over video, at a fixed time. Works well for co-located teams or teams with significant time zone overlap. The social layer of a live standup, picking up on tone and energy, is real and has value.

Asynchronous standup: Each team member updates their status in GoalPath during their morning, before their first focus block. The team lead reviews highlights and blockers and posts any follow-ups. Works well for distributed teams with wide time zone spreads.

Async standups lose the social signal. Sync standups require coordination. Most teams with tight overlap benefit from sync. Most teams spanning more than four time zones benefit from async. Hybrid teams can do both: async for daily updates, sync for the weekly version with everyone present.

Regardless of format, the four stages stay the same.

The Four Stages

GoalPath's standup feature runs through four stages in sequence. Whether the team runs sync or async, this structure keeps the session focused.

Stage 1: Inbox (2 min)

Review any unplanned items added since the last standup. Every item that arrived without being part of the current milestone plan gets surfaced here.

The question for each item: does this belong in the current scope, or does it get deferred?

This is a triage decision, not a planning session. Assign a triage priority: Incident (respond now), Expedite (next available slot), Standard (work it in normally), Deferred (acknowledge and park). Do not debate scope or estimate effort at this stage.

If there are many inbox items, that is a signal worth noting, not a reason to extend the standup. High inbox volume belongs in the next alignment meeting, where there is time to address it properly.

Stage 2: Highlighted Items (3-5 min)

Review items with active highlights: Blocked, Question, or Discussion.

These items need attention. Someone is stuck, a requirement is unclear, or a decision is pending that cannot wait. Go through each highlight and assign it to someone. Who is unblocking this? Who answers the question? Who is involved in the discussion?

The standup does not resolve blockers. It assigns them. The resolution happens offline, between the people who can actually move the item forward.

If a blocker has been open for more than two standups and is not progressing, that is worth naming. A blocker that nobody is actively addressing is not a blocker: it is a delay in disguise.

Stage 3: Team Members (5-10 min)

Each person on the team covers three things:

  1. What did I finish since the last standup?
  2. What is blocking me right now?
  3. What am I working on next?

GoalPath shows each team member's current assigned items. The check-in uses that view directly. No verbal summary of a list that's already on screen. Point at the item, note the state, flag anything that needs attention.

Keep each person to two minutes or less. If someone needs more time to explain a blocker or handoff, take it offline. Note absent team members and who is covering their critical items if anything is time-sensitive.

The peer-to-peer orientation matters. Team members are not reporting up. They are synchronizing with each other. The facilitator's role during check-in is to keep time and note dependencies between people's work, not to evaluate or direct.

Stage 4: Let's Get Going (1 min)

Confirm priorities. Is what everyone said they are working on actually the highest-value next step? Are there dependencies between people that should be coordinated before the session ends?

Then close. "Go build" is a complete sentence.

Time-Boxing

Fifteen minutes total. That is the budget.

If a topic needs more than two minutes, it gets taken offline. The standup is not the place to solve a technical problem, hash out a requirement, or conduct a code review. Those conversations are valuable and should happen. They should not happen in the standup.

The discipline of a short standup is not about the time. It is about the signal it sends: the team respects each other's focus time enough not to extend a daily sync beyond what it needs to be.

GoalPath's standup interface includes a timer. Use it.

Common Standup Anti-Patterns

Status reporting to the manager. When team members direct their check-in at the most senior person in the room, it signals a management dynamic that undermines peer coordination. The standup is for the team. If the manager is in the room, they check in like everyone else.

Problem-solving in the standup. "I'm blocked on the API integration" should produce "talk to Priya after this" in the standup, not a ten-minute technical discussion. The standup identifies problems. The team solves them elsewhere.

Skipping because nothing happened. "I don't have an update today" is still an update. The cadence is the point. A team that shows up every day, even when nothing is changing, is a team that catches drift early.

Rehashing yesterday. The check-in should move forward. What is done, what is blocked, what is next. Extended discussion of completed work belongs in a review or retrospective.

Running without the data. Standing up without looking at the actual items tends to produce vague updates that are not actionable. GoalPath's standup view is designed to run alongside the meeting, not as a pre-read that people glance at the night before.

How GoalPath Handles This

GoalPath has a built-in standup feature that structures the four stages as a guided flow.

Standup view. The interface walks through Inbox, Highlighted Items, Team Members, and Let's Get Going in sequence. Each stage surfaces the relevant data automatically, so the facilitator does not need to pull information from separate views.

Team-specific standups. Projects with multiple teams run separate standups per team. Each team sees only their items, their inbox, and their highlights. Cross-team blockers surface as highlights and get escalated to the next alignment meeting.

Per-member tracking. GoalPath shows each team member's current assigned items during check-in. Items move through status transitions during the standup itself: mark something Finished, mark the next thing Started, right in the interface.

Absent tracking. Mark team members as absent for the session. Their items remain visible so the team can identify coverage gaps.

Notes panel. Capture decisions, action items, or follow-ups during the standup. Notes are attached to the session and visible after the meeting ends.

Timer. A visible timer counts the session. Keeps the facilitator honest about pace without requiring manual timekeeping.

Related Ceremonies

See also: The GoalPath Development Process for the full framework overview.