Managing Remote Teams, Honestly

Managing Remote Teams, Honestly

A lot of remote-team advice is glossy nonsense. Async-first! Trust by default! Outcomes not hours! All true in a brochure. None of it tells you what to actually do on the Tuesday when one of your contractors goes silent for 36 hours and the launch is on Friday.

I've managed and helped manage a fair number of remote teams now — at Microsoft across 12 global offices, at InMobi across Europe and the Middle East, and now with founders running 3-to-15 person distributed teams. The honest version of remote management is less photogenic than the LinkedIn version, but it works.

You are managing the silence, not the work

In an office, you can see when someone is stuck. They sigh. They go for a walk. They sit at their desk a little too long. Remote, you get none of that. You get whatever they choose to type into Slack.

The hardest skill in remote management is reading the *absence* of signal. The teammate who normally posts five updates a day and posted one. The contractor who used to ask questions and stopped. The PM who's saying "all good" in standups but their PRs are getting smaller.

Silence is not a green light. Silence is a signal. The remote managers I trust are the ones who notice it within a week, not within a quarter.

Onboarding is the leverage point

If a remote teammate's first two weeks are bad, they will quietly disengage and you will spend six months wondering why. If their first two weeks are great, you'll get a year of focused work before anything else matters.

Concrete things that work: - A written onboarding doc with their first 30 days mapped out — not "explore the codebase" but actual milestones. - A daily 15-minute call with their manager for the first week. Yes, daily. Not forever, just the first week. - One small, real shipping task in week one. Not a tutorial. Something that ends up in production. - A clear answer to "who do I ping when I'm stuck?" — and that person actually has time.

Founders skip this constantly because they're busy. It costs them six months on the back end every time.

Trust is built by predictability, not vibes

The most underrated remote management skill is *being predictable*. Showing up to the same standup, at the same time, with the same energy, every week. Replying to messages within a known window. Saying yes when you mean yes and saying no when you mean no.

Trust isn't built by big gestures. It's built by 50 small ones, repeated, on a schedule the team can rely on. Remote teams build trust slower than co-located teams. You make up for it with consistency, not charm.

Hire for written communication

This is the boring answer that nobody wants to hear: when hiring remote, weight written communication heavier than almost anything else. A great engineer who can't write a clear Slack message will burn three teammates' time every week. A decent engineer who writes well will multiply the team.

Test it in the interview. Give a small written task. Read it carefully. The signal is enormous and most teams ignore it.

Remote work is not harder than co-located work. It's *differently* hard. Most of the difficulty lives in places that don't show up on the dashboard, which is exactly why it gets ignored until it's too late.