An all-hands meeting has a specific failure mode, and almost every company that runs them eventually hits it. Leadership talks for 45 minutes, then opens the floor, and gets silence, or a question from the same confident person who always asks something, while everyone else's actual questions go unasked. The content half of an all-hands is usually fine, it's the participation half that breaks. This guide covers a working agenda structure and, more importantly, how to run the Q&A so people with real questions actually ask them.
What is an all-hands meeting for?
An all-hands meeting exists to close the information gap between leadership and the rest of the company, on strategy, performance, and priorities, and to give the team a direct channel to ask about it. It's not a status update dressed up as a meeting; if the content could just as easily be an email, it probably should be one. The parts of an all-hands that justify a live, synchronous meeting are the parts that benefit from being live: context that needs explaining, not just stating, and questions that need a real answer, not a FAQ doc. Everything else, metrics, announcements, hiring updates, works better as pre-read material sent before the meeting, so the live time can be spent on discussion instead of a slide read-through.
A working all-hands agenda
Company update (10–15 min)
Key metrics, wins, and challenges since the last all-hands. Keep this tight, send the detailed version as pre-read and use the live time to add context and answer the "why" behind the numbers, not just present them.
Strategic focus (10 min)
What the company is prioritizing next, and why. This is the section most likely to generate real questions, so don't rush it to make room for more updates elsewhere.
Team/department spotlight (5–10 min)
Rotate which team presents a recent win or project. Keeps the meeting from being entirely top-down and gives visibility to work that doesn't otherwise reach the whole company.
Q&A (15–20 min, protected)
This is the section that gets cut first when earlier sections run long, and it shouldn't be. Treat the Q&A time as fixed, if the earlier sections are running over, cut content there, not here.
Put the Q&A time on the agenda with a specific clock, not "time permitting." A protected block signals that leadership actually wants the questions, not that it's an afterthought.
Running a Q&A that actually gets questions
Open-mic Q&A in a large, recorded, company-wide meeting has a strong chilling effect, even people with a genuinely important question will often stay quiet rather than raise it in front of everyone with their name attached. The fix is to collect questions in advance, anonymously, in a shared queue that team members can upvote. This does three things: it surfaces the questions the team actually wants answered (not just whoever happens to unmute first), it gives leadership time to prepare a real answer instead of an off-the-cuff one, and it removes the social cost of asking something pointed. Leave 5 minutes of genuinely live, unscripted Q&A at the end for anything that comes up in the moment, but let the pre-submitted, upvoted queue drive most of the section.
Running an all-hands with a remote or hybrid team
Remote attendees are structurally at a disadvantage in a live Q&A, they're competing with in-room body language cues (raised hands, eye contact) that don't translate over video. An anonymous, async question queue levels this automatically, since submission happens the same way regardless of where someone is sitting. Send the pre-read materials at least a day in advance across time zones, and if your team spans more than a couple of time zones, consider recording the meeting and collecting a second round of async questions afterward for anyone who couldn't attend live. A Chooseday poll works well for both stages, an anonymous, upvoted question queue before the meeting, and a quick pulse-check poll after ("did this answer your question about X?") to confirm the follow-through actually landed.
Frequently asked questions
An all-hands meeting (also called a town hall) is a company-wide meeting, typically held monthly or quarterly, where leadership shares updates on company performance, strategy, and priorities with the entire team at once. It's distinct from a department meeting in scope (everyone attends) and from a one-off announcement in cadence (it's recurring). The best all-hands meetings are two-way: leadership shares information, but the team also gets a real chance to ask questions and raise concerns.
Most effective all-hands meetings run 30–60 minutes. Beyond an hour, attention drops sharply, especially in a remote or hybrid format where people are one tab away from disengaging. If you have more content than fits in that window, cut it, not the Q&A. The Q&A is usually the highest-value part of the meeting and is the first thing that gets rushed when the agenda runs long.
Collect questions in advance, anonymously, rather than relying on people to unmute and ask live. Live Q&A in a large, hierarchical meeting has a strong chilling effect, most people won't ask a pointed question with their name and face attached in front of the whole company. An anonymous, pre-submitted question queue (upvoted by the team so the most-wanted questions surface first) consistently produces sharper, more honest questions than an open mic.
Monthly is the most common cadence for companies under a few hundred people; quarterly is common for larger organizations where a monthly cadence doesn't leave enough new material. What matters more than frequency is consistency, a predictable, recurring slot that people can plan around builds the expectation that leadership will show up and answer questions regularly, not just when things are going well.
Yes, "town hall meeting" and "all-hands meeting" refer to the same format, a company-wide meeting where leadership shares updates and takes questions from the whole team. The terms are used interchangeably; some companies favor "town hall" specifically because it emphasizes the two-way Q&A element over the one-way "all-hands" framing.