How to Run an All-Hands Meeting That's Worth Everyone's Time
What belongs in a company-wide all-hands versus a team meeting, a structure that keeps it from becoming a one-way broadcast, and how often to run one.
An all-hands meeting is meant to give an entire company shared context — what's happening, how things are going, where the business is headed — but it easily drifts into a one-way broadcast that people tolerate rather than value, especially once it becomes routine enough to stop feeling like genuinely new information.
What belongs in an all-hands versus a team meeting
All-hands territory: overall company performance, major company-level decisions or changes, cross-team visibility (what other teams are working on that affects everyone), and recognition that's meaningful company-wide.
Team-meeting territory: day-to-day work specifics, team-level process decisions, and anything genuinely relevant to only one function. Content that only matters to one team, presented to the whole company anyway, is one of the more common reasons an all-hands starts to feel like a waste of time to everyone outside that team.
The test worth applying to any agenda item before it goes into the all-hands: would someone in a completely different function genuinely want or need to know this? If not, it belongs somewhere more targeted.
A structure that avoids the one-way broadcast trap
Open with something genuinely worth everyone's attention, not administrative housekeeping. Starting with the most valuable content, rather than saving it for the end when attention has already faded, respects that people's focus is highest early in the meeting.
Keep any single presenter's segment short. A 15-minute uninterrupted update from one person, repeated for several people in sequence, is exactly the format that produces passive attention. Shorter segments from more voices, with room for questions between them, keep the format from becoming a lecture series.
Build in real question time, and solicit questions in advance. Live, open "any questions?" moments in a large group tend to favor the same few confident voices every time. Collecting questions beforehand — through a shared doc or a quick survey — surfaces what quieter people actually want to know, and gives the presenter a chance to prepare a real answer rather than improvising.
Rotate who presents. An all-hands run entirely by the same one or two leadership voices every time reinforces a top-down, broadcast feel. Having someone from a different team present periodically — a project update, a customer story, a specific win — diversifies the meeting's voice and often surfaces things leadership wouldn't have thought to include.
End with something forward-looking, not just a summary of what was covered. A clear sense of what's coming next gives the meeting a sense of momentum rather than feeling like a closed loop of information that's already happened.
Handling hard news in an all-hands
Not everything covered in an all-hands is good news, and how difficult news is handled matters more than any other part of the format. Vague, softened language about a real setback — a missed target, a difficult decision, a departure — tends to be read as evasive, which damages trust more than the news itself would. Direct, honest framing, with room for real questions, generally lands better even when the content itself is uncomfortable, because it signals the company treats its people as capable of handling real information.
Cadence: how often is worth it
Monthly is a common and reasonable default for a small company — frequent enough to maintain shared context, infrequent enough that there's genuinely new, substantive content each time. A weekly all-hands at a small company often struggles to justify its own frequency, since company-level developments rarely move fast enough to warrant a full company gathering every single week; that cadence tends to drift into padding with content that would have been better as a written update or handled in team meetings instead.
Remote and hybrid considerations
An all-hands with some people in a room and others joining remotely needs deliberate attention to avoid a two-tier experience — remote attendees struggling to be heard during discussion, or missing informal context that happens before or after the "official" meeting in the room. Running the meeting as fully remote-first, even when some people happen to be in the same physical space, or actively bringing remote voices into the discussion by name, both help close this gap.
Measuring whether it's actually working
A simple, honest signal: are people asking real questions, or is the Q&A segment consistently quiet? A consistently silent Q&A across many sessions is worth investigating directly — it might mean genuine clarity (unlikely if it's every single time), or it might mean people have concluded the format doesn't actually invite real engagement, which is worth knowing and addressing rather than assuming silence means satisfaction.
Following up after the meeting
An all-hands generates real value beyond the meeting itself only if what's discussed is captured and followed up on. A brief written recap — key points, any decisions announced, answers to major questions raised — shared afterward serves people who couldn't attend live, gives everyone a reference to return to, and creates a visible record that questions raised were actually answered rather than left to fade once the meeting ends. Skipping this step means the meeting's value evaporates the moment it's over for anyone who wasn't fully paying attention throughout, or who has a follow-up question that occurs to them later.
Reading the room over time, not just in the moment
A single flat or distracted all-hands doesn't necessarily mean the format has failed — attention naturally dips sometimes regardless of content quality. What's worth tracking is the pattern over several sessions: are questions submitted in advance growing or shrinking, does engagement seem to differ meaningfully by topic, are people visibly present but checked out. This kind of pattern, tracked honestly over time, is a far more reliable signal than any single meeting's energy level, and it's the right basis for deciding whether the format itself genuinely needs to change.
The short version
An effective all-hands sticks to genuinely company-wide content, keeps individual segments short enough to hold attention, actively solicits and makes room for real questions, and rotates who presents rather than running as the same one or two voices every time. Run monthly with substantive content, it builds shared context efficiently; run too often or too passively, it becomes a meeting people tolerate rather than one that actually informs or connects anyone.
Frequently asked questions
How often should a small company run an all-hands meeting?
Monthly is a common cadence — frequent enough to keep everyone genuinely informed, infrequent enough that each one has real content worth gathering the whole company for. Weekly all-hands at a small company often struggle to justify their own frequency.
What's the difference between an all-hands and a team meeting?
An all-hands covers company-wide information relevant to everyone — overall performance, company-level decisions, cross-team visibility. A team meeting covers work specific to one team's day-to-day. Content relevant to only one team doesn't belong in an all-hands.
How long should an all-hands meeting be?
30 to 45 minutes is typical for a small company. Longer sessions tend to lose engagement well before they end, especially once the meeting becomes a habit rather than a novel event.
How do you make an all-hands interactive instead of a one-way broadcast?
Build in real time for questions, actively solicit them in advance so quieter people have a way to participate, and occasionally hand part of the agenda to someone outside leadership to present, rather than having the same one or two voices run the entire meeting every time.