Everything you always wanted to know about running Silent Meetings but were too afraid to ask
“There’s nothing I enjoy more than spending time silently typing with you all.”
Preface: I learned how to use silent meetings at Twitter about a year ago and it’s been very useful for most meetings (especially large ones). We’re now expanding it to other parts of the company and I’m sharing what I use in case it’s helpful to others. If you have other suggestions -> reply to this Tweet.
What are Silent Meetings?
“Silent Meetings” are meetings where most of the time is spent working and not talking. When done correctly most of the meeting is spent silently working together.
Is it 100% silent? Not really… A rule of thumb is a silent meeting is where more than 50% of the time is spent silently and the time that is not silent is spent on topics that can’t be resolved through comments in a doc (e.g. coordination problems, difficult conversations).
Where did they start? I’m not sure… but my lineage goes back to Amazon via Square and now Twitter.
Why Silent Meetings?
Silent meetings fix many issues that are common with “loud meetings”:
So how does one have a Silent Meeting?
Before the meeting you’ll need a Google Doc with:
- An agenda that includes:
- Meeting Outcome Statement (i.e.,what do you want the meeting to achieve?)
- Process (“Read doc 20 minutes silently and then discuss for 10”)
- Assigned facilitator
2. The “pre-read”
- The subject matter to be discussed that fits in ½–⅔ of the allotted time
- A good rule of thumb is it should take less than 10 minutes to read in a 30 minute meeting. An x-minute pre-read can grow to 2x if there are lots of comments, so 10 minutes becomes 10 very easily (especially if it’s a controversial topic or if it’s an area that is new to the commenters)
- Note 1: “pre-read” is a misnomer since this is read in the meeting. This is the case because most people don’t have time to pre-read — this also ensures everyone operates from the same base of information. (I believe this is a Jeff Bezos nuance)
- Note 2: Try to include any information needed in the pre-read itself (i.e., avoid using the Appendix, or clicking out to other docs as much as possible since there is leakage)
- Note 3: If a meeting is very large consider breaking up into sections to read-comment. I think optimal reading size per piece is ~20 mins. I’ve done 1 hour per piece and I find people zone out a bit which might be fine for a full day session though.
Then, start the meeting by:
- Pre-reading for the amount of time determined AND commenting in the doc
- Mention that attendees should “Read entire doc before commenting. Often times answers to questions are found later in doc.”
- Readers should then go back to the beginning after finishing to read the comments and reply.
While everyone is reading, the facilitator should:
- Review the comments as they occur and then identify topics that require in person discussion (e.g., identify controversial topics or areas of disagreement and call them out up front if possible)
- Call an end to the silent reading when time is up
- Guide the discussions to the areas identified
- Identify next actions 5 minutes prior to end of meeting and have clear people assigned to each.
- Note: The role of the Facilitator is super important because they need to sort through the comments and guide the discussion. There is such a thing as a skilled facilitator.
When should you use Silent Meetings?
I’m not sure. I’m still learning but here is my rule of thumb:
- More than 10 people? Absolutely.
- More than 6 people? Yes
- 4–6: Maybe
- <4: Maybe?