Async decision-making frameworks: when a doc beats a meeting, and when it doesn't

The pendulum on async work has swung wildly in the last decade. In 2018 the cure for meeting fatigue was "kill the meeting, write a doc." In 2022 the cure for doc fatigue was "stop writing essays, get on a call." Neither was wrong. Both were applied as universal rules when the actual question is a sequencing one.

Some decisions need a doc. Some decisions need a meeting. Most decisions need both, in the right order, and the order is the part teams get wrong.

A decision needs a meeting when it has live trade-offs that only surface in real-time pushback. The architect who realizes mid-conversation that the proposed approach blocks a migration she has scheduled for next quarter, that's a meeting moment. The exec who shifts the strategy based on a question another exec raised three minutes earlier, that's a meeting moment. Synchronous discussion produces insights that no amount of writing can simulate, because the insight depends on what just got said in the room.

A decision needs a doc when the trade-offs are knowable in advance and the inputs are scattered across the team. The roadmap prioritization where engineering, design, customer success, and leadership each see one slice of the picture, that's a doc moment. The hiring decision where five reviewers each ran one part of the interview loop, that's a doc moment. Asynchronous gathering produces a complete view that no meeting can match, because the picture is built from inputs nobody has time to recite in a synchronous slot.

The mistake most teams make is collapsing both phases into one meeting. The roadmap review becomes a context-gathering session followed by an exhausted attempt at decision. The hiring debrief becomes a recap followed by a vote nobody had time to think through. The cost of that collapse isn't the time. It's that the decision gets made by whoever had the most context coming in, which is usually whoever called the meeting.

The framework that works: gather async, decide sync. The doc collects the inputs. The meeting consumes the doc and runs the trade-offs. Every cross-functional decision benefits from both, but only if the doc gets written before the meeting starts, not summarized inside it.

The teams that do this well don't have fewer meetings. They have sharper ones. The roadmap review opens with the four themes already surfaced. The hiring debrief opens with the five reviewers' takes already on the table. The first ten minutes of the meeting is the real conversation, not the catching-up.

If your next decision is on the calendar this week, the test is simple: what would the doc say, if someone wrote it before the meeting? If you can answer that, you have a meeting. If you can't, you have a context-gathering session pretending to be one.