Remote work is no longer the exception. For many product teams, it’s the default.

Now imagine this team distribution:

• Design in Europe

• Backend in Asia and Australia

• Growth in Africa

• Front-end in South America

• Stakeholders in Europe

A reasonable question follows:

What happens when each team member works from a remote location (and a different time zone)?

How do you sync up?

The immediate idea most teams land on is:

“Let’s find overlap hours and do a daily standup.”

That works when time zones are close and calendars are flexible.

But once the team spreads across continents, overlap becomes painful:

• someone joins too early or too late

• people attend half-asleep

• the meeting becomes a status ritual

• real work gets pushed to “after the call”

And slowly the daily standup becomes the thing that remote teams suffer through—not the thing that helps them deliver.

Why Daily Standup Often Fails in Multi-Time-Zone Teams

In a global remote setup, standup becomes waste for two common reasons:

1) It tells you what you already know

If your work is visible in a board (Jira/Linear/GitHub), the standup repeats it.

2) Or it produces “let’s take it offline”

If something is important, the standup ends with a separate conversation anyway.
So the meeting becomes a daily funnel into more meetings.

There’s another reason it becomes less useful over time:

3) Pairing and “baton passing” reduce the need for status broadcasting

In mature teams, people collaborate closely (pairing / quick reviews / shared work).
The real work is already being discussed while it happens.

So the standup becomes a late report of a conversation that already occurred.

This Is Where “No-Standup” Emerged at Squads

Back in 2014, we started experimenting with an idea that felt odd at the time:

What if we remove the daily standup completely… and replace it with better coordination mechanisms?

Not “no communication.”
Not “everyone does their own thing.”

But a system that works even when people never overlap live.

This is how it works.

So How Does No-Standup Work in a Completely Remote Team?

Instead of one daily meeting, we replace it with three lightweight coordination habits:

1) Check-In and Check-Out (Async, not a meeting)

When you “enter” your work window, you post a simple check-in.

Sample Check-In (start of your day):

• I’m checking in. I am ready to get to the work.

Someone already working asks for pairing up. If not, you:

• pick a task and start working

• explain, what exactly are you going to do

• wait for another pair.

Sample Check-Out (end of your day):

• What I finished: <PR/link/result>

• What changed / decision taken: <1–2 lines>

• Next step for whoever picks this up: <clear baton pass>

• Blockers / risks: <if any>

This does two things:

• everyone knows you’re active without calling people into a meeting

• work stays trackable even across time zones

2) Asynchronous Handover (The Baton Pass)

Information exchange happens through deliberate handover using group chat.

The principle is simple:

If you learned something that another person will need tomorrow, leave it behind today.

Examples:

• short message summary in one thread

• a Loom walkthrough for context

• a quick note: “I tried X, it failed because Y, next attempt should be Z”

This prevents the classic remote failure mode:

“Can you jump on a call to explain what happened?”

3) Weekly Feedback Cycles Instead of Daily Reporting

A fair question:

Daily Scrum helps assess sprint progress daily. How does that work without it?

Answer: Mature remote teams have short (weekly) sprints. So even if you slip, slippage is not that much as feedback cycle is very short.

Conclusion

#No-Standup isn’t a rebellion against Agile. It’s a practical response to a global reality: when teams are spread across time zones, synchronization becomes expensive and often pointless.

Daily standups try to create alignment through a meeting.

Mature remote teams create alignment through:

• visible work,

• disciplined check-ins/check-outs,

• intentional handovers,

• and short weekly feedback loops.

If your team is truly distributed, the question is not “How do we schedule overlap?”
It’s “How do we keep progress flowing even when we don’t overlap?”

That’s what #No-Standup is really about.