Not All Togetherness Is Created Equal: A Smarter Way to Think About In-Person Work

Let's get one thing out of the way upfront: this isn't another piece about whether remote work is better than office work. That debate, frankly, has run its course. The more interesting question — and the one that's actually actionable for most teams right now — is a lot more specific.

When does physical proximity genuinely help? And when is it just... theater?

Because here's what the last few years of hybrid work research is starting to make pretty clear: the answer depends almost entirely on what kind of work you're actually doing. And most return-to-office policies aren't asking that question at all.

The Blanket Mandate Problem

When major companies started issuing return-to-office mandates over the past couple of years — three days a week, five days a week, whatever the number — the rationale was often the same: collaboration suffers remotely, culture erodes, and innovation needs in-person energy to thrive.

Some of that is true. Some of it is not. And the problem with blanket mandates is that they treat all work as if it belongs in the same category.

A software engineer doing deep, focused architecture work is not doing the same kind of work as a brand team running a creative kickoff. A financial analyst building models is not doing the same kind of work as a sales team that thrives on energy and shared momentum. Requiring both groups to follow identical presence schedules doesn't serve either of them particularly well.

Research from Microsoft's Work Trend Index and studies out of Stanford's Remote Work research group have both pointed toward the same nuanced conclusion: in-person interaction creates real value for specific kinds of collaboration, while actually degrading performance for others. The key variable isn't location. It's the nature of the task.

Where Proximity Actually Earns Its Keep

So when does being in the same room genuinely matter? The evidence points to a few consistent categories.

Early-stage ideation and creative problem-solving. There's something real about the energy of a whiteboard session where five people are physically building on each other's ideas in real time. The spontaneous nature of in-person brainstorming — the half-finished thought someone else grabs and runs with, the sketch that sparks a new direction — is genuinely hard to replicate asynchronously. Research on creative cognition consistently finds that physical co-presence supports the kind of lateral, associative thinking that generates novel ideas.

Relationship building, especially for new team members. Psychological safety — the sense that it's okay to take risks, ask questions, and be honest — develops faster when people have some baseline of face-to-face interaction. For new hires especially, a period of in-person onboarding builds social context that pays dividends for months in remote collaboration.

High-stakes interpersonal moments. Difficult feedback conversations, conflict resolution, and significant team realignments tend to go better in person. The nonverbal communication that happens in a room — the pause, the expression, the physical acknowledgment — carries information that video calls strip away.

Cross-functional alignment. When a project requires multiple teams with different priorities to get on the same page, in-person sessions can compress weeks of back-and-forth into a single productive day.

Where Forced Togetherness Actively Gets in the Way

Now for the part that a lot of return-to-office advocates don't want to sit with: there's a meaningful category of work that is genuinely harmed by mandatory office presence.

Deep focus work. Coding, writing, financial modeling, research, design — anything that requires sustained, uninterrupted concentration suffers in open-plan office environments. The ambient noise, the impromptu drop-bys, the cultural pressure to appear engaged — all of it chips away at the cognitive bandwidth that deep work requires. Multiple studies have found that knowledge workers do their highest-quality focused work at home, precisely because of the reduced interruption load.

Async-friendly execution tasks. Once a project is aligned and underway, much of the actual execution work doesn't require real-time collaboration at all. Requiring people to commute to an office to do work they could do just as well — or better — from their home desk adds friction without adding value.

Introverted processing styles. This one is underappreciated. A significant portion of the workforce generates their best thinking alone, in writing, or after reflection. Mandatory in-person environments can inadvertently privilege extroverted participation styles and disadvantage the people who contribute most powerfully through written communication, async input, and deliberate solo work.

A Framework for Designing Smarter Hybrid Schedules

So what should leaders actually do with all of this? Here's a practical starting point.

Map your team's work by type, not by role. Instead of asking "should engineers be in the office three days a week," ask what kinds of tasks your engineers are doing each week and which of those genuinely benefit from proximity. You might find that one day a month of intensive in-person collaboration sessions serves them far better than three days a week of commuting to sit on video calls.

Design around collaboration events, not attendance schedules. The most effective hybrid teams tend to organize their in-person time around specific high-value moments — the quarterly planning session, the product kickoff, the team retrospective — rather than arbitrary weekly minimums. This gives presence meaning and makes the commute feel worth it.

Protect deep work time explicitly. If you're going to bring people into an office, make sure the office environment actually supports the kind of work you're asking them to do there. An open-plan floor full of people on headphones trying to focus isn't collaboration — it's just commuting.

Ask your team. This sounds obvious, but it's remarkable how rarely it happens. The people doing the work have a pretty clear sense of which parts of their job benefit from being together and which don't. Surveying your teams on this — and actually using the data — tends to produce hybrid designs that people buy into rather than resent.

The Real Goal Isn't Presence — It's Performance

The companies getting hybrid work right aren't the ones with the most sophisticated office redesigns or the strictest attendance policies. They're the ones that have gotten honest about what they're actually trying to achieve and designed their in-person time around that goal.

Spontaneous collaboration is real, and it's valuable. But so is the focused, uninterrupted work that happens when someone is left alone to think. The trick isn't choosing one over the other — it's knowing which one your team needs on any given day.

Proximity is a tool. Like any tool, it works best when you use it intentionally.