Running a Remote Team on Purpose
Published:
On an in-office team, a lot happens by accident: hallway conversations, overheard debugging sessions, lunch together, reading the room in a meeting. On a remote team, none of that happens unless someone designs for it. The by accident has to be done by intention. This document describes how I run a remote team: the principles behind it, how we communicate, how we run meetings, how we stay connected, and how we manage working hours and boundaries.
Principles
Culture is infrastructure. Remote culture and relationships are infrastructure, which are built on purpose. They don’t emerge on their own.
Know people as people. I want to know my teammates as people, and I want team members to know each other. Small talk about daily life matters: it’s how we understand what makes others tick. A jelled team is more effective (and more enjoyable!) than a collection of siloed workers, and actually knowing each other is a precursor to jelling.
Inclusion is a design problem. Especially in a remote environment, inclusion doesn’t happen by hoping people speak up. Participation has to be built into how we run meetings and processes. That means recognizing and working with differences in culture and communication style, and actively seeking input from everyone, especially the quieter voices who might not otherwise speak up.
Async-first. Remote teams, especially distributed ones, have to be async-first. We’ll have strategic synchronous touchpoints, but we always need to ask who is excluded by default meeting times and what we do about it. If some of the team is in a different time zone, we record meetings and collaborate in shared documents. Sync time is scarce, so when we are together, be present.
Rituals create identity. Culture on a remote team is built through consistent rituals: how we open and run standups, how we celebrate small wins, how we handle a production incident together. Over time, the rituals become the team’s shared story.
Communication
- Be responsive. Respond to Slack (email, etc.) in a timely manner. At minimum, react with a thumbs-up (or another emoji) to show you’ve read something. On a remote team, communication has to be intentional.
- Speak up. Body language doesn’t come across well on a Zoom call. Share your opinions out loud, unmute, and react to others. On a call, silence reads as absence.
- Be proactive. Let us know what you’re working on, any issues you’ve found, and what you need from others. Don’t wait to be asked.
- Flag when you step away. I don’t care if you’re going to the gym, picking up kids, or at a doctor’s appointment. What I don’t want is to wonder why you’ve gone quiet. A quick note in Slack is enough.
- Understand communication styles. I want to understand what motivates and demotivates each of you, how you like to be praised, and how you prefer to hear bad news. It’s easy to take something the wrong way when we’re not in person, so we have to be intentional about understanding each other’s styles and giving each other the benefit of the doubt.
- Use video messages. Sometimes a short video beats a long written message. For example, record a narrated Loom showing a weird bug you found and post it in a Slack channel.
- Use tools to bridge the gap. Use whatever makes remote and async work smoother: Slack, email, Zoom, Loom. Shared whiteboards (Miro, Lucid, etc.) and shared IDEs are great for brainstorming and reviewing together.
- Be authentic and respectful. Speak your mind and be yourself, while always showing respect for others.
Meetings
- Pre-reads. For design discussions and decisions, I’ll circulate a pre-read document ahead of time, and I’ll often ask you to come with a written opinion or mini-proposal. Everyone arrives with context and a view already formed, so the meeting becomes a discussion of prepared ideas rather than a contest of who can think and talk fastest.
- Separate generating ideas from evaluating them. Get everything on the table first, then critique. Early criticism shuts down quieter voices.
- Input after the meeting counts. Some people do their best thinking after the call. Follow-up comments in the doc or in Slack are welcome and carry equal weight.
- Standup is for coordination. We share daily written updates (what you did yesterday, what you’re doing today, any blockers) and hold a short live standup a few times a week. In the live standup, everyone gives a brief status and names anyone they want to stay back with. Anyone not needed can drop off, and the follow-up discussion happens with just the people involved.
- Rotating MC. Each week, a different team member leads standup.
- Cameras on for standup and small-group calls. Facial expressions carry information that Slack can’t. For demos and larger meetings where one person (or a few) is mainly talking, cameras off is fine.
- Protect flow state. I try to schedule meetings at the start or end of the day, or right after lunch, to leave large blocks of focus time.
- Deep Work Wednesday. One day a week is dedicated to focus work: no meetings, no Slack pings.
- Advance notice. I try to schedule meetings at least a day in advance so each day is predictable.
- Optional means optional. If you need to be at a meeting, I’ll invite you. You’re free to skip optional meetings, and to drop off one that turns out to be irrelevant to you.
Connection and Rituals
- Interaction beyond standup. Standup is a coordination tool, not a culture-building one. I deliberately create other touchpoints: pairing two or three people on a design, a debugging task, a shared presentation, or pair programming. Sometimes I pair people who don’t naturally work together. Collaboration builds trust faster than any team-building activity, and I (the manager) shouldn’t be the hub of every interaction.
- Shared wins and celebrations. I try to highlight small victories, shout-outs, and personal milestones.
- Virtual coffee breaks and happy hours. I host, and encourage others to host, low-pressure, non-work Zoom chats. For example, a Friday afternoon hangout with no agenda and a no-work-talk rule.
- Learning and fun. Do something educational or fun regularly. Teams I’ve been on have run ML reading groups, AI discussion groups, online games, show-and-tell, side-project demos, and vacation photo shares.
Working Hours and Boundaries
- Core overlap, flexible around it. Define your own working hours, as long as we all share several hours of overlap. Prefer to start early and finish early? Great. Start late and finish late? Also great. Let me (and the team) know your working style, and we’ll settle on our core collaboration hours together.
- 40 hours, arranged how you like. Appointments and errands during the day are fine. Flag them ahead of time and make sure the work gets done.
Know thyself: integrator or segmentor?
It helps to figure out whether you’re a work-life integrator or a work-life segmentor:
- Integrators blend work and personal life. They move fluidly between the two, don’t mind answering a message in the evening, and might hit the gym mid-afternoon.
- Segmentors need a clear line. They keep well-defined working hours, and once they’re done for the day, they’re done.
(Atlassian has a good write-up on the distinction.)
Neither is better; it’s about your personal preferences and boundaries. I’m an integrator, and I’ve had teammates who are segmentors. Knowing which you are helps your teammates understand how to work with you, and it tells me that a message from me after hours is never a request to answer after hours.
Whichever you are, daily startup and shutdown rituals help:
- Fake commute. Take a walk before and after work to mark the transition between work and personal time.
- Startup habit. Write down your top-priority task before you do anything else.
- Shutdown habit. Turn off notifications, close the laptop, and tidy your workspace.
Closing Thoughts
Remote doesn’t have to be worse than in-office. Done deliberately, it can be better. At Yelp, about 90% of employees said they had found effective ways to collaborate remotely, and 89% said they could manage personal and professional demands (Fortune, 2024). None of that happens by accident. It takes the intentional habits above, and it takes all of us.