All Insights
guides· 8 min read

Remote Team Rituals That Actually Work

I've worked across multiple time zones for years. Here's what's worth keeping.

SV
Sri VardhanNovember 26, 2024
Share on Twitter
Share on LinkedIn
Copy link

Most remote-team advice is generic. After running engineering pods at a bank, a bank, and now my own clients across timezones, I have stronger opinions about what works.

Remote work is ergonomically harder than in-person. Most teams treat it like in-person with Zoom. That's the source of the problem.

What I've kept across teams

Async-first as default. If a question can be answered in writing, write it. Use Loom for things that need narration. Reserve sync time for genuinely sync work.

One quality sync per week. A team without any sync time turns into ships in the night. One real meeting where everyone is present, video on, agenda shared, pays for itself.

Weekly written updates. Every engineer writes a 3-bullet update once a week: what shipped, what's blocked, what they need. Read by team lead and other team members. This catches drift early.

Visible work. Linear / Jira / whatever, used consistently. The work needs to be visible without anyone asking. "What is X working on?" should be answerable from the tool, not from messaging X.

Real onboarding doc. Day-1 readiness is harder remote. I write a per-project onboarding doc with: how to get the dev env running, who to ping for what, where the docs are, the team's working hours.

What I've stopped doing

  • Daily standups for everyone. They're noise for most teams. Standups work for tightly coupled work; for most distributed teams, async updates are better.
  • All-hands video calls more than monthly. Death by Zoom is real. If it's not actively useful, kill it.
  • Slack as the source of truth. Information dies in Slack. Anything important goes in a doc.

What's hardest about remote

Building trust between engineers who haven't met. I budget for one team offsite per year. Real face time once a year is enough to make the rest of the year work.

Reading intent in writing. I now over-explicit. "I think X. I'm not pushing back, just sharing." Cuts down a lot of ambiguity.

Onboarding juniors. This is the hardest thing remote. I don't take on juniors at remote-only clients unless we can budget extensive 1-1 time.

A small ritual that works

Friday end-of-week, I run a 30-min "show and tell." Anyone who shipped something cool that week shows it. No agenda, no slides. Five-minute demos, max.

Started this at a client a year ago. Best thing I've added. Builds team identity. Ships more polished work because people know they might demo.

Tagged

#remote#team#leadership
SV

Sri Vardhan

Independent technology studio of one. I help founders and small teams ship serious software without the consultancy overhead. More about me.

Want to discuss this topic?

I am always happy to dig deeper. If a piece sparked an idea or a disagreement, send it over. I read every message myself.

Get in Touch