Automating away our daily standup in Slack
Our daily call had stopped surfacing new information and started repeating what Slack already showed. Here's what we replaced it with: tasks that follow up on their own, issues with visible owners, and a weekly pulse digest instead of a meeting nobody wanted.
For a long stretch, our mornings started the same way. Whoever was around would hop on a call, go around the group, and answer three questions: what did you do yesterday, what are you doing today, is anything blocking you. Fifteen minutes if it went well, twenty five if someone's update turned into a design discussion that really belonged in its own meeting. We kept doing it because stopping felt risky. Without the call, how would anyone know what was blocked, or notice that two people had quietly started working on the same thing?
Why the meeting outlived its usefulness
The honest answer is that the standup wasn't really failing at its job. It was succeeding at a job that had already been done somewhere else. By the time the call started, most of what people reported had already happened in Slack the day before, a task got closed, a bug got filed, a blocker got flagged in a thread. The meeting's real function had quietly shifted from surfacing information to repeating it out loud for an audience that had, in most cases, already seen it scroll by.
What kept it alive wasn't need, it was habit and a bit of fear. Nobody wanted to be the one who suggested cutting the one ritual that gave the team a shared sense of where things stood, even after most of that sense was already available elsewhere.
What the standup was actually protecting
Underneath the ritual, three things genuinely mattered: knowing what was blocked, knowing who owned what, and catching when two people had drifted onto overlapping work without noticing. None of those three things require a synchronous call. They require the information to be visible somewhere people already look.
That's the part we changed first. Tasks created from a thread carry a due date, and Via follows up in the channel the morning that date arrives instead of waiting for someone to ask about it out loud. Leave a task unclaimed and it goes up for grabs automatically rather than sitting quietly on one person's mental list. A blocker raised in a thread becomes a tracked issue with an owner, visible to anyone who opens the channel, not just the six people who happened to be on the call that morning.
The rhythm that replaced the ritual
The piece we hadn't expected to miss was the roll up, the moment at the end of the call where someone said "anything else before we wrap" and half the useful information actually came out. We replaced that with Viably's weekly pulse, a digest that lands in the channel and pulls together what's actually true right now: open issues, tasks nobody has claimed yet, reminders coming due, pins about to expire, and who moved on the recognition board that week. Nobody has to compile it and nobody has to sit through it live. It's there when someone wants the wide view, and easy to ignore on a week when nobody needs it.
| What the standup covered | Where it lives now |
|---|---|
| What shipped yesterday | Already visible in the channel it shipped in |
| What's blocked | A tracked issue with an owner, not a verbal note |
| What's still open | Tasks with due dates and automatic follow ups |
| The weekly roll up | The weekly pulse digest, posted automatically |
A meeting earns its spot on the calendar by producing something the tools around it can't. Ours had quietly stopped.
What we lost, and what we didn't
We'd be lying if we said nothing was lost. There was a social beat to the call, a moment where the team heard each other's voices before diving into the day, and that's worth naming honestly rather than pretending automation replaces it. What we didn't lose was visibility. If anything, blockers surface faster now, because a tracked issue doesn't wait for the next morning's call to get noticed, and an unclaimed task doesn't rely on someone remembering to bring it up.
The meeting we cut wasn't a bad meeting. It was a good answer to a problem that automation was already quietly solving underneath it. Once we noticed that, keeping the call going stopped making sense.
If your team's status updates already live in Slack threads, add Viably and see what a morning without the call actually looks like, or read about how tasks and reminders fit together.