Most hybrid work arrangements fail in a way nobody puts on the org chart. On paper, everyone has the same job and the same access. In practice, the people in the office live in a different company than the people at home. Decisions get made in the hallway on the way to lunch. The real context for a project lives in a conversation that happened by someone's desk. The remote employee gets the summary, late, secondhand, and slowly learns that the meeting they joined on video was the polite version of a decision already reached in the room. Resentment does not arrive as a dramatic event. It accumulates, one excluded moment at a time, until your best remote people quietly start looking elsewhere.
The instinct, when you notice this, is to fix it with policy. Mandate cameras on. Require everyone in three days a week. Add a remote-inclusion item to the meeting checklist. None of it works for long, because you are treating symptoms of a deeper design flaw. The flaw is that you are running an in-office company with remote people bolted on. The fix is to invert the default and run a remote company that happens to have offices. You run the whole thing as if everyone were remote, including, and this is the part that matters, the people sitting fifteen feet from each other.
The two-tier company nobody admits to building
Let me describe the failure precisely, because naming it is half the work. In a typical hybrid setup, proximity becomes power. Not officially, never officially, but functionally. The person in the room hears the aside that reframes a project. They catch the manager's mood before the one-on-one. They get pulled into the impromptu whiteboard session that becomes the actual decision. The remote worker, no matter how talented, is structurally downstream of all of it.
This produces a quiet two-tier system. Tier one is in the building, plugged into the informal network where most real coordination happens. Tier two is remote, technically equal, practically peripheral. And here is the part that should worry any leader: the sorting into tiers has nothing to do with performance. It tracks geography and, often, life circumstance. The parent who works from home to manage school pickup, the employee who moved for a partner's job, the person with a commute that eats two hours, these are frequently your most committed people, and the proximity-based system penalizes them for the exact flexibility you offered as a benefit.
Over time the message lands. To be taken seriously, be in the room. So people come in, not because the work requires it, but because absence has become a career risk. You wanted hybrid and you built a soft return-to-office mandate enforced by anxiety. The resentment is the rational response of people who can see the rules they were never told about.
Run the whole company as if everyone were remote
The principle that fixes this is uncomfortable for in-office leaders because it asks them to give up the very convenience that created the problem. If a decision matters, it does not get made in the hallway. It gets made in a place every relevant person can see, regardless of where they sit. The office stops being where the real company operates and becomes what it should be, a nice place to do focused work and have lunch with colleagues, with no bearing on who has access to information or influence.
Concretely, running remote-first means the source of truth is written and shared, not spoken and remembered. Decisions get documented where everyone can read them. Discussion happens in channels and documents, not only in rooms. When something does happen in a room, the output goes to the same shared place immediately, so the person at home is not waiting on a generous colleague to relay it. The test I use is simple: if a fully remote employee in another time zone could not have participated in or at least seen a decision, then we made it wrong, and we fix the process, not the person who missed it.
This is where the tooling matters more than people expect. You cannot run a remote-first company on tribal knowledge and a hope that information will flow. The work, the decisions, and the context have to live somewhere durable and shared by default. We run our own operations inside Atlas precisely because tasks, projects, the inbox, and the discussion around them sit in one place that everyone can see, which means the in-office advantage of overhearing things mostly evaporates. There is nothing to overhear when the information was written down where everyone already looks.
The practices that make it fair in daily life
Principles are easy to write and hard to live. A handful of concrete habits do most of the work of keeping a distributed team genuinely level:
- One person remote means everyone remote. If a single participant in a meeting is on video, everyone joins from their own screen, even the people in the building. No half-room, half-screen meetings, because those are exactly where the remote voice gets lost. This one rule prevents more resentment than any policy document.
- Default to writing. Important context goes into a document or a thread before it goes into a meeting. This is not bureaucracy, it is the thing that lets someone in another time zone contribute on equal footing.
- Make decisions legible. Every meaningful decision has a written record of what was decided, by whom, and why. The hallway conversation is fine as thinking. It is not fine as the only record.
- Protect asynchronous time. A distributed team that schedules everything synchronously just exports the in-office problem to calendars. The point of remote work is partly that not everything needs everyone live at once.
I want to dwell on the first one, because it is the highest-return rule on the list and the one most companies refuse to adopt. A meeting with six people in a conference room and two on a screen is not a meeting with eight participants. It is a meeting with six participants and two observers. The room has the side conversations, the body language, the whiteboard. The screen has a laggy view and the courage to interrupt. Make everyone join from their own machine and the playing field levels instantly, at the small cost of in-office people feeling slightly silly sitting alone at their desks on a call. That mild awkwardness is the price of fairness, and it is cheap.
What management has to give up
None of this works if managers keep managing by visibility. The deepest habit to break is the equation of presence with contribution, the quiet sense that the person you see working is the person who is working. Remote-first management means evaluating output, not attendance, and that requires managers to actually define what good output looks like rather than relying on the lazy proxy of who was around.
This is harder than it sounds and it is where most hybrid cultures secretly break. A manager who cannot articulate what a role should produce will fall back on presence every time, because presence is observable and outcomes take thought to define. So the real work of running fair hybrid is not a tooling project, it is a management upgrade. You have to get specific about goals, communicate them in writing, and judge people on whether they hit them, wherever they sat while doing it. Do that and remote stops being a disadvantage, because the thing being measured no longer correlates with location.
Leaders also have to model the behavior, visibly. If the founders and executives make their real decisions in the building and only perform inclusion on camera, everyone reads it instantly and the whole effort collapses. When I have a substantive conversation that shapes direction, it goes into the shared record, even when it would have been faster to just tell the three people near me. That is not convenient. It is the tax that proximity-holders pay so that the system stays fair, and the most senior people have to pay it first, because everyone is watching what we actually do, not what the handbook says.
Onboarding is where remote-first is won or lost
If you want to know whether a company is genuinely remote-first or just tolerant of remote work, watch how it onboards. The first month is when an employee learns the unwritten rules, and a new hire who starts remote into an in-office culture learns the most damaging rule of all: that the real information lives in the building and you are on the outside of it. They miss the casual context that in-office newcomers absorb by osmosis, they do not know who to ask because they have never overheard who knows what, and they spend their first weeks feeling vaguely behind without being able to say why.
The fix is the same principle applied earlier and harder. The onboarding has to assume the new person can see nothing they were not explicitly shown, which means the context that in-office hires pick up by proximity gets written down and handed over deliberately. Who owns what. How decisions actually get made here. Where the real conversations happen. We treat a new hire's first weeks as a test of our own documentation, because if a remote starter cannot get productive from what is written, the gaps they hit are gaps every distributed employee is quietly working around. The new person is the canary. Fix what they stumble on and you improve the system for everyone.
Pairing matters too. A new remote employee needs a designated person whose job is to answer the questions they do not yet know to ask, because the in-office equivalent, turning to the desk next to you, does not exist for them. Build that connection on purpose and you replace the proximity that remote work removes. Leave it to chance and you recreate the two-tier problem at the worst possible moment, when someone is forming their first impression of whether this company actually meant what it said about being distributed.
Why fairness is the strategy, not the kindness
It would be easy to read all of this as an argument about being nice to remote workers. It is not. It is an argument about not throwing away talent and not poisoning your culture. The resentment that builds in a two-tier hybrid is not a soft cost. It shows up as your best distributed people leaving, as a slow concentration of influence among whoever happens to live near the office, and as a workforce that quietly narrows to the people for whom commuting is easy, which is a far smaller and less varied group than the one you could have had.
Run hybrid as remote-first and you get the opposite. You keep the person who does brilliant work from another city. You keep the parent who needs flexibility and repays it with loyalty. You get a company where influence tracks contribution rather than geography, which is the only basis on which it should ever track. The office becomes a genuine perk instead of a hidden requirement, and the people who choose to come in do it because they want to, not because they are afraid of what happens if they do not.
Hybrid work does not fail because remote work is hard. It fails because most companies run it as in-office work with exceptions, and exceptions always get treated as second class. Decide instead that the remote experience is the real experience, build the whole company around that, and the resentment has nowhere to take root. Everyone is in the same company again. That is the entire point, and it is worth the awkward calls and the written records to get there.