Running the meeting4 min read16 September 2026
All-hands meeting agenda
A good all-hands does one hard thing: it tells people something they did not already know, including when the news is bad. Everything else — the numbers, the demo, the welcome — is structure around that. Forty-five minutes is enough, and the running order below reserves a third of it for questions, because the Q and A is the part people judge the whole meeting by. A meeting that is thirty-eight minutes of presentation and a limp "any questions?" at the end teaches people the Q and A is decorative, and they stop preparing for it.
The running order
Times are minutes, not clock times. The two items people cut when it overruns — the recognition and the Q and A — are the two that should be protected.
[2 min] The one message
Open by saying the single thing you want everyone to leave with, in one sentence, before any context. If you cannot write that sentence, the all-hands is not ready. Repeat it at the close — the opening and the close are the two moments with full attention.
[8 min] Where we are, honestly
The numbers that matter, the same ones every time so the trend is visible, and a plain statement of whether the picture is better or worse than last month. Changing which metrics you show is read, correctly, as choosing the flattering ones.
[10 min] The thing that changed
One substantive item per all-hands: a strategy shift, a launch, a reorganisation, a loss. Presented by whoever actually owns it, not relayed by a communications function. A relayed message cannot answer the follow-up, and the follow-up is the whole point.
[5 min] Something real being shown
A demo, a customer call clip, a piece of work someone shipped. Presented by the person who made it. This is the item that makes an all-hands feel like a company rather than an announcement, and it is worth protecting even in a hard week.
[5 min] Named recognition
Two or three specific people, with what they did and why it mattered. Specific and short. Generic thanks to a whole team reads as filler, and everyone can tell the difference.
[15 min] Questions
Pre-submitted and upvoted, highest first. Anonymous allowed. Take the top question even if — especially if — it is the uncomfortable one. Skipping the top-voted question is the single fastest way to lose the room, and everybody can see the vote count.
How to answer what you cannot answer
I cannot answer that yet. Here is why, here is when I will be able to, and here is who will chase me. That is a complete and respected answer. "We will come back to you" with no name and no date is heard as no, and it is usually right.
Afterwards, within 24 hours
Post the recording, the slides, and a written answer to every question there was not time for — each with a name against it. The written follow-up is what converts a meeting into a record, and it is disproportionately read by the people who did not speak up.
Questions
How long should an all-hands be?
Forty-five minutes, with fifteen of those reserved for questions. Sixty minutes tends to fill with presentation; thirty rarely leaves room for the Q and A, which is the part that carries the credibility.
How often should you hold an all-hands?
Monthly is the common rhythm. Weekly is too often to have something substantive and degrades into status; quarterly is long enough that news reaches people through other channels first, which is worse than not holding one.
How do you get people to ask questions?
Collect and upvote them in advance, allow anonymity, and answer the top-voted one first. Waiting for hands in a room where the last hard question went unanswered is how you get silence and conclude wrongly that nobody has concerns.
What should you do with unanswered questions?
Publish written answers within a day, each with a named owner. A question with no name against it is not being handled, and people have learned to read it that way.
Should an all-hands be recorded?
Yes — for people in other time zones, on leave, or who joined later. Tell everyone it is recorded before the Q and A rather than after, because it changes what some people are willing to ask and they are entitled to know.
Who should present at an all-hands?
The person who owns the thing being presented. A relayed update cannot survive its first follow-up question, and the audience recognises a relay immediately.
What should you not say in an all-hands?
Anything you cannot stand behind under a follow-up question, and any reassurance you are not certain of. A promise that later fails costs far more than saying “I do not know yet, and I will tell you on the 14th”.
The follow-up is where all-hands processes fail, not the meeting. Writing up answers to fifteen questions the same day is genuinely hard if the only record is the memory of whoever was on stage, which is an argument for recording your own all-hands and working from the transcript.
Read next
- Meeting agenda template — Four lines that fit in the invite body.
- QBR agenda — Their outcome, not your usage charts.
- Skip-level questions — Easiest first, and the mistake that ends the programme.
- Running effective meetings — Four decisions, and the three meetings to cancel.
- Return to office — The documentation layer that quietly left.