The remote vs. office debate is a distraction. The actual question is whether your organization has the discipline to pick a model, design around it, and own the trade-offs.
Most don't. They waffle into hybrid by default -- "three days in, maybe" -- and end up with two half-built infrastructures. Remote employees feel peripheral. In-office employees resent uneven expectations. Async tooling gets partial investment. Office space gets partial utilization. Nobody wins because the organization optimized for the appearance of flexibility rather than the reality of functioning.
Why Waffling Is Worse Than Either Extreme
A fully remote company builds around async communication, written decision-making, and distributed hiring. A fully in-office company builds around spontaneous collaboration, co-located teams, and geographic density. Both models work because they're coherent -- every operational decision reinforces the same set of assumptions.
Hybrid without clear design principles is neither. Meetings default to in-person attendees because it's easier. Information flows through hallway conversations that remote employees miss. The written culture that remote work requires never develops because in-office employees don't need it. The result is a two-tier system where proximity to the office correlates with influence, and the company's stated flexibility is contradicted by its actual power dynamics.
The Design Requirement
Hybrid can work, but only as a deliberate engineering problem. That means hard-coded expectations -- "everyone in-office Tuesday through Thursday" -- not soft guidance. Real investment in async tooling so remote days aren't second-class days. Senior leaders modeling the norms: if the CEO takes every meeting from the office while the team is supposed to be hybrid, the team learns that "remote" means "out of the loop."
The Trade-Off Acknowledgment
Every work model has costs. Remote means slower trust-building and harder onboarding. In-person means smaller hiring pools and higher real estate overhead. The problem isn't the trade-offs. It's pretending you can avoid them.
Pick a model. Design around it. State what you're giving up. Your team deserves that clarity more than they deserve the illusion of having it all.