Six years ago I made a decision that almost broke my team. I told everyone they could work from wherever they wanted, whenever they wanted. I thought I was enlightened. What I actually built was a group of nine people who stopped talking to each other. Not out of spite — they just drifted. Three months in, our sprint velocity had dropped about 40%, and nobody could tell me why.
The problem wasn't distance. It was me. I had confused freedom with absence, and managing remotely means being more present in some ways, not less. Not physically present. Structurally present. The leaders who get this right don't have better tools or bigger budgets. They have a different operating system for how a team stays connected when nobody shares a hallway.
Key Takeaways
- The location of your team matters far less than the quality of your management, your clarity of expectations, and how intentionally you design the group.
- Written communication becomes your default — and most managers never learn to write for a remote audience.
- Trust is built through consistency, not surveillance. Tracking hours is the fastest way to lose a good engineer.
- Performance reviews need rewriting. Output metrics from a shared office often say nothing about remote contribution.
- Async doesn't mean silent. You need rituals that create belonging without forcing everyone onto a video call.
Leadership strategies that actually survive contact with remote teams
Let me start with the hard part. When I ran my first fully remote team, I kept falling into the same trap: I'd assume silence meant everything was fine. In an office, you read a room in two seconds. Someone's shoulders are tight. Someone else is unusually quiet. That data disappears overnight when your team goes remote, and most of us never replace it.
Stop managing time, start managing outcomes
The first thing I changed — and this took me embarrassingly long to figure out — was to kill the assumption that being online equals working. I had a developer who logged in at 11am because he picked his kids up from school at 3pm. For six months I privately worried he was slacking. His output was consistently the best on the team. I was the problem, not him.
Remote leadership means you define what "done" looks like in writing, then get out of the way. Vague goals like "improve the onboarding flow" become useless when there's no hallway conversation to clarify them. So write it down. And then write it down more clearly than feels comfortable.
- A definition of done that a stranger could evaluate without asking you a single question
- Deadlines with dates, not "sometime next week"
- Who owns the decision, and who only needs to be informed
- The one metric that genuinely matters for this piece of work
The payoff isn't just clarity. It's that you stop needing to be in every conversation, which is the only way remote management scales beyond about eight people.
What great remote managers do differently
I've worked under and alongside maybe twenty managers running distributed teams. The good ones share a habit that took me years to name: they over-communicate the boring stuff. Not strategy decks. The unglamorous context — why a project got deprioritized, who's struggling, what changed about the roadmap and why. In an office, that context travels by osmosis. Remotely, it travels only if you push it.
There's a research angle here worth naming. Gallup's workplace data tracked employee engagement falling from 41% in 2019 to 35% in early 2024 — and notably, the drop was concentrated among remote and hybrid workers who felt disconnected from their organization's mission. The number itself isn't the story. The story is that connection is a management deliverable, not a side effect of a good culture. You have to produce it on purpose.
The managers who succeed remotely are the ones who realize their job is now partly editorial. You are writing the story of the team, every week, for people who can't see the office whiteboard.
Managing remote and hybrid teams: the hybrid trap
Pure remote is honestly easier to lead than hybrid. Hybrid creates a two-tier system by accident, and if you don't actively fight it, the people in the office win every invisible battle.
The proximity bias nobody admits to
I watched this destroy a project two years ago. Half the team was in one city, half was scattered. Promotion decisions, quick hallway fixes, "hey can you take a look at this" — all of it flowed to the people who happened to be sitting near the manager. The remote folks did competent work and got passed over for the interesting projects. Nobody was being malicious. They were being human.
The fix is mechanical, not motivational: default every meeting to remote-first. If one person is dialing in, everyone dials in. Even the people in the building. Once you accept that video calls where three people share a conference room mic are a disaster, you stop doing them.
| Practice | Office-first habit | Remote-first replacement |
|---|---|---|
| Decisions | Made in the hallway, announced later | Written up before the meeting; meeting only resolves disagreement |
| Meetings | Everyone in the room, one person dialing in | Everyone on their own device, even when co-located |
| Feedback | Quick verbal comment at someone's desk | Documented, specific, within 24 hours |
| Onboarding | Shadow a colleague, absorb by watching | Explicit checklist with an assigned buddy and weekly check-ins |
Expectations for remote workers — spelled out
This is where I see the most confusion, and I've been guilty of it too. "We trust you to manage your time" sounds generous. In practice it's terrifying for a new hire who has no idea what's expected. So I now write the unwritten rules down. Response time expectations. Which channels are for urgent things and which are for later. How many hours overlap we require across time zones. When people are genuinely allowed to log off.
Real talk: the single most useful document I ever created for a distributed team was a two-page "how we work" file. It saved more confusion than any tool we ever bought.
Communication that doesn't collapse under its own weight
Every remote team eventually drowns in messages. Slack, Teams, email, a project board, a wiki nobody reads. The instinct is to add another channel. That's the wrong reflex.
The async default
I'll die on this hill: most meetings should have been a document. Not all. But most. When someone schedules a 30-minute call to "align on X," what they usually mean is they haven't decided what X is yet. Writing forces the decision.
My rule, after a lot of trial and error, is simple. If a topic needs a decision, write a one-page brief first. If nobody has comments after 24 hours, the decision stands. If there are comments, we meet — and the meeting is shorter and better because everyone read the same thing. I cut our recurring meeting load by roughly half doing this. Nobody missed the meetings.
Rituals that create belonging without surveillance
Here's a mistake I made early: I tried to recreate office social life on video. Virtual happy hours. Icebreakers. Everyone hated them, including me, and attendance quietly dropped to two people and a dog.
What actually worked was lower effort and less performative. A weekly written update where people share one win and one friction point. A rotating "demo day" where anyone shows something they built, however small. A shared channel for non-work stuff that nobody is required to read. The belonging comes from repeated small signals that you know what your colleagues are doing and care about the outcome — not from forced fun.
Performance and evaluation when you can't see anyone working
This is the part almost every remote-management guide skips, and it's the part that broke me the first time. I was evaluating people on activity — messages sent, hours online, how quickly they replied. Every one of those signals was noise dressed up as data.
Rewrite the review around outcomes
When you can't watch the work happen, you have to evaluate the result. That means the review conversation changes. Instead of "you were responsive and present," it becomes "here's the outcome you owned, here's what the data shows about impact, and here's where I think you could go further."
- Judge the artifact, not the activity. A shipped feature beats a hundred status messages.
- Keep a running log. I keep a simple file per person with specific wins and specific misses, dated. It takes two minutes a week and it makes reviews honest instead of recency-biased.
- Separate the person from the number. Remote work makes people defensive about their output because they can't see you seeing them.
- Do the review live, on video, with the document open. Text-only performance feedback reads as cold, and people read tone into plain sentences that you never intended.
One thing I learned the hard way: if someone is underperforming remotely, the cause is usually unclear expectations, not laziness. I once spent weeks assuming a designer was checked out. Turned out he had no idea what "good" looked like for the project because I'd never defined it. My failure, framed as his.
The thing that lingers
Nobody hands you a manual when your team goes remote. You build one by making mistakes in front of people who trusted you. I've done that more times than I'd like to admit.
But here's what I keep coming back to. The leaders who do this well aren't the ones with the slickest stack of tools or the most elaborate meeting cadence. They're the ones who treat clarity as a kindness and connection as real work. If you take one thing from all of this, let it be that. The tools change. The operating system doesn't.
And if your team is quiet right now, that might not be peace. It might be the sound of people slowly drifting. Go ask someone what they're actually working on. You might be surprised by the answer.
