If your daily standup feels like a status report to your boss, you’re doing it wrong.

Let me tell you about the worst standup I ever attended.

It was 45 minutes long. Sixteen people crowded around a conference table (and another seven dialling in from remote, their faces frozen on a laptop screen). One person droned through every line of code they’d written the day before. Another hijacked the meeting to solve a complex architectural problem live. The product manager took notes like it was a performance review. And I sat there thinking: This is not what we signed up for.

That team was miserable. But here’s the thing: they weren’t alone. I’ve seen the same pattern play out at startups, agencies, and Fortune 500s alike. The daily standup, in theory one of Agile’s most powerful ceremonies, had become a weekly (or daily) exercise in tedium.

So let’s fix that.

What Is a Standup Actually For?

Before we get into mechanics, let’s get clear on purpose.

The daily standup is a short, focused sync for the team to surface blockers and coordinate, not a status report to a manager.

Repeat that to yourself. Highlight it. Stick it on your monitor.

The goal isn’t to justify your existence or prove you’ve been “productive.” The goal is to answer one question: Are we still on track together, and what’s getting in our way?

When standups work well, they feel like a pit stop in a race: quick, efficient, and entirely focused on getting back on the road.

The Classic Three Questions (and Why They Work)

You’ve probably heard these before:

  1. What did I do yesterday?
  2. What will I do today?
  3. Is anything blocking me?

These questions aren’t magic. But they create a useful structure that keeps things moving and prevents people from wandering into irrelevant territory.

The key word in question one is “yesterday”, not “last week” or “since we last met.” Yesterday keeps it recent, relevant, and brief.

Question two isn’t a detailed project plan. It’s a directional signal: “Here’s what I’m tackling next so everyone knows where I’ll be.”

And question three? This is the most important one. If someone says “no blockers” without thinking, they might be missing the opportunity to unstick themselves. Encourage genuine reflection here.

The 15-Minute Rule (and Why Standing Helps)

Here’s a simple but surprisingly effective trick: stand up during your standup.

If you’re in person, literally have everyone stand. It creates a gentle physical pressure to stay concise. You’ll notice people naturally keep things shorter when they can’t sink into a chair.

Of course, this gets trickier with remote teams. But the principle still applies: keep it short, keep it focused, and keep it moving. 15 minutes should be your hard cap.

If you consistently go over, something is wrong. Either your team is too large (split into smaller groups), or you’re letting problem-solving creep in.

Speaking of Which: Take Problem-Solving Offline

This is the number one cause of standup bloat.

Someone mentions a tricky technical issue. Another person starts brainstorming solutions. Before you know it, six people are deep in a whiteboard session while everyone else stands there awkwardly, waiting to share their update.

Here’s the rule: If a discussion requires more than two follow-up questions, it goes offline.

Agree as a team that when someone says “I’m blocked on the API response format,” the response is “Let’s grab a few minutes after standup” or “Jim, can you sync with them afterwards?” Not “Well, have you considered using a different endpoint and restructuring your data model and”

Save the detailed problem-solving for the people who actually need to be in that conversation.

When Standups Go Wrong: Common Failure Modes

Let’s be honest about why standups fail. I’ve seen all of these:

The Status Report to Management
When the product manager or Scrum Master treats standup as an opportunity to audit individual performance, the entire dynamic changes. People start talking defensively. They pad their updates. They avoid mentioning blockers because they don’t want to look bad.

Fix this by shifting the language. Remind everyone: “We’re not reporting to anyone. We’re coordinating. This is peer-to-peer.”

The Problem-Solving Trap
We covered this above. It’s the silent killer of standup efficiency.

Going Through the Motions
The worst standup I ever attended? Actually, the worst standup is the one where everyone says the same thing every day. “Working on ticket ABC-123.” “Still working on ticket ABC-123.” No blockers. No coordination. Just ritual.

If your team is doing this, ask the hard question: Does this format still serve us? Maybe your team doesn’t need a daily sync. Maybe a weekly check-in and async updates are enough. Or maybe you need to shake up the format to keep it fresh.

Too Many People
The 15-minute cap assumes a team of about 3–9 people. If your standup has 15 people, you’re not having a standup you’re having a small town hall. Break into smaller teams or rotate who attends.

Remote and Async Variants: The Modern Reality

Let’s be real: many of us work on distributed teams across multiple time zones. A live daily standup at 9 AM might mean someone in a different country is joining at 2 AM.

Here’s how remote teams are succeeding:

Live Video Standups
Many teams still do live standups over Zoom or Teams. This preserves the human connection and real-time coordination. Just keep it tight with the same principles: stand up (even at your desk), stay on point, and spin off detailed discussions.

Async Written Standups
Some teams use Slack threads, Teams channels, or tools like Geekbot, Range, or Standuply. Team members answer the three questions asynchronously in a shared space. Everyone reads updates on their own time.

This is especially powerful for cross-time-zone teams. I’ve seen this work beautifully when the team sets a clear expectation: “Post your update by 10 AM your time, and everyone reads before their workday begins.”

The tradeoff? You lose the real-time coordination and the chance to quickly unblock each other. But many teams find that the flexibility is worth it and they save 15 minutes a day that adds up over months.

Making Your Standup Actually Valuable

Here’s what I’ve learned from working with teams that have fantastic standups:

Rotate the facilitator. It keeps everyone engaged and prevents any one person from dominating.

Start and end on time. If you’re late, you wait until the next person’s turn. Harsh but effective.

Use a physical or digital board. Have your Jira board or physical task board visible so people can reference ticket numbers without explaining them from scratch.

Periodically ask: “Is this working?” Every month or two, have a five-minute conversation about the standup format itself. If it’s not serving the team, change it. The Agile Manifesto literally says to inspect and adapt, so do it.

Celebrate wins. Sometimes, a quick “Hey, great job on that release” can boost morale without derailing the meeting. Keep it brief, but don’t forget to acknowledge progress.

A Final Thought: Standups Are a Tool, Not a Religion

I’ve seen teams treat the daily standup like sacred scripture: “We must do it exactly at 9:05 AM every day or the gods of Agile will be displeased.” That’s missing the point.

Agile is about people and interactions over processes and tools. The standup serves your team, not the other way around. If it’s not working, change it. If it’s working brilliantly, keep doing it.

The best standup I ever attended lasted under eight minutes. Everyone shared updates, surfaced one blocker, and coordinated on a dependency. Then we all went back to work, feeling aligned and informed.

That’s the goal.

What’s your experience with daily standups? Love ’em? Hate ’em? Tried something creative that worked? I’d love to hear about it in the comments, whether you’re a standup evangelist or a certified standup sceptic.