I started managing remote engineers in 2019, right before the world made everyone do it. Thought I had a head turn. I didn't. My first distributed team had six people across four time zones, and within two months I'd burned out two senior devs without realizing it. The problem wasn't the work. It was that I kept defaulting to how I managed co-located teams, and remote work punishes that approach fast.
The biggest shift was learning to write things down. Not Slack messages that disappear into scroll. Actual documents. Decisions, context, rationale, trade-offs. When your team spans from Berlin to Austin, someone is always asleep when a conversation happens. If it isn't written down, it didn't happen. I started requiring that every technical decision get a one-page write-up in our shared repo. Engineers hated it for about two weeks. Then they stopped asking me to repeat context in every standup.
Async communication became the default, not the fallback. I killed most recurring meetings. Our daily standup became a Slack thread where people posted updates by 10am their time. Weekly one-on-ones stayed, but I moved them to 30 minutes instead of 60. Shorter meetings force clarity. You learn to say what matters when the clock is tight.
Trust was the hardest part. Early on, I made the mistake of tracking activity instead of output. I'd check commit timestamps, Slack green dots, Jira ticket velocity. Felt like management. Was actually surveillance. One engineer called me out directly: "You're measuring presence, not progress." She was right. I stopped looking at when people worked and started caring about what they shipped and how they communicated blockers. Team output went up within a sprint.
Another thing that worked: intentional overlap. I asked everyone to keep a four-hour window where their schedule touched someone else's. Doesn't have to be the same four hours every day. Just enough that real-time collaboration is possible when it matters. For us, that meant the European folks started an hour earlier twice a week and the US folks stayed an hour late. Small friction, big payoff for pair debugging and design reviews.
The mistake I see new remote managers make most is overcompensating with process. They add more standups, more check-ins, more status reports. Remote teams don't need more process. They need clearer expectations, better documentation, and managers who resist the urge to fill silence with meetings. Silence on a remote team usually means people are working. Let them.
One practice I'd recommend to anyone: do a quarterly retrospective on how the team communicates, not just what it builds. Ask what's getting lost, what's annoying, what's working. The answers change as the team grows. What worked for six people breaks at fifteen. Stay curious about the system, not just the code.