
🧞♂️ New to Exponential Scale? Each week, I provide tools, tips, and tricks for tiny teams with big ambitions that want to scale big. For more: Exponential Scale Podcast | Scalebrate | Scalebrate Hub
Founding Supporters: Support the following people and companies because they supported us from the beginning: DataEI | Dr. Bob Schatz | .Tech Domains | Fairman Studios | Jean-Philippe Martin | RocketSmart AI | UMBC
In today's newsletter:
Latest Podcasts: What You Missed
What Can You Learn from 22 Microteam Success Stories? (…Plus 1) - Real microteams, real results, and the repeatable patterns behind outsized growth with tiny teams… and one notable failure.
Interview with Wade Foster, CEO of Zapier - How Zapier scaled with leverage, automation, and focus instead of hiring and organizational bloat.
Interview with Fabian Veit, CEO of Make - How advanced automation helps microteams remove busywork and scale faster without added headcount.
Async Standup Protocol: Status Without Sync Meetings
Every morning at 9am, your team drops everything for a "quick" 15-minute standup.
Except it's never 15 minutes. Someone rambles. Questions derail the agenda. By 9:35, you're finally back to actual work—but your flow is broken.
Multiply that by 5 days a week, and you've burned 2.5+ hours in status meetings. Hours you could've spent shipping product, closing deals, or solving real problems.
Meanwhile, your async-first competitor has zero standups. Their team posts updates in Slack, reads them when convenient, and stays in flow all morning.
Daily standups aren't bad. Synchronous daily standups are.
The Team That Quit Standup (And Got Faster)
Let me tell you about Maya, founder of a remote 6-person dev shop building SaaS products.
Maya's team did daily standups at 9am PST. Standard practice, right?
The problem? Her team was spread across 3 time zones. For the East Coast developer, 9am PST was noon, right in the middle of his most productive hours. For the London contractor, it was 5pm… end of day.
Everyone showed up. But nobody was happy.
One week, Maya's internet died. She couldn't host the standup. So she asked the team to post updates in Slack instead.
What happened?
Updates were clearer (people wrote thoughtfully instead of speaking off the cuff)
No interruptions (everyone read updates when convenient)
Faster (reading 6 updates took 3 minutes vs. 25-minute meetings)
Better async collaboration (people replied with help/suggestions in threads)
When Maya's internet came back, the team voted: "Let's keep the async format."
Result: 2 hours/week saved per person = 12 hours/week total for the team. Zero loss in alignment.
"We realized the standup wasn't about synchronous discussion. It was about visibility. And async gave us better visibility with zero coordination tax."
Why Sync Standups Are Broken
Traditional standups fail because they prioritize presence over productivity.
The theory:
Quick sync to align the team
15 minutes, no deep dives
Everyone knows what everyone's working on
The reality:
25+ minutes because people ramble or ask tangential questions
Interrupts flow (especially for makers)
Same info could've been shared in writing in 2 minutes
Time zone pain for remote teams
People zone out if the update isn't relevant to them
Think of sync standups like forcing everyone to gather in the town square to hear announcements.
Async standups are like posting the announcements on a bulletin board where people read them when it makes sense.
Same information. Zero coordination overhead.
The Async Standup Framework
Here's how to replace daily sync standups with async updates:
Step 1: Choose Your Async Tool
Option A: Slack/Teams
Create a dedicated #standup or #daily-updates channel
Pin a message with the update template
Team posts updates every morning
Option B: Dedicated Tools
Geekbot (Slack bot that prompts team for updates)
Status Hero (async standup + reporting)
Range (async check-ins with team mood tracking)
Option C: Notion/Google Doc
Create a shared doc with daily sections
Team adds their update under today's date
Recommendation: Start with Slack. It's where your team already is.
Step 2: Define the Update Template
Keep it simple and consistent.
Standard Async Standup Template:
**Yesterday**: [What I completed]
**Today**: [What I'm working on]
**Blockers**: [What's blocking me, if anything]
**Needs**: [What I need from teammates, if anything]
Example:
**Yesterday**: Shipped the user dashboard redesign, fixed 3 bugs from QA
**Today**: Starting API integration for payment flow
**Blockers**: None
**Needs**: @Sarah, can you review the dashboard PR when you have 10 min?
Short. Specific. Actionable.
Step 3: Set Clear Expectations
When to post: By 10am (or start of workday) in your local timezone
How long it should take: 2-3 minutes to write
Who reads it: Everyone scans the channel once daily (typically mid-morning)
Response expectations:
React with ✅ if you read it
Reply in thread if you have help/feedback
No need to reply to every update
Step 4: Replace the Sync Meeting
Send a message to the team:
"Starting Monday, we're moving to async standups. Here's how it works:
- Post your update in #daily-updates by 10am using this template: [link]
- Read everyone's updates once a day (takes ~5 minutes)
- Reply in threads if you can help with blockers
- We'll keep our weekly sync for deeper discussions, but daily standups are now async."
Step 5: Monitor and Iterate
Week 1: People might forget or write too much. Gently remind them.
Week 2: If someone consistently skips updates, DM them: "Hey, saw you missed a few standups—everything okay?"
Week 4: Check in with the team: "How's async standup working? Any tweaks needed?"
Most teams never go back to sync standups once they experience the freedom.
Advanced Async Standup Tactics
Tactic #1: Use Automation to Prompt Updates
Geekbot or Standuply (Slack bots) can automatically DM team members at 9am asking for their update.
They type it in DM, bot posts it to the channel.
Benefit: People don't forget. Updates happen automatically.
Tactic #2: Add Weekly Themes
Every Friday, add a reflection question:
Monday: No extra question (ease into the week)
Wednesday: "What's one thing blocking progress this week?"
Friday: "What's one win from this week?"
Keeps updates from feeling robotic.
Tactic #3: Link Updates to Task Management
If you use Linear, Jira, or Asana, have team members link their tasks in the update.
Example:
**Today**: Working on [LIN-432](link)
This creates traceability without extra work.
Tactic #4: Time-Box Reading Updates
Don't let reading updates become a 30-minute scroll.
Rule: Spend max 5 minutes reading the channel once a day (mid-morning).
If something needs deeper discussion, move it to a thread or schedule a focused call.
Scenario #1: Team Needs Real-Time Collaboration
When Async Standups Don't Work (And What to Do)
If your team is pairing daily or needs live problem-solving, async standups might feel disconnected.
Solution: Keep async standups for visibility, but add a weekly sync for collaboration and planning.
Scenario #2: People Stop Posting Updates
If updates drop off after a few weeks, the format might be too boring or people don't see the value.
Solution:
Make updates shorter (just "Today" and "Blockers")
Celebrate wins publicly (react with 🎉 to good updates)
Lead by example (founder posts first every day)
Scenario #3: Updates Become Novels
Some people write 10-sentence essays for every update.
Solution: Set a word limit (50 words max) or bullet-point format only.
Async Standup Comparison
Sync Standup | Async Standup | |
|---|---|---|
Time cost | 15-25 min/day | 2-3 min to write, 5 min to read |
Interruption | High (breaks flow) | Low (read when convenient) |
Remote-friendly | Hard (time zones) | Easy (post anytime) |
Clarity | Varies (people ramble) | High (written is clearer) |
Searchable | No (unless recorded) | Yes (Slack history) |
Scalability | Hard (10+ people = 45+ min) | Easy (read time stays ~5 min) |
Async wins on every dimension except one: real-time problem-solving.
If you need that, schedule focused problem-solving calls—don't disguise them as standups.
Real Team Examples
Example 1: 8-Person SaaS Startup
Before: Daily 9am video standup (30 minutes) After: Async updates in Slack by 10am Time saved: 25 min/day × 5 days × 8 people = 16.6 hours/week Team feedback: "I can finally start my day in flow instead of waiting for a meeting."
Example 2: Remote Design Agency (12 people, 5 time zones)
Before: 2 sync standups (Americas + Europe) = 1 hour total daily After: One async Slack channel everyone posts to Time saved: 5 hours/week Team feedback: "We actually read updates more carefully now because we're not half-listening in a Zoom call."
Example 3: 3-Person Founding Team
Before: No formal standups (just ad-hoc Slack chatter) After: Daily async updates using Geekbot Result: Better visibility without adding meetings Team feedback: "We didn't think we needed standups. Turns out async updates help us stay aligned without the meeting overhead."
Today's 10-Minute Action Plan
You don't need to overhaul your standup process today. Just test async for one week.
Here's what you can do in 10 minutes:
Create a #daily-updates channel in Slack
Pin the update template (Yesterday/Today/Blockers/Needs)
Send a message to the team: "Let's try async standups this week. Post by 10am daily."
Lead by example: Post your update first thing tomorrow
Set a Friday retro: "How did async standups feel? Keep or revert?"
That's it. One week experiment.
90% of teams who try it never go back to sync standups.
A Final Thought
Standups exist for a good reason: visibility and alignment.
But synchronous standups are a relic of co-located, single-timezone teams.
In 2025, most teams are remote, distributed, or hybrid.
Async standups give you the benefits (visibility) without the costs (coordination overhead, flow interruption, time zone pain).
You don't lose alignment. You gain focus.
Try it for a week. See how much time you get back.
Then ask yourself: "Why were we doing sync standups in the first place?"
But what can you actually DO about the proclaimed ‘AI bubble’? Billionaires know an alternative…
Sure, if you held your stocks since the dotcom bubble, you would’ve been up—eventually. But three years after the dot-com bust the S&P 500 was still far down from its peak. So, how else can you invest when almost every market is tied to stocks?
Lo and behold, billionaires have an alternative way to diversify: allocate to a physical asset class that outpaced the S&P by 15% from 1995 to 2025, with almost no correlation to equities. It’s part of a massive global market, long leveraged by the ultra-wealthy (Bezos, Gates, Rockefellers etc).
Contemporary and post-war art.
Masterworks lets you invest in multimillion-dollar artworks featuring legends like Banksy, Basquiat, and Picasso—without needing millions. Over 70,000 members have together invested more than $1.2 billion across over 500 artworks. So far, 25 sales have delivered net annualized returns like 14.6%, 17.6%, and 17.8%.*
Want access?
Investing involves risk. Past performance not indicative of future returns. Reg A disclosures at masterworks.com/cd
Refer Folks, Get Free Access
What This Is
A complete async standup implementation toolkit with ready-to-copy templates, automation setup guides, team rollout plans, and troubleshooting playbooks. Everything you need to eliminate daily sync meetings and reclaim 10+ hours per week for your team while maintaining (or improving) alignment.
Why You Need This
Synchronous daily standups are a coordination tax that kills flow, fragments schedules, and punishes distributed teams across time zones. But simply canceling standups without a replacement creates chaos. This toolkit gives you a proven async alternative—complete with templates, automation, and change management—so you can eliminate sync overhead while keeping visibility and alignment.
Subscribe to our premium content to read the rest.
Become a paying subscriber to get access to this post and other subscriber-only content.
Upgrade