Work asynchronously when people can read the same context, think independently, and reply before a clear deadline. Meet when the outcome depends on rapid negotiation, sensitive back-and-forth, or a decision the written discussion has genuinely stalled on.

Some people do their best thinking in a room. Some do it forty minutes later, on a walk, while composing a devastatingly useful reply to a question nobody gave them time to answer.

Make it easy to give a useful written answer

A link and “thoughts?” hand the reader the work of figuring out what matters. A good brief names the question and gives people enough context to answer it. If you need input from several people, ask each for the part they know.

  • Context: What changed, and why does it matter now?
  • Ask: Are you sharing an update, collecting feedback, or asking for a decision?
  • Deadline: When are replies needed, and what happens if no one responds?
  • Owner: Who closes the loop and records what happens next?

Decision needed: pilot the new onboarding email with 10% of signups next week? Please flag any support or reporting risks in the doc by Thursday at noon. I’ll make the call Thursday afternoon and post the decision there.

Know when to switch to a call

If comments are resolving the question, keep writing. If two people disagree because they have different constraints and replies are circling the same issue, invite those two people and the decision owner. Send the thread as the pre-read so the call can pick up where writing stopped.

Then post the result where the discussion started. A teammate should be able to see what was decided, why, and what they need to do without asking for another meeting about the meeting they missed.