Key takeaways
- →Falling attendance is not an engagement problem to solve with reminders - it is feedback that the last few sessions were not worth the time.
- →Cap the meeting at three messages people could repeat afterwards; anything else belongs in a written update.
- →Collect and upvote questions in the 48 hours beforehand so the Q&A opens with what the company actually wants to know.
- →Answer the hardest upvoted question first, while attention is highest and before people start drifting to other tabs.
- →Say 'I do not know' or 'I cannot say yet, and here is why' plainly - evasion costs more credibility than the answer would.
- →Send a recap within a day covering every question asked, including the ones there was no time to answer live.
An all-hands meeting earns attendance when people leave knowing three things they did not know before and having heard a real answer to a question they actually cared about. That is the whole test. If your attendance is sliding, the reminders and the calendar-blocking are treating a symptom - people are voting with their diaries on the last four sessions, and they are usually right.
The typical failure is a session that is structurally a broadcast: forty minutes of department updates read from slides, five minutes of 'any questions?' answered by the same two extroverts, and a close that runs three minutes over. Nobody objects to it. Nobody remembers it either, and within a quarter the optional attendees have quietly stopped coming.
This guide covers a forty-five minute structure, how to cut an agenda down to three messages, collecting and upvoting questions in advance, answering the difficult ones without damaging trust, adapting the format for a distributed company, and how to tell whether the last one worked before you plan the next.
What an all-hands is actually for
It has exactly three jobs that no other channel does as well. It gives the whole company the same picture at the same moment, which stops six departments building six slightly different versions of the strategy. It lets people ask leadership something directly and watch the answer land. And it produces a shared reference point - 'as we said at the all-hands' - that makes the next three months of decisions easier to explain.
Notice what is not on that list: status reporting. A round of departmental updates is the single most common way an all-hands gets padded to an hour, and it is almost always better as a written summary. Reading out what each team shipped is comfortable for the presenters and low value for the four hundred people who care about roughly one of those teams.
The other thing an all-hands is not is a morale event. You cannot make people feel good about a difficult quarter by putting an upbeat slide in front of them; the room can tell. What actually builds confidence is watching leadership take an uncomfortable question and answer it without flinching, which is why the Q&A is the part that deserves protection when the agenda runs long.
The forty-five minute shape
Forty-five minutes is the right default for a monthly all-hands at almost any company size. An hour invites padding, and the last fifteen minutes of an hour-long broadcast are attention nobody is really giving you. Under half an hour and the Q&A gets squeezed into a token five minutes, which is worse than not having one.
Inside that, run roughly five minutes of opening and a live pulse question, twenty minutes on the three messages, fifteen on Q&A, and five to close with what happens next. The proportions are the point: the parts where the company hears itself - the pulse check and the questions - take almost half the session.
Protect the Q&A ruthlessly. When the agenda overruns, the instinct is to cut questions because the presenters have already prepared their slides. Cut a message instead. A message can be written down and sent; the Q&A cannot be, because its value comes from happening in public.
Cut the agenda down to three messages
Start from the end. Write the three sentences you want a randomly chosen employee to be able to say the next morning if a colleague asks what the all-hands covered. If you cannot get the list to three, you do not have an agenda problem - you have a prioritisation problem, and pushing it into the meeting just moves it to four hundred people at once.
Each message needs three components: what changed, what it means for the people listening, and what happens next. Most all-hands slides carry the first and skip the second, which is why a genuinely important announcement can land as background noise. 'We closed the funding round' is information. 'We closed the round, which means the hiring freeze in support lifts next month and here is who to talk to' is a message.
Everything that does not make the three goes into a written update sent beforehand. This is not a demotion - it is the correct channel. Written updates are searchable, skimmable, and can be read at whatever depth each person needs. A slide read aloud is the least efficient way to deliver detail ever invented.
What earns a slot
Two categories consistently fail to earn a slot and consistently get one anyway. The first is the department round-robin, where eight teams each get four minutes because it would be awkward not to. The second is the strategy recap that has not changed since last quarter - repeating an unchanged strategy trains people that the session contains nothing new.
If leadership visibility is the real reason a department wants stage time, there are cheaper ways to get it. Rotate a single five-minute deep dive from one team per session, chosen because the work is genuinely interesting to everyone rather than because it is their turn. One good five-minute story beats eight dutiful updates.
Collect questions before the meeting, not during it
The reason to collect in advance is not preparation time, though that helps. It is that 'any questions?' in a room of two hundred is a social trap: asking one publicly signals that you have an opinion, and the cost of that varies wildly by seniority, tenure and confidence. Written submission with upvoting removes that cost, and the questions get sharper for it.
Session Flo handles this pattern directly - an open question board with upvoting and optional anonymity, run from the same room code as the pulse poll at the start - so the ranked list is on screen while you answer rather than in someone's inbox.
Open the question box 48 hours ahead
Two days is long enough for people to think of something real and short enough that the questions still reflect what is on people's minds. Announce the window in the same message as the agenda, so it looks like part of the meeting rather than an afterthought.
Let people upvote as well as submit
Upvoting turns a scattered list into a ranked one and tells you what the company actually cares about, not what the three most confident writers care about. It also means someone who was too nervous to ask can still push a question to the top.
Allow anonymous submission, and say so plainly
The questions worth having are the ones people would not put their name to. Say the word anonymous out loud rather than relying on the interface to imply it, because people assume the worst about anonymity unless told otherwise.
Publish the ranked list before the session
Sharing the top questions an hour beforehand does two things: it proves nothing was quietly removed, and it stops people spending the presentation drafting a question that is already at the top of the list.
Answer the hardest one first
Take the top-voted question immediately after the three messages, while attention is still high. Saving the awkward one for last, when time is short, is transparent and reads as avoidance even when it is not.
Keep a live channel open too
Pre-submitted questions cover what people knew to ask. Something in the presentation will prompt new ones, so keep submissions open during the session and reserve the last few minutes of the Q&A for the live ranked list.
Answering questions without damaging trust
The Q&A is where an all-hands is won or lost, because it is the only part the audience cannot predict. People are not primarily assessing whether the answer is good news. They are assessing whether it is a real answer, and they are very good at spotting the difference between 'I cannot tell you yet' and a paragraph of words arranged to look like a response.
Three answers are always available and always acceptable: here is the answer; I do not know and I will find out by Friday; and I know but I cannot say yet, and here is the reason. The third one is used far too rarely. 'That is decided but not announced to the affected team yet, so I am not going to say it here first' is a completely satisfying answer to almost everyone, and it costs nothing.
What does damage is the non-answer that pretends to be an answer. If a question about redundancies gets a reply about how much the company values its people, everyone in the session has now learned two things: the answer is bad, and asking directly does not work. The next question box will be emptier, and the drop-off will look like disengagement rather than what it is.
People do not turn up for the announcements. They turn up because last time someone asked the difficult question and got a straight answer in front of everybody.
Handling the questions you would rather not have
Assume that anything you decline to discuss will be discussed anyway, in smaller rooms, with less information. The choice is not between addressing a difficult topic and avoiding it - it is between addressing it once with accurate detail or having six teams reconstruct it from fragments over the following fortnight.
One structural safeguard: have someone other than the presenter watch the incoming question list during the session. A presenter mid-slide cannot track a board that is moving, and the moderator's job is to spot the question that has just jumped to the top because of something that was said thirty seconds ago.
Never skip a top-voted question
If the highest-voted question goes unread, everyone notices, and the credibility of the whole format goes with it. Read it out as written, even if the answer is that you cannot answer it today.
Read hostile questions verbatim
Softening the wording of a sharp question is visible to the person who wrote it and to everyone who upvoted it. Read it as submitted, then answer the substance rather than the tone.
Give a date, not a promise
'We will look into it' is where questions go to die. 'I will have an answer for you at the next all-hands on the fourteenth' is checkable, and being checked is the point.
Group the duplicates out loud
When six versions of the same question appear, say so before answering: 'six people asked about the hiring freeze.' It tells the company what the company is thinking, which is information in itself.
Let the right person answer
A chief executive answering a detailed engineering question badly is worse than handing it to the person who knows. Pre-assign the top five questions to whoever can actually answer them.
Close the loop on unanswered ones
Every question that did not get airtime gets a written answer in the recap. This single habit does more for the next session's submission rate than any amount of encouragement.
Running an all-hands for a distributed company
Rotate the time slot rather than fixing it around headquarters. Two alternating slots covering different halves of the day, or a monthly rotation, spreads the inconvenience instead of concentrating it on the same region every time. It costs the organisers a little planning and buys a lot of goodwill from the people who have been joining at ten at night for two years.
Treat the recording as a second-class experience and design around it. Asynchronous viewers cannot ask, cannot upvote and cannot read the room, so give them a written question route that stays open for twenty-four hours afterwards with answers appended to the recap. Otherwise, the people watching the recording are structurally excluded from the only interactive part of the session.
Above roughly two hundred attendees, separate the channels. Chat is for reactions and side conversation; the question board is for questions, ranked and moderated. Merging them means good questions scroll past in ninety seconds, and the moderator ends up picking whatever they happened to see.
✓ Pros
- •One live session keeps the whole company on the same page at the same moment
- •Questions and answers happen in front of everyone, so nothing is second-hand
- •A single recording plus recap is far cheaper to produce than repeated sessions
- •Live participation data tells you immediately which regions are drifting away
- •One shared reference point makes the following months of decisions easier to explain
✗ Cons
- •Somebody always joins at an antisocial hour unless you rotate the slot
- •Recording-only attendees cannot ask questions in the moment
- •A single time zone anchor quietly signals whose hours count as normal
- •Very large sessions push the Q&A towards broad questions and away from specifics
- •Chat and questions in one channel become unreadable above a few hundred people
Getting people to attend without mandating it
Top Tips
- Start on time and finish early at least sometimes. A session that reliably ends at forty-two minutes builds more goodwill than one that reliably ends at fifty-one, and people schedule around it differently.
- Put one thing in the agenda notice that can only be got by attending live - a decision being announced, a question being answered, a number being revealed. If everything is equally available in the recording, the recording is the rational choice.
- Ask for a live contribution in the first three minutes. A single pulse question that everyone answers converts passive viewers into participants before the first slide, and gives you a number to open with.
- Publish the agenda and the ranked questions in advance. People decide whether to attend based on whether it looks relevant, and a title like 'Monthly All-Hands' tells them nothing.
- Never open with an apology for the length or a run-through of housekeeping. The first ninety seconds should contain actual information, because that is when people decide whether to keep the tab in focus.
- Stop running it monthly if there is not enough to say. A genuinely useful all-hands every six weeks beats a padded one every four, and cancelling one because there is no news builds more credibility than filling it does.
How to tell whether it worked
Attendance is a lagging indicator and a blunt one, especially where attendance is expected. Better signals are available inside the session itself. Track how many questions were submitted, how many distinct people submitted them, and what proportion of attendees responded to the live pulse question. A question count that halves over three sessions is telling you something long before the calendar acceptances do.
Ask one closing question every time, in the last minute, and keep it identical: 'did you learn something today you did not know this morning?' A single consistent question tracked over a year is worth far more than a detailed survey run once. Detailed surveys about internal meetings get a low response rate, and the people who answer are not a representative sample.
The strongest test is a fortnight later. Pick three people at random and ask what the last all-hands covered. If they can name one of your three messages, the format is working. If they remember the meeting happened but not what was in it, you delivered updates rather than messages, and the fix is cutting the agenda rather than improving the slides.
Watch the sessions people remember, too. What tends to stick is the peak moment and the ending - the difficult question answered squarely, or the closing line that named what happens next. A session that trails off into 'right, that is us, thanks everyone' wastes the most memorable slot in the whole forty-five minutes.
The twenty-four hours afterwards
Send the recap within a day, while the session is still live in people's heads. It needs four things: the three messages in one line each, written answers to every question that was not reached, the named owner and date for anything promised, and the recording link. Anything longer than a screen will not be read.
The unanswered questions section is the part that compounds. People who submitted something and got a written answer a day later will submit again next month; people whose question vanished will not. This is the single strongest lever on the quality of your next Q&A, and it costs an hour of somebody's afternoon.
Then carry the commitments forward. Anything you promised to answer 'by the next one' goes at the top of the next agenda, answered before the new material starts. A company that watches leadership open with 'last month I said I would find out about X, here is the answer' learns that this session is a place where things get resolved - and that, rather than any amount of promotion, is what makes people show up.
Frequently asked questions
How long should an all-hands meeting be?
Forty-five minutes is the right default for a monthly session at almost any size. An hour invites padding and the final quarter is attention you are not really getting. Split it roughly into five minutes of opening and a pulse question, twenty on your three messages, fifteen on questions and five to close. If you consistently cannot fill forty-five minutes with things worth saying, run it every six weeks instead of shortening it.
How often should you run an all-hands?
Monthly suits most companies above about fifty people, with quarterly deep dives around planning cycles. Weekly is almost always too often - the agenda gets padded with status updates and people learn the session is skippable. If you are cancelling regularly for lack of content, move to a six-week cadence deliberately rather than running thin sessions and letting attendance decay on its own.
Should all-hands questions be anonymous?
Yes for submission, with upvoting visible. The questions worth answering are usually the ones people would not attach their name to in front of the whole company, and anonymity costs you very little - a moderator can still decline anything abusive. Say the word anonymous explicitly when you open the window, because people assume attribution unless told otherwise, and one careless comment about tracing a question will empty the box for a year.
What do you do when nobody asks a question?
Almost always this is a collection problem rather than a curiosity problem. Open a written question window forty-eight hours in advance with upvoting and anonymity, and seed it with two or three real questions leadership has genuinely been asked in corridors. If the box is still empty after that, the message is that people do not expect a straight answer, and the fix is in how the last few difficult questions were handled.
How do you run an all-hands across time zones?
Rotate the slot rather than anchoring it to headquarters, using two alternating times or a monthly rotation so the same region is not always joining late. Keep a written question route open for twenty-four hours after the session so asynchronous viewers can still ask, and append those answers to the recap. Treat the recording as a designed experience rather than a byproduct, because for distributed companies it is how a large share of people attend.
Should department updates be part of the all-hands?
Rarely. A round-robin of team updates is the most common way a session gets padded to an hour, and most of it is irrelevant to most of the audience. Put updates in a written pre-read and use the live time for direction changes, decisions that alter how people work, and questions. If departments want visibility, rotate one five-minute deep dive per session, chosen because the work is interesting rather than because it is that team's turn.
Keep reading
- running a town hall for a distributed company — The time zone, recording and regional questions in more depth.
- running a Q&A without awkward silence — How to fill an empty question box and keep the ranked list moving.
- facilitating a session for more than a hundred people — What changes structurally once the room is too big for open discussion.
- measuring whether a meeting actually worked — The in-session signals worth tracking instead of attendance.
- see what running large sessions costs — Question boards, upvoting and pulse polls for company-wide sessions.