The thing that surprised me about managing people I rarely see in person is how much of ordinary management turns out to have been passive. In an office you absorb an enormous amount without asking: who looks stuck, who is bored, who two people are quietly disagreeing about something. None of that arrives on its own when the team is distributed. It has to be manufactured, deliberately, by someone.
That is the actual shift, and it cuts both ways. If you work remotely, a large amount of information about you that used to travel for free now has to be sent. This is not the same as self-promotion, and confusing the two is why so much remote-work advice reads badly.
What the evidence supports, precisely
The most credible study in this area is Nicholas Bloom's randomised trial at Trip.com, written up by Stanford. It found that employees working from home part of the week performed as well as their in-office peers, were promoted at similar rates, and resigned at a substantially lower rate.
It is worth being exact about what that does and does not show, because it gets cited loosely in defence of arrangements it did not test. The trial was of hybrid work — two days at home, three in the office — at a single large company, with employees who already knew each other and each other's work. It is strong evidence that hybrid does not damage productivity or promotion prospects. It is not evidence about fully distributed teams, about people who have never met, or about the first ninety days in a new job, which is the hardest case and the one nobody has good data on.
My own read, from a team that is partly distributed: the format is close to neutral for work that one person does alone, mildly negative for work requiring rapid back-and-forth between several people, and clearly negative for the informal transmission of context to anyone new. The last of those is the real cost and it is usually paid by the most junior people, silently.
Making your work legible
The mechanism that harms remote employees is not managers doubting you are working. It is managers having less material to think with when they come to say something about you.
When I write a performance review, I am reconstructing a year from what I can recall and what is written down. For someone in the room, the recall is richer. For someone remote, the written record is nearly all of it. So the written record is worth investing in — not as theatre, but because it is the input to decisions about you.
In practice that means a few habits.
Say what you are doing before it is finished, in a channel rather than a direct message. Not a status report — a sentence when you start something non-obvious, and a sentence when you learn something from it. The channel matters because it lets other people connect it to their own work, which is the thing that happens spontaneously in a room.
When you are blocked, say what you already tried. "Stuck on the query performance" tells me nothing and costs me a meeting to unpack. "The endpoint takes five seconds; I have ruled out the index and the serialisation, I think it is the N+1 in the loader, before I restructure it does anyone know why it was written this way" is a complete artefact. It shows your reasoning, it is answerable asynchronously, and it happens to be the single most persuasive evidence of competence you can produce.
Keep your own record. Not for your manager — for you. A running note of what you shipped, what broke, what you fixed and what people said about it. Every review season I watch capable people fail to remember their own year, and the ones who have a list get better outcomes, because the review reflects what is in front of me when I write it.
Writing is the job now
In a distributed team, writing stops being a soft skill and becomes the medium through which most of your work reaches other people. This is genuinely unfair to some excellent colleagues who think faster than they type, and it is still true.
The version that matters is not eloquence. It is: put the conclusion first, state what you need from the reader, and assume they are reading it six hours later with no memory of the context. Most bad workplace writing is not badly written — it is a transcript of someone thinking, published in the order they thought it.
The other half is restraint. A two-thousand-word message is not more informative than a short one; it is a request that someone else do the compression you declined to do. And the instinct to write long Slack essays is often anxiety about visibility, which the reader can feel.
Structure, and the part about burnout
The failure mode of remote work is not slacking. Every serious look at this finds the opposite problem: the working day stretches, because the commute that used to end it is gone and the laptop is fifteen feet from where you sleep.
What actually helps is boring and physical. A defined start and stop that other people know about. A place where work happens that is not where you relax, even if that is a corner of one room. Getting outside during daylight, which sounds like a wellness platitude and is in fact the intervention most people notice immediately when they start doing it. Notifications off after hours — not as a boundary-setting gesture, but because the alternative is a nervous system that never fully stands down.
The isolation is the other half and it is harder to solve, because the fix is not a tool. Days can pass without a conversation that is not about work. If that is your situation, it is worth treating seriously rather than waiting for a team offsite to fix it: standing calls with one or two colleagues, a co-working day, a commitment outside the house on a fixed day. People who do remote work well for years almost all have something like this, and they had to build it on purpose.
For managers, briefly
Almost everything written about remote management is about monitoring, which is the wrong end. Two things matter much more.
Write things down, so that the context that used to circulate in a room exists somewhere retrievable. A team with good written decisions absorbs new people far better than one with excellent meetings.
And be explicit about the things you would otherwise convey by presence. In an office people infer that they are doing fine from a hundred small signals. Remotely those signals do not arrive, and the default assumption in their absence is usually negative. Saying plainly that someone's work is good, and being specific about it, does more for a distributed team than any process change.
Is it right for you
The honest answer is that it depends on things you can partly predict. People who need external structure to start work, who process by talking, or who draw significant social life from work tend to find it harder, and no amount of discipline fully compensates. People who work best in long uninterrupted blocks and whose social life is elsewhere tend to find it a large improvement.
But do not decide from a list. Most people misjudge this until they have done it for six months, and the version that suits many is neither pole — a few days in company, the rest alone, which is roughly what the evidence supports anyway.
Tags
Taresh Sharan