A note on this archive: an earlier version of this site was lost in a migration, with no surviving backup. This piece is a good-faith recreation of our writing from this period, not a recovered original; its date reflects the period it represents. See about this archive.
A few months ago, remote work was a debate. Now it's just how everyone works.
Before anything else: this has been a hard, strange spring, and the scramble to work from home came wrapped in a lot more worry than any normal change-management project. We don't want to wave that away. But if your team is figuring out distributed work on the fly right now, we've been doing it for years — and a few of the lessons we picked up slowly might save you from learning them the hard way.
The struggle usually isn't the tech
Watching companies go remote overnight, the thing that stands out is that the ones struggling mostly aren't struggling with their tools. The video calls connect. The files sync. What breaks is the set of habits that quietly depended on everyone being in the same room — and you don't notice those habits until the room is gone.
So here's what actually matters, from years of doing this on purpose.
A meeting is not a substitute for writing it down
In an office, you can settle things by talking and trust that the people who needed to hear it were nearby. Remote, that breaks immediately. If a decision only lives in the memory of whoever was on the call, half the team is working from yesterday's plan. Write it down, put it where people can find it, and you erase a whole category of "wait, I didn't know that changed."
"Are they working?" is the wrong question
A lot of newly-remote managers are anxious about whether people are really working when they can't see them. It's the wrong question, and chasing it — status pings, constant check-ins — makes everything worse. The right question is "is the work happening?" Judge the output, not the hours or the green dot. People feel the difference between being trusted and being watched, and they do better work under the first one.
More video calls are not more communication
When the hallway disappeared, a lot of teams tried to replace it with meetings — and now everyone's worn out by a screen full of faces, the "Zoom fatigue" you've probably already felt. Communication isn't the number of calls; it's whether the right information reached the right people. A good written update often beats a meeting, and it doesn't cost anyone an hour they'll never get back.
Trust is the load-bearing wall
Underneath all of it is trust. Distributed work runs on the assumption that people will do their jobs without being watched, raise their hand when they're stuck, and tell the truth about where things stand. If that trust is there, the tools barely matter. If it isn't, no tool will save you. We made this case before, back when working with someone you couldn't see was still considered exotic — it's just that everyone gets to test it at once now.
The part worth keeping
When things settle — and they will — there'll be a temptation to treat all of this as an emergency you endured and then filed away. I'd push back on that. The teams that use this stretch to actually build the muscle — clear writing, real trust, remote-first as a discipline rather than a stopgap — are going to come out of it with an advantage that outlasts the reason they started. The hard way is still the way. You just don't have to learn all of it the hard way.