Async decisions: votes, silence, and deadlines

Deciding something asynchronously takes three written parts: a concrete proposal, a deadline, and a stated default for what happens if people stay silent. Miss any one of the three and the thread does not decide anything; it just discusses until someone books the meeting you were trying to avoid.

Teams spread across time zones already know meetings cannot carry every decision. What fewer teams have noticed is that an unstructured thread cannot either. "Thoughts on switching to the new tool?" posted into a channel is not an async decision process. It is a suggestion box with no bottom.

Propose, do not poll

An async decision starts with someone sticking their neck out in writing: "I propose we do X. Here is why, here are the options I rejected, here is what it costs."

The open-ended version ("what does everyone think about the tool situation?") feels more democratic and performs far worse. It generates opinions rather than positions, and opinions do not converge on their own. Someone still has to synthesize them into a proposal, so the open thread just delays the moment a proposal exists, at the price of forty messages.

Writing the proposal is genuinely harder than opening the poll. That difficulty is the point: it forces the proposer to do the thinking the meeting would have flailed through. The rejected options list matters most, because the first three replies to any proposal are "did you consider Y," and a proposal that pre-answers them survives its comment section.

Silence must mean something, and you pick what

The center of async decision-making is a sentence most people are too polite to write: "If I have not heard objections by Thursday noon, we are doing this."

Silence is the default state of every busy channel. If your process cannot digest silence, it cannot finish, because you will never get eleven explicit yeses from eleven people with different weeks. The consent-by-deadline line converts silence from a blocker into an answer.

Is that fair? Mostly yes, with two honest conditions:

• The window must actually span everyone's working hours, at least one full workday for each time zone touched, more across many zones.
• The blast radius must match the mechanism. Consent-by-silence is for reversible calls. Nobody should discover a reorg happened because they were on vacation during the objection window.

Within those limits, the stated default is kinder than it sounds. It tells everyone precisely what their silence costs, which is more respect than the open-ended thread ever shows.

Votes are for preferences, not for truth

Emoji votes and polls have a real but narrow job: settling questions where the answer genuinely is aggregate preference. Team lunch, meeting time, which of three finished designs ships when they are all fine.

The misuse is voting on questions that have a right answer someone in the thread actually knows. Whether the database migration is safe is not a matter of preference, and putting it to a vote averages the one informed opinion with six uninformed ones. For those questions the async form is different: ask the informed person directly, in public, and give them room to answer at length.

A useful habit for mixed cases: vote to narrow, decide to finish. Let the poll eliminate the options nobody wants, then have the named owner make the final call in a written line with reasons. The poll gathers signal; it does not sign the decision.

Write the ending, loudly

Async decisions fail at the finish more than anywhere else. The deadline passes, the default kicks in, and nobody says so, which means three weeks later half the team believes the question is still open.

The decision needs a closing message with its own weight: "Decided: we are switching, starting the 1st. Objections were raised about export formats; we are handling that by keeping the old tool read-only for a quarter. This thread is closed." Pin it, or move it to wherever your decisions live. The thread that produced the decision is a working document; the closing message is the record, and the record is the part people will search for.

Unwritten endings are how the same decision gets made three times. If your team keeps re-litigating settled questions, the problem is usually not disagreement. It is that the settlement was never announced as one.

What async cannot decide

Some disagreements should not be settled in a thread, and pretending otherwise burns people. When two colleagues have argued past each other in eight polite paragraphs each, the disagreement is usually not about the stated topic anymore. Values conflicts, trust gaps, and anything with heat in it want a live conversation, where repair happens at the speed of talking.

The tell is repetition: when the same position gets restated a third time in new words, writing has done all it can. Name it and move: "We are going in circles; fifteen minutes tomorrow?"

The written proposal still matters even then, because both people arrive having read the same document instead of having imagined each other's positions. When I need a proposal like that to hold up, the last thing I do is run the tense sentences through a calmer rewrite before posting, because a proposal that sounds irritated collects objections to its tone instead of answers to its question.