When organizations first went remote, there was a lot of hand-wringing about what would be lost. The casual hallway conversation. The creative collision. The ability to actually know what people were working on. Some of that concern was legitimate. Some of it turned out to be noise.
What's interesting is what actually improved, and it's usually the thing nobody talks about in the remote work discourse.
Take documentation. When people worked in physical offices, knowledge lived in someone's head, or in email threads, or in conversations that happened near the coffee machine and never made it into any system. Onboarding new people meant pairing them with an existing person for weeks. Questions got answered the same way three times a year because nobody had written the answer down.
Remote work killed that out of necessity. If you can't just swing by someone's desk, you start writing things down. You build wikis. You record Loom videos. You actually document your decision-making process because synchronous explanation isn't an option. Organizations that made this transition seriously now have institutional knowledge that's actually accessible. It's searchable. New people can find it without bugging someone.
This is boring infrastructure work. Nobody gets excited about it. But it's the kind of thing that compounds. It makes the organization function better, faster, for way longer than the people who originally created the knowledge stick around.
Something similar happened with meetings. The forced shift to video created an accidental constraint: if a meeting happens on Teams and it's recorded, anyone who wasn't there can watch it later. Suddenly there's no second-class participation for people in different time zones, or people who were heads-down on something else when the meeting happened. Organizations started being more intentional about what meetings actually needed to happen synchronously.
Some teams discovered they didn't need weekly touch-bases if they had a shared document and async updates. Others realized that meetings worked better when they actually had an agenda and a decision to make, instead of just being "where we check in on stuff." The ones that got this right stopped having meeting exhaustion.
There's also the thing that happened with focus time. In an office environment, if you want to concentrate, you're basically fighting against the entire structure of the place. Someone will interrupt. You'll get pulled into a conversation. Your calendar will fragment your day.
Remote work made focus time the default state instead of the thing you have to defend. You can actually do work that requires deep concentration. Some teams found they could ship things faster. Others discovered they could actually think about problems instead of just reacting to them all day.
None of this was guaranteed to happen. Organizations had to choose it. Some remote teams still meet constantly, still duplicate information across three different systems, still struggle with async communication. The difference between ones that got better and ones that got worse usually came down to whether leadership actually decided to change how work gets done, rather than just moving the exact same office-based workflows into Zoom.
The organizations that did this right didn't stumble into it because remote work forced them. They decided that if they were going to go distributed anyway, they might as well fix some of the stuff that was broken about how they worked.
Turns out that's one of the better things that came out of all this.