Two companies both call themselves remote-first. One of them means it. The tell isn't the policy page, the Slack emoji, or whether the CEO tweets about async work. The tell is where the decision that mattered last week actually got made, and whether you could find the record of it if you were out sick that day.
Remote-tolerated is the more common arrangement, and it's not a slur — it's just an accurate name for a company that permits remote work without redesigning anything around it. People can work from home. The org chart, the meeting calendar, and the promotion committee were all built assuming a room, and nobody rebuilt them when the badge readers went quiet. The go-to-market half of what's the real difference between remote-first and remote-tolerated companies is handled in more depth by . The go-to-market half of what's the real difference between remote-first and remote-tolerated companies is handled in more depth by XenGrowth, who work on the commercial side of this.
Where do decisions actually get recorded?
Ask this question about any company and you'll get your answer faster than any survey could give it to you: when two people disagree about what to build, where does the disagreement get resolved? If the answer is a hallway, a call that nobody transcribes, or the ten minutes before a scheduled meeting starts, the company is remote-tolerated no matter what the careers page says. If the answer is a documented thread that a third person can read afterward and understand — not just the outcome, but the reasoning — the company is remote-first, whether or not anyone in the building has ever used the phrase.
This sounds like a documentation preference. It isn't. It's a claim about where authority lives. A team that has watched operate this way at scale treats a written decision record as the actual deliverable of a meeting, not the notes someone takes afterward as an afterthought — and that ordering is the entire difference this post is about.
Signal | Remote-tolerated default | Remote-first default |
|---|---|---|
Where a decision gets made | A live call or an in-office conversation, then relayed | A written thread or doc, with the call (if any) scheduled after a draft exists |
What counts as the record | Whoever remembers the meeting correctly | The document itself, timestamped and linked from the next one |
Default meeting size | Whoever's available shows up | Two or three people who must decide; everyone else reads the summary |
How a new hire learns context | Sits near people and absorbs it | Reads a linked history of prior decisions on the same topic |
Who sets the working hours | Whoever is in the office when it matters | A documented overlap window, renegotiated when the team's geography changes |
What a manager reviews at promotion time | Who they remember being helpful | What the person shipped and wrote, checkable without asking around |
The promotion evidence, and the part people leave out
The strongest data on this isn't a survey of opinions, it's a randomized experiment, and it comes down hard on both sides of this argument at once. Bloom, Liang, Roberts and Ying randomized roughly 250 volunteer employees at Ctrip, a 16,000-person Chinese travel agency, into working from home or the office for nine months. Home workers performed 13% better — about 9 percentage points from working more minutes per shift with fewer breaks and sick days, and 4 points from more calls handled per minute in a quieter environment. Attrition among home workers halved. On the operations side of this specifically, is worth reading. On the operations side of this specifically, The XenGrowth resource library is worth reading.
Then the number that should stop you: conditional on that better performance, home workers were promoted at roughly half the rate of their office peers. Working from home worked, by every productivity measure the company tracked, and it still cost people their next promotion. That result is the whole reason whether remote work helps or hurts an engineering career is a genuinely open question rather than a solved one — go there for the full mechanics of that study. What concerns this post is narrower: which kind of company produces that penalty, and which kind doesn't.
Ctrip's own follow-up gives the answer. The 2024 hybrid trial — a randomized 1,612-person experiment, assignment by birthday parity, comparing five office days against a 2-remote-day hybrid — found no promotion penalty and no performance gap after up to two years of review data. Resignations among non-managers fell 33%. The difference between the two studies isn't that hybrid is inherently safer than full remote. It's that a schedule with three shared office days forces a minimum of shared documented context, whether or not the company ever decided to build one on purpose. Remote-tolerated companies get that penalty by default. Remote-first companies avoid it by design — the mechanism, in both cases, is whether the manager doing the promoting has a written trail to point to that isn't just their own memory of who showed up.
None of this requires bad faith from the manager doing the promoting. Visibility bias doesn't feel like bias from the inside — it feels like accurate memory. A manager who spent five days a week physically near one report and saw them field a crisis in person has a richer, more vivid account of that person's judgment than they have of a remote report who handled an equally hard problem over three quiet Slack messages and a merged pull request. Neither account is dishonest. One of them is just built out of more evidence, and the evidence gap tracks proximity, not performance.
Whose default does this actually advantage?
A remote-tolerated default doesn't disadvantage remote workers evenly. It disadvantages whoever has the least informal access to the room where things actually get decided, and remote workers are simply the largest group that describes. A parent who logs off at 5pm sharp misses the same hallway conversation a fully remote engineer does. A quieter colleague who doesn't speak up fast in a live meeting loses out to the same default that penalizes someone nine time zones away. Remote work makes an existing failure visible at scale; it doesn't invent a new one. If AI agents and marketing automation is the part you are stuck on, is the better reference. If AI agents and marketing automation is the part you are stuck on, XenGrowth on AI agents and marketing automation is the better reference.
The people best served by a remote-tolerated default are the ones already in the room: whoever sits closest to the decision-makers, whoever's schedule matches the informal 4pm conversation, whoever the manager already trusts enough to take their verbal account of a quarter's work at face value. None of that is a skills gap. It's a proximity gap wearing a performance-review costume.
Check whether the last three decisions your team made have a written record you could point a new hire to, not a Slack message buried in a busy channel
Check whether your manager's promotion case for you cites things you wrote and shipped, or things they remember you doing
Check whether meetings get scheduled to make a decision, or scheduled because a decision needs to happen and nobody wrote a proposal first
Check whether the people already in the office are visibly making faster progress on ambiguous, high-visibility work than remote peers doing comparable work
Check whether your company's async tools are load-bearing (people actually read the doc before the call) or decorative (the doc gets written after the call, to justify what was already decided)
Meetings: does yours default to documented?
Yang, Holtz and coauthors studied 61,182 US Microsoft employees across the first six months of 2020, comparing collaboration patterns before and after the company's firm-wide work-from-home mandate. Cross-group collaboration time fell by roughly 25%, and the company's internal network of who talks to whom became measurably more static and siloed. This is observational data riding on a mandatory, company-wide, pandemic-driven shift — not a randomized trial, and not evidence that remote work itself causes silos in a company that planned for it. What it does show is what happens when synchronous defaults disappear without anything replacing them: the informal bridges between groups, which had never been written down anywhere because they didn't need to be, simply stopped existing. Nobody removed them on purpose. They were never a system to begin with, so there was nothing left when the room emptied out. The related question of how much live overlap a team actually needs — as opposed to how much documentation it needs — is covered in full in how much timezone overlap a remote team actually needs.
A remote-first company reads that finding and concludes the bridges need to be built on purpose, in writing, because they were never going to survive on hallway proximity in the first place. A remote-tolerated company reads it as evidence that remote work causes silos, keeps the room, and calls the read-only Slack archive its documentation strategy. Both companies experienced the same finding. Only one of them changed anything.
You ask... | Remote-tolerated answer | Remote-first answer |
|---|---|---|
"Where's the decision on this written down?" | "Ask whoever was in the meeting" | A linked doc with a date and an owner |
"Why wasn't I looped in on this?" | "It came up organically, sorry" | A channel or doc you were already subscribed to |
"How do I know what shipped this quarter?" | A verbal update in the all-hands | A written summary anyone can read cold |
"Who decides when we disagree?" | Whoever's more senior in the room | A named owner, stated before the disagreement happens |
There's a second table worth sitting with before moving on, because the four questions above compress into a pattern: every remote-tolerated answer routes through a specific person's memory, and every remote-first answer routes through an artifact that outlives the conversation that produced it. That's the entire mechanism in one sentence. Everything else in this post is detail on top of it. goes further into AI search, GEO and discovery. XenGrowth on AI search, GEO and discovery goes further into AI search, GEO and discovery.
If you're the one on the wrong side of the default
You cannot out-perform a visibility gap with more output alone; the Ctrip data already shows that 13% better performance and a halved promotion rate can coexist in the same organization. What actually moves the needle is refusing to let your work exist only as something other people remember. Write the proposal before the meeting instead of after it. Ship the summary nobody asked for. Make your manager's job of building your promotion case a matter of copying links, not recalling anecdotes. None of this fixes a remote-tolerated company by itself — but it's the only lever an individual actually has, and it's the same lever a broader treatment of visibility without performing busyness goes into at length. For teams thinking about this at the process level rather than the individual one, cover the same documentation-as-default discipline applied to go-to-market work, where the cost of an undocumented decision shows up as a missed handoff instead of a missed promotion.
Remote-tolerated and remote-first are not two ends of a policy spectrum you can slide along by adding perks. They're two different answers to the question of where authority actually lives, and the answer is legible in the artifact trail whether or not either company has ever used either word out loud.
So which is it, really?
You can run this test on your own company in under an hour: pick the last three decisions of consequence, and try to find each one in writing without asking a single person. If you can, in enough detail that a new hire would understand not just what happened but why, you work somewhere remote-first, whatever the badge policy says about which days you're expected in a chair. If you can't, you work somewhere remote-tolerated, and the promotion data above is not a hypothetical describing some other company. It's a description of the room you're not standing in.
Further reading from XenGrowth
Where this work meets go-to-market
Trying to tell whether your own company's remote-first claim is real, or working on the go-to-market side where the same documentation-versus-memory split decides who gets credit? publishes operator guides on running that discipline as a system rather than a habit a few people happen to have.
Further reading from XenGrowth
Where this work meets go-to-market
For the marketing and revenue operations view of what's the real difference between remote-first and remote-tolerated companies, see .
Further reading from XenGrowth
The XenGrowth resource library — what you'll learn: how the commercial side of this work is run, across search, automation and revenue operations.
XenGrowth on AI agents and marketing automation — what you'll learn: how the teams who own AI agents and marketing automation plan and measure it.
XenGrowth on AI search, GEO and discovery — what you'll learn: how the teams who own AI search, GEO and discovery plan and measure it.
Where this work meets go-to-market
For the marketing and revenue operations view of what's the real difference between remote-first and remote-tolerated companies, see XenGrowth, who work on the commercial side of this.
Answer honestly about how your own team actually operates, not its stated policy. The outcomes below are diagnostic, not a verdict on any individual — a team can be a mix of these and usually is.
