intermediate 2 min answer

A distributed engineering organisation makes architectural decisions in meetings and repeatedly relitigates them. What practice fixes this?

vercelwritten-culturedecisionsasyncdistributed
Show the full answer Hide the answer

Why meetings produce relitigation

A meeting produces a shared feeling rather than a shared record. People leave with different understandings of what was decided, the reasoning is not captured, and anyone absent — which in a distributed organisation is most people — has no access to it at all.

Three months later the question reappears, the original reasoning is unavailable, and the discussion starts from the beginning with different participants.

What fixes it

  • A written proposal circulated before the discussion, containing the problem, constraints, options and a recommendation. Reviewers comment asynchronously, which surfaces most objections without a meeting.
  • A meeting only for what writing cannot resolve — genuine disagreement, or a decision needing a conversation — and with the pre-read as the entry condition.
  • A written decision record produced immediately afterwards, including the dissent. The dissent is the most valuable part, because it tells a future reader what to watch for.
  • Decisions indexed by the question they answer, so someone with a question can find whether it has been decided.

The specific advantages for a distributed organisation

Writing is asynchronous, reviewable, searchable and inclusive of people in other time zones. It also imposes a discipline: an argument that survives being written down is usually better than one that survives being spoken, because vagueness is harder to sustain in text.

It scales with organisation size in a way meetings do not. A meeting's cost is linear in participants and its value is not.

The failure mode of written culture

Documents that nobody reads, which is the mirror problem. It is caused by length, by burying the decision being requested, and by circulating without asking specific people for specific input.

A proposal should state the requested decision near the top, be readable in ten minutes with detail in appendices, and name who must respond and by when. Without those three, a written culture produces a large archive and the same relitigation.