I ran two teams in the Meta London office before 2020 and two remote-first teams at Amazon afterwards. The jobs were recognisably the same job but they were different enough that almost every habit I had built in the office turned out to be wrong in a remote context. Here is what I changed.

1. Write more; talk less

In an office, a lot of alignment happens by accident. Two engineers bump into each other at the coffee machine, a decision gets made, and the team absorbs the change by osmosis within twenty-four hours. Remote teams do not have a coffee machine. If you rely on osmosis you will get drift.

The correction is uncomfortable at first: almost every decision that used to be a verbal "I've decided X" has to become a written "I've decided X, here's why, please push back by Friday if you disagree". It feels slower. It is not slower in aggregate, because the cost of undoing a drifted team is much higher than the cost of writing the paragraph.

2. Ruthlessly reduce synchronous meetings

Every meeting is more expensive in a remote-first team — it costs the full focus of everyone on it, plus the cognitive overhead of context-switching on and off video, plus the timezone tax if anyone is not on UK time.

I now hold only three standing meetings: a weekly team meeting (30 min), a weekly one-to-one with each report (30 min), and a fortnightly technical review (60 min). Everything else is either async, or a short ad-hoc call booked the same day.

3. Keep one-to-ones; shorten them; hold them sacred

The single most important thirty minutes of my week. More important in remote than in office, because the alternative — "grabbing a coffee" — doesn't exist. I have never regretted doing a one-to-one; I have repeatedly regretted cancelling one.

A useful rule: the one-to-one is the report's meeting, not mine. I come with one thing I want to cover. They come with as much as they like. If they have nothing, we end early.

4. Over-communicate what you're working on

Remote teams lose the ambient signal of "I can see that person typing, therefore they are doing work". You replace it by making your work visible without making people feel surveilled.

I ask the team to post a two-line message in a team channel at the start and end of each day. Not a standup; a quick "here's what I'm picking up today / here's what I got done". This one habit has done more for team cohesion than anything else I've tried.

5. Make the unwritten rules written

In an office, you can observe how the senior engineers behave and absorb the norms. Remotely you can't. You have to write the norms down. How long should a PR take to get reviewed? What's the expected response time on a tagged message? When is it OK to book an unscheduled call?

Having a team handbook — even a rough one — prevents a new hire from spending their first three months guessing, and prevents an existing member from quietly diverging over time.

6. Travel matters more, not less

This one is counterintuitive. Remote-first teams I've worked on have all benefited enormously from two or three in-person weeks a year, held deliberately. The teams that skip them are the ones where people start to feel like avatars rather than colleagues.

I'm not talking about elaborate off-sites. A rented flat somewhere central, a week of working in the same room, a long dinner. The cost is small against the operating benefit of the rest of the year.

7. Hire for written communication explicitly

An engineer who codes beautifully but cannot write a short, clear Slack message is, in a remote context, not a high-performance hire. I now ask every candidate to write a design document as part of the loop and I weight it as heavily as the coding round.

This is not a bar you should raise with existing team members — you hired them under different rules. It's a bar for new people, so the team's communication norms don't degrade as it grows.

8. Respect the clock

The risk with a remote-first team is that work bleeds into the whole day. The evening messages, the weekend emails, the 8 p.m. meetings because "the other team is in US time zones".

I now hold a fairly strict rule: no work messages sent to the team between 7 p.m. and 9 a.m. UK time, weekdays, except genuine incident response. If you have to write something at 11 p.m., schedule the send for the morning. The habit matters more than the policy — it signals that this is a job, not a lifestyle.

None of this is novel. It's just that, three years into remote-first being the norm, I still see teams run by managers applying office habits to a remote team and wondering why they're struggling. The habits are not portable. You have to replace them deliberately.

— Nivaan