A twenty-person AI agency in Toronto ran daily standups for all three of their delivery teams. Each standup was scheduled for fifteen minutes but routinely ran to thirty. With three teams, that was ninety minutes of collective standup time per day, or seven and a half hours per week. The agency's senior ML engineer calculated that standups were consuming roughly four percent of the agency's total available engineering hours.
The engineer was not upset about the time itself. She was upset about what the standups accomplished with that time, which was almost nothing. The format was the standard "what I did yesterday, what I am doing today, any blockers" rotation. Most updates were perfunctory. Blockers were mentioned but rarely resolved during the call. People who were not speaking scrolled their phones. And because the standup was at 10 AM, it fragmented the morning focus time that engineers relied on for deep work.
After the engineer raised this with the operations lead, the agency redesigned their standup process. One team switched to asynchronous standups. Another kept synchronous standups but shortened them to ten minutes with a different structure. The third team experimented with twice-weekly syncs instead of daily.
All three teams reported better outcomes. The async team appreciated the recovered focus time. The shortened-standup team found the new format more actionable. The twice-weekly team discovered that they did not actually need daily alignment.
Standups are not sacred. They are a tool. And like any tool, they should be optimized for the job they need to do.
Why Standard Standups Fail in Agency Environments
The daily standup originated in co-located agile teams working on a single product. That context is fundamentally different from a distributed AI agency where multiple teams work on multiple client projects across multiple time zones.
Time zone sprawl makes synchronous standups impractical. If your team spans Pacific and Eastern time, a 10 AM standup for one person is a 1 PM standup for another. Add a European team member and there is no time that works for everyone without someone sacrificing their focus hours.
Multi-project context makes updates irrelevant to most listeners. In a product team, everyone works on the same codebase. Every update is potentially relevant to every participant. In an agency team where three people are on Client A and two people are on Client B, the Client B updates are noise for the Client A engineers.
AI work does not change meaningfully every day. "Yesterday I continued training the model. Today I will continue training the model. No blockers." This update conveys no information. AI work often involves multi-day tasks (data cleaning, training runs, evaluation cycles) where daily status updates are repetitive.
Standups compress into the wrong part of the day. Morning standups break up the first block of focus time. Afternoon standups break up the second. Either way, the standup creates a context switch that costs more productivity than the update provides.
Determining What Your Standups Actually Need to Accomplish
Before redesigning your standup, clarify what it needs to achieve. Most standups try to serve multiple purposes with a single format, and they serve none of them well.
Purpose One: Surface blockers. The most valuable function of a standup is identifying when someone is stuck and needs help. Everything else is secondary.
Purpose Two: Maintain team awareness. People need a general sense of what their teammates are working on so they can coordinate, offer help, or avoid conflicts.
Purpose Three: Create accountability. The social commitment of stating your plan to the team creates a mild accountability pressure that keeps work moving.
Purpose Four: Build team connection. Especially in distributed teams, the standup is sometimes the only daily touchpoint where the team interacts as a group.
Each purpose can be served by different mechanisms. Not all of them require a synchronous meeting.
The Asynchronous Standup Model
For many distributed agency teams, async standups deliver better results than synchronous ones.
How it works:
Each team member posts a daily update in a dedicated Slack channel (or equivalent) by a set time. The update follows a structured format.
Recommended async standup format:
- Focus today: What is the main thing you will work on? (One sentence)
- Blockers: Anything preventing progress? Tag the person who can help. (One sentence or "None")
- Flag: Anything the team should know? (Optional, one sentence)
That is it. Three lines or fewer. The entire update takes under two minutes to write.
Why async standups work well for agency teams:
- Time zone friendly. Each person posts when their workday starts. No scheduling conflicts.
- Respectful of focus time. No meeting to attend, no context switch. People post when they have a natural break.
- Scannable. A team lead can review all updates in under two minutes. In a synchronous standup, the same information takes fifteen minutes because of the overhead of speaking turns and social filler.
- Searchable. Async updates create a record. If someone asks "what were you working on last Tuesday?" the answer is in the channel history.
- Blocker-focused. The format highlights blockers prominently, making them easy to spot and address quickly.
Common objection: "People will not post consistently."
This is true if there is no follow-through. The team lead should check daily that everyone has posted. A gentle reminder for missed posts is sufficient. If someone consistently does not post, address it directly. The habit forms within two to three weeks for most teams.
Common objection: "We lose the human connection."
Valid concern. Supplement async standups with a weekly or biweekly synchronous team call that is explicitly for connection, discussion, and problem-solving, not status updates. This gives the team face time without the daily overhead.
The Optimized Synchronous Standup
Some teams prefer or need the synchronous format. If you keep it, optimize it.
Keep it under ten minutes. Fifteen minutes is the standard recommendation. For most agency teams, ten is achievable and forces discipline.
Change the format from "what I did" to "what needs attention."
Instead of the traditional rotation, use a focus-based format:
- Blockers first. Anyone with a blocker speaks first. The team immediately discusses resolution. If it cannot be resolved in two minutes, schedule a follow-up.
- Decisions needed. Any decisions that require team input. Quick discussion, decision made, move on.
- Flags. Anything the team should be aware of: client feedback, deadline changes, dependencies.
- Skip "what I did yesterday." This information is in the task tracker. If someone wants to know, they can look. The standup should not be a recitation of what the tool already shows.
Do not go around the room. The round-robin format is the primary reason standups run long. Instead, let anyone with something to share speak up. If nobody has anything, the standup is over in two minutes. That is a success, not a failure.
Schedule it at a transition point, not in the middle of a focus block. Right before lunch or right at end of day works better than mid-morning. The standup becomes a natural boundary between focus blocks rather than an interruption.
Keep cameras on but do not require standing. The "standing" in standup was designed to create discomfort that encourages brevity. In a distributed team, that does not translate. Cameras on maintains the human element. Requiring people to stand at their desk is performative.
The Twice-Weekly Sync Model
For mature teams with good async communication habits, daily standups may be unnecessary. A twice-weekly synchronous check-in (Monday and Thursday, or Tuesday and Friday) provides enough touchpoints without the daily overhead.
Monday sync: Set priorities for the week. Identify dependencies and potential blockers. Align on what each person is focusing on.
Thursday sync: Mid-week check on progress. Surface any blockers or changes. Adjust plans for the remainder of the week.
Between syncs, the team uses async updates and direct messaging for coordination. Urgent blockers are raised immediately in the team channel, not held until the next sync.
This model works best when:
- The team has strong self-management habits
- The project is in a steady execution phase (not early discovery or crisis mode)
- Most work is independent and does not require daily coordination
- The team has a shared task board that is actively maintained
This model works poorly when:
- The team includes junior members who need more regular guidance
- The project is in a rapid iteration or debugging phase with frequent changes
- Multiple team members are working on tightly coupled components
- There is significant client communication requiring daily alignment
Standup Anti-Patterns to Eliminate
The status report standup. Every person gives a comprehensive update of everything they did. This is a meeting, not a standup. Push detailed status to async channels or the task board.
The problem-solving standup. A blocker is raised and the entire team spends ten minutes debugging it while everyone else waits. Rule: if a problem cannot be resolved in two minutes, take it offline with the relevant people after the standup ends.
The audience standup. Three people do all the talking and seven people listen silently. If most participants are spectators, either the team is too large for a single standup (split by project or sub-team) or the format is not encouraging participation.
The status-quo standup. The standup has run the same way for two years and nobody questions whether it is still serving the team. Review your standup format every quarter. Ask the team: is this meeting helping you? What would you change?
The guilt standup. People feel pressured to report "impressive" work. This leads to inflated updates and discourages honest sharing of struggles. The standup should be a safe space to say "I am stuck" without judgment.
Standups Across Multiple Client Projects
If your agency has engineers working on multiple client projects simultaneously, your standup structure needs to account for that.
Option One: Team-based standups. The standup is organized by delivery team, and each person updates on all their projects. This works when the team is small (four to six people) and projects do not overlap much.
Option Two: Project-based standups. Separate standups for each client project. People attend the standups for their active projects. This works when projects have dedicated teams, but it can mean someone attends two or three standups per day, which defeats the efficiency goal.
Option Three: Hub-and-spoke. One daily standup per team (async or short synchronous) for general updates, plus project-specific syncs as needed (weekly or ad hoc). This balances team cohesion with project-specific coordination.
For most agencies, the hub-and-spoke model works best. The team standup maintains connection and surfaces blockers. Project-specific coordination happens separately and only as frequently as the project demands.
Measuring Standup Effectiveness
Track these indicators to assess whether your standups are working.
- Standup duration versus target. If your target is ten minutes and standups consistently run twenty, the format needs adjustment.
- Blocker resolution speed. When blockers are raised in standup, how quickly are they resolved? If blockers sit for days after being raised, the standup is surfacing problems but not driving solutions.
- Team satisfaction with the format. Ask quarterly: is the standup useful? Would you prefer a different format or frequency? Take the feedback seriously.
- Attendance and participation. If people are regularly skipping or disengaging, the standup is not providing enough value to justify the interruption.
- Engineering focus time. Are engineers getting at least three to four hours of uninterrupted focus time per day? If not, meeting load (including standups) may be a contributing factor.
Your Next Step
Audit your current standups this week. Time them. Note how much of the content is genuinely useful versus routine recitation. Ask each team member privately whether they find the standup valuable and what they would change.
Then try one change for two weeks:
- If your standups run long, switch to the "blockers, decisions, flags" format and enforce a ten-minute cap.
- If your team is distributed across time zones, try async standups for two weeks and measure the impact on focus time and blocker resolution.
- If your team is mature and self-directed, try twice-weekly syncs and see whether daily standups were providing value you actually miss.
The goal is not to eliminate standups. The goal is to make every minute of team alignment time count. The best standup is the one that takes the least time while still keeping the team connected, unblocked, and moving forward.