How to Make Great Decisions Async and Avoid Endless Meetings
How to Make Great Decisions Async and Avoid Endless Meetings
Most decisions can be made async. Follow these five steps to do it effectively.
Join 38,000+ others who get my best writing and interviews on how to level up your product skills and build a thriving creator business.
Dear subscribers,
Today, I want to share my advice on how you can make great decisions async.
If you learn how to do this well, you’ll save your team from endless hours of meetings and they’ll love you for it.
Here’s my 5-step process:
Identify key people
Set context
Use one channel for communication
Use numbered lists for discussion
Push for a decision and share it broadly
This post is brought to you by…Vowel
Vowel uses AI to summarize notes and action items that you can then easily share via Slack or email. That platform also includes transcripts, recordings, and clips by default. Here’s a quick video demo to see it in action - it’s quite magical!
Click the link below to try it out yourself for free:
1. Identify key people
Every decision should ideally have one decision maker and fewer than five stakeholders to provide input. Avoid having too many cooks in the kitchen.
2. Set context
The decision maker should create a decision doc with:
List of people involved
Context
Recommendation
Options considered with pros and cons
Nobody has time to read long docs, so try to be as concise as possible.
3. Use one channel for communication
Ask people to provide input in the decision doc or in one Slack channel.
Avoid starting a bunch of separate threads and then having to play a game of telephone to figure out who said what.
4: Use numbered lists for discussion
In the decision doc, ask people to discuss async using nested numbered lists. This helps keep things organized (think of it like a Reddit comment thread). Here’s an example:
Discussion:
Peter: I like option B because of XYZ.
Daniel: I hadn’t thought of it that way, let’s proceed.
5. Push for a decision
When it looks like people are reaching alignment, the decision maker should push for a decision:
"It sounds like people prefer #1, any strong objections to moving forward?"
Once confirmed, share the decision far and wide so that everyone is on the same page.
To recap, the steps are:
Identify key people
Set context
Use one channel for communication
Use numbered lists for discussion
Push for a decision and share it broadly
If you do the steps above, you’ll be able to make great decisions async and only schedule meetings when absolutely necessary. This is a much better way to make your coworkers feel better than the following:
Of course, sometimes a decision does require a meeting. Usually, it’s when:
A decision has a lot of ambiguity
A decision is a one way door (hard to reverse)
Your decision doc has a lot of discussion without consensus
I’ll cover how to run meetings that don’t suck in my next post.
A version of this post was first published on the async newsletter.
The 2nd point you said about setting the context was the best one. A lot of confusion and misinterpretations can be solved by setting a concise context as you said.