Why we went remote-first

Remote-first is not an office policy with the office removed. It is a decision that the default way information moves is written and asynchronous, and almost everything uncomfortable about it follows from that one change. We build an office suite for teams working this way, and we work this way ourselves, which is a useful source of bias worth declaring up front.

What has to be written down

• Decisions, with the alternatives considered. In an office the reasoning survives in people's memories for a while; remotely it evaporates immediately.
• The current state of anything somebody else may pick up — not a status report, just enough that a colleague is not blocked for a day waiting for a timezone.
• Handovers before absences, written while the context is still boring rather than during the holiday.
• What you are working on, somewhere visible, so coordination does not require a meeting to discover.

Async does not mean slow, and it does not mean silent

Two failure modes, opposite in shape. The first is treating asynchronous as a prohibition on talking: questions that would take ninety seconds on a call get spread over two days of messages, and people conclude that remote work is inherently slower. The second is scheduling so many calls to compensate that the day fragments into gaps too small to use. The usable rule is that anything requiring more than two rounds of clarification should become a call, and anything that is one person telling several others something should never have been one.

The real cost of remote-first is not communication, it is that nothing is observed. Nobody notices you are stuck, nobody sees you working late for a fortnight, nobody catches the thing you misunderstood on day one. That has to be replaced deliberately, and a weekly one-to-one is the cheapest replacement available.

The practices that survive contact with a real week

1. Write the decision down where the work is, not in a chat thread that scrolls away.
2. Default to a shared document over a meeting, and to a meeting over four days of asynchronous confusion.
3. Keep a running note per recurring meeting rather than a fresh page, so history is one scroll away.
4. Set a response expectation — a working day, not an hour — so nobody feels obliged to be permanently online.
5. Name an owner for anything that crosses a timezone, because shared ownership plus distance means nobody.

What we got from it

Mainly the thing we did not expect: writing more made us better at deciding. A decision that has to be written is a decision somebody has to actually hold an opinion about, and the ones that do not survive the writing were usually not decisions at all. That is also why the suite leans the way it does — towards documents, records and registers that outlive the conversation rather than towards ever richer chat.