Remote work was an experiment that became a default, and now it's something stranger: a thing companies argue about in public while quietly settling into hybrid in private.
Six years in, the question isn't whether remote work works. It's what shape work should take now that location is unbundled from job description. This piece is an honest look at what's better, what's worse, and what's still unresolved.
What actually got better
1. Talent is no longer geographically rationed
The biggest unlock isn't the pajamas — it's that great hires are no longer gated by who's willing to relocate to a few expensive cities.
Key takeaway: Remote-friendly companies routinely beat remote-hostile competitors on talent quality, not just cost.
2. Async writing got serious
Companies that went remote properly invested in writing — decision docs, design proposals, async standups. The result is a paper trail of why decisions were made, which is genuinely useful for new hires.
Key takeaway: Strong writing culture is the closest thing to a remote work superpower.
3. Work fits around life
For people with kids, caretaking responsibilities, or chronic illness, remote work is closer to "the work is finally accessible" than "I get to work in pajamas."
Key takeaway: The accessibility gain alone is reason enough to keep remote on the table.
What actually got worse
Pretending remote work is free is a popular online sport. It isn't.
1. Onboarding takes longer
You learn a new company by absorbing its texture — overheard conversations, hallway introductions, the way people roll their eyes during certain meetings. Async writing replicates some of that, but not all of it, and not fast.
Key takeaway: Budget more time and more deliberate context for remote onboarding than you think.
2. Junior engineers miss osmotic learning
Senior engineers are mostly fine remote — they already have the patterns. Junior engineers learn by sitting next to someone debugging in real time, and that's harder to recreate over Zoom.
Key takeaway: Pair sessions and recorded walkthroughs aren't optional anymore; they're the training pipeline.
3. Loneliness is a real productivity tax
You can't process every weird work feeling alone in your apartment. Some teams burn out faster remote, even when they ostensibly have more time.
Key takeaway: Treat connection as infrastructure, not a perk.
The best remote teams act like they have to earn the trust they used to take for granted.
Hybrid as a deliberate compromise
Most teams have settled into 2 or 3 in-office days. The point isn't the desk; it's the deliberate overlap.
1. Anchor days, not assigned days
The teams that make hybrid work pick specific days when everyone's together — for whiteboarding, lunches, the unstructured side conversations that actually generate ideas.
Key takeaway: Two great anchor days beat five mandatory days.
2. Travel as the unlock for distributed teams
For fully remote teams, occasional in-person offsites do a lot of the work hybrid days do. They're expensive, and they're worth it.
Key takeaway: Budget at least one team-wide gathering per year — non-negotiable.
3. Don't pretend the office is "back"
Returning to the office "like before" doesn't bring back the before. The office now competes with people's home setups, and a lot of those home setups are very nice.
Key takeaway: If you want people in, the office has to earn it.
Closing thought
Remote work isn't a perk and it isn't a temporary state. It's a redesign of how knowledge work happens. The companies that win the next decade will be the ones that stop arguing about where work happens and start designing for the version of work they actually want.
