Async Standups on a Kanban Board: Replacing the Daily Meeting
Written by Georgii Garanin, Founder, Taskora
TL;DR: An async standup replaces the daily meeting with a written check-in that lives on the board: three questions, posted as a comment on the task you are working on today, read by everyone on their own schedule. The board carries the status, so the meeting's real job narrows to two things the columns cannot show: intent for today and blockers in words. A comment thread covers both for distributed teams. Written standups fail in four specific ways, and this article shows the routine, the template, and the handful of situations where you should keep the live call anyway.
What an async standup actually is
An async standup is a written daily check-in posted where the work lives instead of spoken in a meeting. Each person answers three questions in a few sentences, attached to a card on the board, and the team reads and replies on their own schedule. Nobody stands, nobody waits for a call slot, and nobody sits through nine updates to hear the one that mattered to them.
The term gets misused, so keep three things straight. A check-in written to satisfy a boss becomes a status report, and the team stops reading it. No software does this for you, because the habit is the setup. And a chat channel is the wrong home for it: a check-in posted there scrolls away and takes the card's context with it. The card is where the task's reasoning is supposed to live, so that is where the check-in goes.
A morning standup spends fifteen minutes of every person's day transmitting information the board already displays, and a written check-in transmits it once, in a form everyone can read at 9:15 their time.
What the daily meeting actually does
Before replacing the daily standup, be honest about its jobs. Scrum calls it the daily scrum, and it answers three questions out loud: what moved since yesterday, what I am doing today, and what is blocking me. Underneath the format, the meeting performs three distinct jobs.
First, it surfaces blockers out loud, early, while they are still cheap. Second, it aligns today's intent, so twelve people pull in roughly one direction. Third, it creates light accountability: saying your plan to the room makes skipping it feel real.
A board answers the first question by itself. The columns are the status. Where a card sits is the answer to "what moved", updated continuously instead of once a day at 9:00. That is why a kanban board is the natural home for an async standup: most of what the meeting carries is already on the board, current and timestamped. What the columns cannot show is the second and third job. A card in "In Progress" says nothing about whether you plan to finish it today, and a card stuck for three days looks like focus even when it is blocked. Written comments carry exactly that layer.
How to run one on a kanban board
The routine is short enough to run from memory by the end of a week.
- Move your cards first. Update the board to reality before you write anything. The check-in is written against the board, so the board going stale poisons the whole ritual.
- Post your check-in as a comment on your main card. If your day spans several cards, post it on the one you are pushing hardest, and reference the others by name.
- Answer the three questions in writing. Three to five sentences total. The template below keeps it tight.
- Mention the person you are blocked on. A mention puts their name on the card. A hopeful sentence buried in a paragraph does not. Naming the blocker's owner is the difference between a recorded problem and a solved one.
- Read your team's check-ins once, in one place, at whatever hour suits you. Reply in writing where a reply matters. A question on a check-in keeps it alive the same way a raised eyebrow does in a meeting.
- Escalate what writing cannot hold. Two people going back and forth four times in a thread is a conversation that wants a call. Park it, take it live, and write one line into the thread afterward with what was decided.
That is the whole system: board first, comment second, mention when blocked, read once, escalate honestly.
The three-question template
Keep the template boring on purpose. Your future self and your teammates skim it, and boring survives busy weeks.
- Finished since the last check-in: one or two lines, pointing at cards.
- On it until the next check-in: your main card, plus anything you plan to touch.
- Blocked or at risk: what is stuck, who you are waiting on, and what could slip.
Rules of thumb that keep it useful. Link or name the card you are talking about so readers can jump without guessing. If you are waiting on a person, say who and what you need from them. If nothing is blocked, say so plainly, because "nothing blocked" is information. If a blocker resolved mid-day, a one-line follow-up comment on the same thread closes it, and the thread reads like a small story of the day.
That is the core template. Teams adapt it. Some add "who reviewed my work yesterday", some drop question one entirely because the board's card movement covers it.
Where async beats the live call
Distributed teams feel the win immediately. A team spread across four timezones has exactly zero meeting slots that are 9:00 for everyone, and the standard compromise puts someone on the call in their evening, which quietly taxes the same people every day. Async removes the tax, because the check-in waits for each reader.
Quiet teammates get equal airtime. In a live standup, the loudest three voices set the day's tone, and the person mid-thought gets talked over. Writing flattens that out: everyone gets the same space, and the careful thinkers contribute as visibly as the confident ones.
The paper trail is the third win. A week of written check-ins is quotable, skimmable, and readable by someone who was out sick. "What happened on the billing task last Tuesday" has an answer in the thread instead of in nine memories, and the version history on the docs beside the board plays the same trick in longer form.
Deep work gains the most. A 9:00 meeting splits the one uninterrupted morning block the team would have had. The same fifteen minutes, spent reading three check-ins whenever the reader chooses, costs a fraction of the attention.
There is a headcount effect too, and it is arithmetic rather than a vibe: eight people in a live standup cost eight times fifteen minutes plus the ramp in and out. Eight written check-ins cost their writers a few minutes each and their readers about two minutes each. The saving compounds across a week of mornings.
When the live meeting still wins
Async standups are the default, and four situations argue for keeping the call.
Blockers that need real-time back-and-forth come first. If the fix to "I'm blocked" is two people pairing for twenty minutes, the thread is just a slower way to arrange it. Take it straight to the call.
New teams should run live standups for their first weeks. The ritual teaches names, ownership, and what "done" means on this board. Once the habits exist, the board can carry the daily load.
Crisis weeks change everything. Launch week, an outage, a demo to a big client: the cost of one missed signal dwarfs the convenience of async, and a single standup call is cheap insurance.
And some teams simply run on the meeting: the standup is how a small crew starts the day together, and that is a legitimate answer. The honest test is whether the board or the meeting is the source of truth. If the answers people give in the meeting are already on the board by 9:00, the meeting has become a reading of yesterday and async will do it better.
The failure modes to watch
Async standups fail in recognizable ways, and all four are fixable.
Copy-paste theater. The check-in that says "continuing with my tasks" satisfies the ritual and informs nobody. The fix is cultural: write for the teammate who has to act on it, and ask the follow-up question out loud when a check-in is too vague to act on.
The silent blocker. Nobody enjoys typing "I'm stuck", so blockers go quiet and the board shows calm. The fix is standing instruction, given once by the lead: asking for help in a check-in is the normal case, and waiting silently until the work dies in a column is the abnormal one.
Read-nothing managers. When check-ins become wallpaper, writers stop trying. The fix is cheap: the lead replies in writing to at least one check-in a day, briefly. Questions in the thread are what keep a written ritual breathing.
A board that contradicts the check-in. The deadly one: the check-in says the deployment shipped while the card still sits in "In Progress". The fix is the order in the routine itself: cards move first, comments second. A check-in written against a stale board teaches everyone that the board is decoration.
What you need, and what you don't
The tooling requirement is small: a board your team actually maintains, comments on cards on cards, and mentions that name people. All the check-ins live in one stream, the project itself, so each one lands where people already read. Teams that want the wider story on board tooling can compare options in the small-teams guide, and remote-heavy setups will recognize their own constraints in the remote-team kanban piece.
What you do not need is anything that stands between the team and the habit. No standup bot asking the questions on a schedule. No digest emails summarizing what the board already says. No automatic meeting summaries, because the written check-in already did the summarizing. Every one of those buys back the interruption you were escaping and adds a step that decays into spam. The routine fits any kanban tool that keeps comments on cards. Taskora does it with streams, comments, and mentions, as the software-team board examples show. The feature tour walks the whole loop without a standup bot in sight.
Making the switch in two weeks
Run it as an experiment with an end date, and judge it on the board.
Week one, hybrid: keep the live standup on Monday, where the week's shape gets set with everybody present, and run written check-ins Tuesday through Friday. Announce the three-question template once. The lead reads everything and answers at least one thread a day in writing.
Week two, go fully async except a Monday call if the team wants it. The agile ceremonies guide shows where the standup sits among the other sprint meetings, and planning for a small team covers the sprint planning meeting. Measure two things. First, the time returned: five people skipping a fifteen-minute call four mornings a week is five hours of meeting time back, before counting ramp-in. Second, how fast blockers get answered: the time between "I'm stuck" appearing in a comment and the named person replying. If blockers surface faster than they did in the meeting era, the switch is working, whatever anyone feels about the missing call.
Then look at the board and ask the only question that matters: did the columns track reality more closely last week, or less? Written check-ins that sharpen a board are replacing the meeting successfully. Check-ins that coexist with a stale board are theater, and the fix is board discipline.
FAQ
What is an async standup?
A written daily check-in posted on the board instead of spoken in a meeting. Each person answers what they finished, what they are on, and what is blocked, as a comment on the card they are working on, and the team reads and replies on their own schedule. The board carries the status. The comment carries the intent and the blockers.
What do you write in an async standup?
Three short answers. One or two lines on what finished since the last check-in, naming cards. One line on the main card you are pushing until the next one. One line on blockers or risks, naming the person you are waiting on. Three to five sentences total, written against a board you just updated.
How long should an async standup take?
Under five minutes to write, and about two to read the whole team's check-ins. If yours takes longer than that, the board is drifting from reality and the comment is doing the board's job. Move the cards first, then the three questions get short.
When is a live standup still better?
When blockers need real-time back-and-forth, during a team's first weeks while habits form, and in crisis weeks like launches or outages where one missed signal is expensive. Many distributed teams settle on a hybrid: written check-ins daily plus one live call a week, often Monday, for the week's plan and the conversations threads cannot hold. Fully meeting-free suits experienced teams in quiet stretches, and the two-week experiment from this article is how you find out where your team sits. Let the board make the call.
Which tool runs async standups?
Any kanban board with comments on cards and mentions can carry one, because the check-in is a habit and the tool only hosts it. What matters is that comments stay on the cards where the reasoning lives and that the blocked person is named in a mention on the card. Taskora is built this way: every project is a stream with its own board. A board that people abandon by Wednesday cannot carry a written standup ritual no matter what features it lists.
Related posts
- Per User vs Flat Rate Task Management: What Grows the Bill
Per user vs flat rate task management pricing: how tiers, seat minimums, and add-on stacks grow a per-seat bill, and what one flat plan changes.
- AI Task Management Software: What It Actually Costs
What AI task management software actually does, the three ways vendors bill for it, and a five-question checklist before you pay.
- Kanban for Support Teams: Build the Board from the Ticket Lifecycle
Kanban for support teams: why sprint boards break, a support kanban board built from the ticket lifecycle, WIP caps per queue, and waiting made visible.