Does the research say remote work is more or less productive?

It depends on which work. Nicholas Bloom's randomized studies found clear productivity and retention gains for remote and hybrid work on individual, measurable tasks. But the same body of research raises concerns about the harder-to-measure parts — mentorship, onboarding juniors, weak-tie trust, and innovation — which tend to benefit from being in the same room. 'More productive' and 'less productive' are both true, of different things.

Why do return-to-office mandates cause so much conflict?

Because the stated reason (collaboration) and the felt reason (control) often diverge. When a blanket mandate ignores that focused work usually goes better at home, employees read it as 'we don't trust you to work unless we can see you.' The fight stops being about output and becomes about trust, which no productivity study can settle.

What should companies actually decide?

Not a single number of office days for everyone. Which specific tasks and which career stages need co-location, and how often. A new hire learning the ropes and a senior individual contributor doing deep focused work have opposite optimal answers, and a blanket policy gets at least one of them wrong.

THE CRUX · NO. 03 · UNDERSTANDING EACH OTHER

REMOTE WORK vs. THE OFFICE

The boss says come back for the collaboration. The team says they get more done at home. They're both telling the truth, because they're measuring two different kinds of work and calling both of them 'productivity.'

By Jared Ohman June 29, 2026 7 min read

The fight as stated

The email lands on a Tuesday: everyone back in the office, three days a week, starting next month. The team reads it as a punishment for two years of doing the job fine from home. Leadership reads the pushback as proof that people got too comfortable.

That's the fight. One side says presence is how a company actually works: the hallway conversation, the junior who learns by watching, the trust you build sharing a room, the fast loose coordination that email turns to mud. The other side says they ship more from a quiet desk with no commute and no open-plan interruptions, that talent is everywhere now, and that dragging people back is about control and empty real estate, not results. One hears: you're hollowing out the company. The other hears: you don't trust me to work.

Each side, steelmanned

Each side in its own language, made strong enough to recognize.

The office camp

Some of the most valuable work a company does never shows up on a task tracker. A junior becomes good by overhearing how a senior handles a hard call. Trust between people who barely know each other gets built in passing, not in scheduled video calls. The loose, ambiguous, fast coordination that solves novel problems happens when bodies are in the same space. Remote can look fine this quarter while quietly starving the connective tissue that pays off in three years.

The remote camp

Focused, individual work measurably improves without a commute and an open-plan room full of interruptions. Autonomy and trust are what actually drive engagement and retention, and the research bears it out. The talent pool stops being a 30-mile radius. And a lot of return-to-office is a manager's comfort and a landlord's lease dressed up as strategy. Forcing presence to feel in control is not the same as producing results.

Both of those are true. They're just true about different parts of the work.

The actual crux

Underneath, the agreement is most of the picture. Both sides want the company to do well and want people to have lives worth living. Both, pressed honestly, would admit some work is better done alone and some is better done together. Nobody's real ideal is an empty culture, and nobody's real ideal is a commute for the sake of being seen.

So the fight is not "remote: good or bad." The word in the middle is broken.

"Productivity" means two different things here. One is individual, measurable output, the tickets closed and the docs written, which usually goes up with focus and quiet, often at home. The other is collaborative and developmental value, the mentorship, the weak-tie trust, the serendipity, the culture, which usually goes up with proximity. They respond to location in opposite directions, and "productivity" hides that they're not the same thing. That's the load-bearing belief. If the valuable work is the part you can count this quarter, remote wins on the merits. If the valuable work is the part you can't easily count, presence has a real case. Most fights are two people each defending the half they can see.

The evidence fits this shape. Nicholas Bloom's randomized work-from-home studies found solid gains in output and retention on individual tasks, while the same literature flags the costs that land on the uncountable side: slower mentorship, harder onboarding, thinner innovation. Neither headline ("remote is more productive," "remote is killing us") is wrong. They're answers to different questions.

The costume check

This argument wears a spreadsheet. "Studies show productivity went up." "Studies show collaboration collapsed." Strip the costume and three things are tangled.

A definition split wearing a data war. Most of the disagreement is two people using "productivity" for different work and each citing the real evidence for their half.

A genuinely mixed empirical question. The right answer depends on the task, the tenure, and the team. Deep individual work and a new hire's first six months have opposite optimal setups. Anyone claiming the data clearly settles it for everyone is flattening a result that was never flat.

A trust question wearing the data. Underneath a lot of return-to-office is a quieter claim: presence is how leadership knows you're committed. And underneath a lot of remote advocacy is a quieter claim: measure my output, not my chair. That's a fight about trust, not minutes, and it's the one that actually generates the heat.

What survives

Take the costume off and the shared ground is large.

Both sides want results and the harder-to-measure human capital that produces future results. Both, if the question is put cleanly, would agree that a senior doing deep focused work and a junior trying to learn the job should not be handed the identical policy. That's not a deadlock. That's the design problem hiding under the shouting.

What's left to disagree about is honest and specific: which tasks and which career stages actually need the room, and how often. That's answerable team by team, role by role, in a way a blanket five-days or fully-remote edict never could be. Stop arguing the number of days. Argue which work needs which mode, and the trust question gets to come out from behind the spreadsheet where it can actually be addressed.

Because the common ground was never going to be a universal office schedule. It was admitting that "productivity" was carrying two arguments at once. Find that, and you've found the crux.

— The moves behind this —

The Crux runs two methods on one real disagreement. Want to run them yourself?

The Disagreement Cartographer → The Worldview Translator →

— Where this comes from —

The productivity-and-retention gains for remote/hybrid work on individual tasks come from Nicholas Bloom's research at Stanford, including the randomized work-from-home experiment first run with Ctrip and his later hybrid studies. The countervailing concerns — mentorship, onboarding, weak-tie trust, and innovation benefiting from proximity — are drawn from the same and adjacent organizational-behavior literature, and remain genuinely contested and job-type dependent. The "presence as a proxy for trust" lens is standard in management research on monitoring and autonomy. This is a map of a disagreement, not a recommendation for your company's policy.

The office camp

The remote camp

Get the next Crux.