The afternoon I realized I had seventeen browser tabs open — each one a different tool my team had adopted in the previous eighteen months — I closed my laptop and went for a walk. It was a Tuesday in late 2021, and I was supposed to be writing. Instead I had been toggling between a project board, a chat window, a shared doc, a video call lobby, a time-zone converter, and something called an "async standup platform" that nobody on the team had logged into since March. The walk lasted forty minutes. The tabs were still there when I got back.
That moment has become a kind of personal shorthand for everything that went wrong with the remote work experiment — not the working from home itself, which I had wanted for years, but the layer of tooling we piled on top of it like insulation that turned out to be noise.
The Accumulation Problem Nobody Warned Us About
When offices emptied in 2020, companies did not just shift their workflows online. They panicked-purchased. Every friction point in remote collaboration became a product category. Asynchronous video? There's a startup for that. Virtual office with ambient sound? Six startups for that. The result was a kind of tooling arms race where the cure became indistinguishable from the disease.
I spoke to a product manager at a mid-sized SaaS company — she asked me not to use her name — who told me her team was paying for eleven separate subscriptions by mid-2022. "We had two tools that did basically the same thing," she said, "and nobody could remember which one was the official one, so people just used both and duplicated everything." She estimated her team lost roughly four hours a week to what she called "tool overhead": finding the right channel, converting a Loom link someone sent into a task, re-explaining context that existed in three different places.
Four hours a week. Per person. That is a full workday, evaporated.
The remote work tools that actually work, I have come to believe, are not the ones with the most features. They are the ones that reduce the number of decisions a person has to make before they can do the actual work.
What Staying Power Actually Looks Like
Consider Slack, which is easy to mock and just as easy to underestimate. When it works — and I mean genuinely works, not just hums along while everyone complains about notification volume — it works because a team has made deliberate choices about how to use it. Channel discipline. A norm around threading. An agreement about what warrants a direct message versus a public post. None of those things come from Slack. They come from the people.
This is the uncomfortable truth about remote work tools that actually work: the tool is rarely the variable. The variable is the social contract the team builds around it.
I have watched the same project management software succeed brilliantly at one company and become a graveyard of abandoned cards at another. The software did not change. The culture of accountability around it did. One team did a five-minute weekly review of open tasks. The other trusted that people would update their cards organically. They did not.
Notion is another instructive case. It is genuinely one of the most flexible pieces of software I have used — a canvas that can become a wiki, a database, a task list, a journal, or an elaborate personal CRM if you have the patience. It is also one of the easiest tools to over-engineer into uselessness. I spent three weeks in 2022 building what I called a "content operating system" in Notion. It had linked databases, rollup properties, a kanban for drafts, and a calendar view that auto-populated from a status field. It was beautiful. I used it seriously for about ten days before reverting to a plain text file and a legal pad.
The legal pad is still on my desk.
The Ones That Earned Their Place
So which remote work tools actually work? Let me be specific, because vague endorsements are useless.
For writing and thinking, nothing I have tried beats a plain document — Google Docs for anything collaborative, iA Writer for anything solo. The constraint is the feature. When you remove the ability to add a status field or a linked database, you are left with the only thing that matters: the words.
For meetings that cannot be avoided, Zoom has earned its ubiquity not through innovation but through reliability. It works. The video does not freeze as often as the alternatives. The audio is consistent. That is not a glamorous recommendation, but reliability is the most underrated quality in a remote work tool. A video call platform that drops your connection during a client presentation is not a minor inconvenience — it is a trust event.
For asynchronous communication, the tool that surprised me most was the humble shared document with a running log of decisions. Not a fancy async video platform. Not a structured standup bot. Just a Google Doc titled "[Team] Decisions and Context" where anyone can add a timestamped note. I started doing this with a small editorial team in 2023. Six months in, it had become the single most-referenced artifact of our collaboration — a searchable record of why we made the choices we made. It cost nothing and required no onboarding.
For project tracking, I keep coming back to Linear for software teams and a simple Trello board for everything else. Not because they are the most powerful options — they are not — but because their interfaces impose just enough structure without demanding that you become a tool administrator to use them.
The Fatigue Is the Signal
There is a version of this essay that becomes a listicle, and I want to resist it, because the list is not the point. The point is the pattern.
Every tool I have described above succeeded in my experience because it reduced cognitive overhead rather than added to it. Every tool I have abandoned — and there have been many, from elaborate time-tracking software to AI-powered meeting summarizers that somehow made meetings feel more exhausting — failed because it asked me to spend mental energy managing the tool itself.
The remote work tools that actually work have a quality I can only describe as low friction in the right places. They do not make it easy to procrastinate by customizing. They make it easy to start.
A friend of mine who runs a small design studio put it more bluntly when we talked about this over coffee last spring. "I stopped evaluating tools by their features," she said, "and started evaluating them by how long it takes a new person to be useful in them." Her current stack: Figma, Slack, a shared Notion wiki that nobody touches except to update the client list, and a weekly thirty-minute video call. That is it. Her studio does good work. Her clients are happy. Her team does not spend Tuesday afternoons with seventeen tabs open.
I think about that a lot.
Because the deeper question — the one I have been circling since that walk I took in 2021 — is not which tools work. It is what we were hoping the tools would do for us. Whether we were buying software or buying the feeling that we had solved the problem of working together across distance. Those are different purchases. Only one of them actually ships.