Remote vs Office

Remote vs Office

July 15, 2026

Engineering

The debate was never about location

Every few months someone declares the remote experiment over. Then a team ships something remarkable from six timezones and nobody mentions it. The truth is less quotable: location was never the variable that mattered. Clarity was. Teams that were vague in an office became invisible remotely. Teams that were sharp stayed sharp.

We run engineering teams across four continents. Here's what actually moved the needle.

What breaks first

Remote doesn't create new problems. It removes the padding that was hiding the old ones:

  • Decisions that lived in someone's head, never written down

  • Status meetings that substituted for actual progress

  • Onboarding that depended on sitting next to the right person

  • Feedback that only happened when someone looked annoyed

Every problem a remote team has, an office team also had. The office was just good at hiding it.

What we changed

Write things down, once. If a decision matters, it goes in a document with the reasoning, not the conclusion alone. The reasoning is what future you needs when the context has evaporated.

Default to async. A meeting is a synchronous lock on four people's calendars. Sometimes that's worth it. Usually it's a document and a day of comments, and the output is better because nobody was performing.

Optimize for the slowest timezone. If a decision needs someone who's asleep, it waits. That sounds slow. In practice it forces the question: did this need to be a decision at all?

The hybrid trap

Hybrid sounds like the reasonable middle. It's often the worst of both, a two-tier team where the people in the room make the real calls and the people on the call receive them. If some of you are remote, act as if all of you are. One person dialing in means everyone dials in.

Where we landed

  1. Hire people who are self-directed and comfortable async, this is a hiring filter, not a training problem

  2. Make writing the default, meetings the exception

  3. Treat every meeting as a bug in your documentation

  4. Spend the office budget on getting people together deliberately, a few times a year

  5. Measure what shipped, never who was visible

The result isn't a team that tolerates remote. It's a team that got better at the things co-location let them avoid and would now be worse in an office.

If you're trying to make this work for your own team, let's talk.