Thread by @petergyang

How to make great decisions async and save yourself and your team from drowning in a calendar like this:

1/ Loop in the right people

Every decision should ideally have one decision maker and fewer than five stakeholders to provide input.

Avoid too many cooks in the kitchen.

2/ Give context

Write a decision doc with:

1. List of people involved
2. Context
3. Recommendation (don't bury the lede)
4. List of options with pros and cons

3/ Keep the discussion in one place

Pick one channel or doc for people to provide input.

Avoid starting a bunch of separate threads and then having to play a game of telephone to figure out who said what.

4/ Push for a decision

When it looks like people are reaching alignment, the decision maker should push for consensus or "agree to disagree".

5/ Document and share the decision

Once confirmed, share the decision far and wide so that everyone is on the same page.

6/ To recap:

1. Loop in the right people
2. Give context
3. Keep the discussion in one place
4. Push for a decision
5. Document and share the decision

Check out my post with @bkaneMN for an example of this process in action:
async.twist.com/how-to-make-de…

7/ Here's another trick to make your teammates feel better (j/k don't do this):

8/ If you found this helpful, follow me @petergyang for more.

Back to the top:

9/ If you're a new or aspiring PM, check out my upcoming live PM course that covers great communication and other topics like this.

Use the code EARLYBIRDPM to get $100 off:
maven.com/peter-yang/lau…