Cut Your Daily Standup With a Two-Week Digest Test

The standup is paying for status, not decisions

Your calendar shows the standup again: same time, same people, same status round. The recurring invite is a block of time that nobody reviews, and the cost is that block, multiplied by every person in the room.

Most of the meeting is status: what happened yesterday, what happens today, what is blocked. A 2025 Atlassian State of Teams survey covering 12,000 knowledge workers showed that top-performing groups treat meetings as decision-making time instead of status reporting. When the standup is mostly status, the digest should carry that part.

Run the two-week digest test before you cancel the invite

You do not cancel the standup first. Replace the reporting layer, then let the meeting shrink to the work that still needs a human. The test gives you a reason to change the invite without making it a personal call.

Put the digest where the team already looks: a team chat channel if the team lives there, or a project page if the team lives in the tracker. Keep it short enough to read without hunting, and make it name the blocker, not just the ticket.

• Baseline the meeting. Keep the standup unchanged for the first stretch. After each session, note how many minutes go to status, blockers, and decisions. Done looks like a short daily tally that shows whether the meeting is mostly reporting.
• Turn on the digest. Replace the status portion with an automated update. For teams on Jira, the Delivery Agent is a built-in AI agent powered by Rovo that reads work items and produces audience-specific updates. The Daily Standup automation scans the board and posts a daily status update to Confluence or Slack. You are done when a posted update says what moved, what is blocked, and what needs attention.
• Shrink the sync to decisions. Keep the meeting only for blockers that need a human choice and decisions that need a room. When the digest already answers a question, do not ask it aloud. The result is a shorter invite that says decisions and blockers only.
• Review the test. Compare the baseline tally with the new meeting. Once status talk is gone and decisions are faster, shrink the cadence or cancel the recurring invite. Finish when the calendar no longer reserves time for reporting.

The usual mistake is to send the digest and keep the same meeting. The standup still spends most of its time on status, and the digest becomes another place to report.

Before you announce the change, check that the team has Confluence and Rovo access for the Summary-view Delivery Agent automations, and a Slack App Bot or Webhook if the digest goes to Slack.

Keep the meeting for the part only humans do

A digest can carry the routine: what moved, what is blocked, and what is on track. Leave the meeting for the parts that need judgment: a tradeoff, a priority call, a blocker that needs a decision, a conflict that needs a name.

For distributed teams, Asana's async standup setup lets each member add a daily update as a task or comment in a shared Asana project on their own schedule. That keeps the reporting out of the meeting and leaves the sync for the questions that actually need a room.

Do not let the sync become a digest review. Spending the opening minutes reading the update aloud moves the ritual instead of removing it. Let people read the digest before the sync, then start with the first decision.

Rewrite the invite before the test starts. The title should say what the meeting is for, not what it used to be. Daily standup invites status. Decision sync invites a choice. Make the test visible to the team. Tell them you are testing a digest, not blaming the meeting.

When the test is done, update the invite to the new decision sync or cancel the recurring invite, and tell the team where the digest lives.