---
type: "article"
title: "The case against daily standups"
summary: "Standups optimize for the manager's anxiety, not the team's flow. Here's what to run instead."
newsletter: "The Weekly Shift"
newsletter_handle: "weekly-shift"
newsletter_url: "https://staging.in.usecommune.com/n/weekly-shift"
author: "Fran Méndez (@fmvilas)"
published: "2026-08-22T08:30:00.000Z"
canonical_url: "https://staging.in.usecommune.com/n/weekly-shift/a/the-case-against-standups"
markdown_url: "https://staging.in.usecommune.com/n/weekly-shift/a/the-case-against-standups.md"
chat_url: "https://staging.in.usecommune.com/n/weekly-shift/a/the-case-against-standups/chat"
body_source: "native"
likes: 8
replies: 0
body_words: 144
---

# The case against daily standups

Every team I've worked with treats the daily standup as sacred. Nobody remembers deciding to have it. It was just there, like the office coffee machine.

## What standups actually optimize for

The honest function of a standup is reassurance for whoever feels least in control. That's usually a manager. The cost is thirty context-switches a week spread across the whole team.

> If your status update fits in a sentence, it belongs in writing. If it doesn't, a fifteen-minute meeting won't save it.

## The async replacement

- A written check-in thread each morning: blockers first, then progress.
- A weekly 45-minute sync for the things that genuinely need a room.
- A visible board so 'what are you working on' answers itself.

We ran this for a quarter. Cycle time dropped, and nobody missed the circle of people staring at their shoes.

***

## Discussion

No replies yet.