Skip to content

People ops · 3 min read

Staying human at a distance

Remote kills the hallway, so we rebuild connection on purpose, without forcing fun.

Remote work is worth it. But it takes something real, and pretending otherwise is how remote teams end up as a group of strangers who happen to share a repo. The thing it takes is the hallway. In an office, connection is a byproduct: you bump into people, overhear a joke, get coffee, learn that the person three desks over is a person. Remote deletes all of that by default, so we put it back deliberately. Doing it deliberately is the part that matters.

The hallway doesn't come free anymore

In an office you'd have to actively work to avoid ever talking to a colleague as a human. Remote flips the effort: now you have to actively work to talk to one. Left alone, remote optimizes ruthlessly for tasks. Every interaction becomes a ticket, a review, a thread with a purpose, and the low-stakes human stuff that makes a team feel like a team never happens, because nothing schedules it.

That's not a people problem or a culture problem. It's a structural fact about the medium, and the fix is structural too: if connection won't happen by accident, we make a little room for it to happen on purpose. Not a lot. Just enough.

What we actually do

A few deliberate, low-pressure things. All optional, none of them mandatory fun:

  • Coffee chats. A short, no-agenda call with someone, sometimes randomly paired, sometimes because you've been meaning to. The rule is there's no rule: talk about the work, or don't. The point is to know the person behind the pull requests.
  • Show-and-tell. A standing, casual slot to show something you made, a thing you learned, a side project, a rabbit hole you fell down. Half of team culture is just watching each other be curious out loud.
  • A channel for none of it. A place that is explicitly not about work: the dog, the terrible weather, the thing you're cooking, the game you can't stop playing. It sounds trivial. It's load-bearing.
  • Celebrating wins, out loud. When something ships or someone pulls off something hard, we say so where everyone can see it. Remote makes wins easy to miss, because there's no room that spontaneously claps. So we clap on purpose.

No mandatory fun

Everything here is an invitation, not attendance. The fastest way to kill real connection is to require it and put it on a calendar with a mandatory flag. Forced fun isn't fun, it's a meeting wearing a party hat. Show up because you want to, skip it when you don't, and no one's counting.

Where it gets hard

This is harder at our size, not easier. A big company can spin up a dozen affinity groups and a full-time culture team. We can't, and won't pretend to. When the crew is small, one person having a rough month or just being heads-down is enough for a couple of these rituals to quietly go quiet. There's no crowd to carry the energy. It takes real individual effort, from people who'd often rather just keep working.

We think that effort is worth it, and we'd rather admit it's effort than sell you a frictionless "culture" that runs itself. It doesn't. Someone has to start the coffee chat, post in the not-work channel first, notice the win and say it out loud. Sometimes that someone is you, and the small act of starting it is most of the job.

The payoff is a team you'd actually want to work with for years, one where directness lands as care instead of coldness, because you know the person on the other end. A lot of this handbook depends on that: the async distance, the blunt feedback, the communication norms. None of it survives between strangers. So we keep the strangers from forming, one slightly awkward hallway moment at a time.