If you're an EM who was promoted on a co-located team and now manages across timezones, the playbook you used does not translate. Real-time visibility, hallway calibration, and instant 1:1 escalation all break. The replacement isn't more meetings — it's a smaller number of high-quality written artifacts and a discipline about overlap hours.
Default to writing, not speaking
The single biggest mindset shift: you communicate by writing, with calls as exceptions. Co-located managers do the inverse. The reason is mechanical — speaking only reaches the people in the room, and your team isn't in any one room.
Every important thing you'd want to say in a meeting, write down first. Share. Hold the meeting only for the things writing didn't resolve.
Build the manager artifact set
You need four documents kept current:
- Team direction — what we're working on this quarter, why, and what we're not.
- Surface ownership map — who owns what, with backup.
- Decision authority map — who decides what, especially with deputies for each timezone.
- Weekly digest — what shipped, what's blocked, what's coming. Replaces most status meetings.
If these four are current and accessible, you can manage 20+ engineers across zones without burning out.
Use overlap hours for the things that need them
Overlap with each timezone is a scarce resource. Spend it on: hard conversations, conflict resolution, growth conversations, urgent decisions. Don't spend it on status, demos, or anything that could happen async.
If your 1:1s land in overlap, make them about people, not project status. Push project status into the team digest.
Run 1:1s with two-mode structure
Distributed 1:1s should rotate between two modes: project mode (every other week, 25 min, what's blocked and what does this person need) and growth mode (every other week, 45 min, what are they learning and where are they heading).
Single-mode 1:1s tend to drift into project status and starve growth.
Visibility without surveillance
The mistake some EMs make distributed: trying to recreate co-located visibility through monitoring. Online status. Activity tracking. Daily standups that turn into status interrogation.
The alternative: declared state. Engineers write wraps. You read them. Visibility comes from the artifact, not from watching. This is faster, less corrosive, and produces better information.
Manage on Declared State
StandIn replaces status meetings and DM checks with structured wraps and decision records — so managing scales across zones.
See the Workflow →Distribute authority before you have to
If you're the bottleneck for decisions, your team will stall during your off-hours. Map authority explicitly: who can decide what, in each zone. The first time you take vacation, you'll see whether the map works.
Build the map when you don't need it. You won't have time when you do.
Manage your own time visibly
Block focus time. Use status indicators. Don't model 24-hour availability — your team will copy the model. If you reply at 11pm, they'll feel like they should too. Lead the boundaries you want them to keep.
Common failure modes
Failure: hiring a remote-ish team but managing co-located. Office-default norms applied to a distributed team produce slow attrition. Either go distributed-default or get back to one location.
Failure: too many 1:1s, too few artifacts. 12 hours a week of 1:1s and no written team digest is a recipe for an exhausted EM and a team that still feels uninformed. Invert.
Failure: privileging your timezone. If every meeting and decision aligns to your hours, your team's other-zone engineers will quietly leave. Rotate meeting times; default to async where possible.
What to do tomorrow
Pick the manager artifact set above. Audit which of the four documents are current. Pick the most stale and refresh it this week. Repeat next week. Within a month, you have the foundation for distributed management that doesn't depend on you being awake.
Frequently asked questions
How do I keep team culture strong across timezones?
Through writing and shared rituals — not through forced social calls. Engineers feel cultural belonging when their work is seen, their contributions matter, and the team's decisions are findable. Optional social time supports this; it doesn't substitute for it.
Should I require cameras on for distributed calls?
No. Cameras are useful for hard conversations and conflict, not for status. Mandating cameras for every call produces fatigue without proportional benefit.
How big can a single distributed EM's team get?
8-10 direct reports works. 12 is stretched. 15 is too many — the EM becomes a routing layer instead of a manager. Add senior ICs or a layer if you cross that line.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.