What is an all hands meeting?

One audience, one version of the news

Most company communication is filtered: a manager passes on part of a leadership decision, a team hears about a new customer secondhand, a rumour about a restructure runs ahead of the facts. The all hands exists to remove that filter for an hour. Slack's guide describes it as a gathering where every employee comes together to hear important updates, celebrate wins and engage with leadership, and it notes the same meeting is also called a town hall or company wide meeting. In practice the content repeats from month to month: how the business is performing, what the priorities are, who has joined, what is changing, who deserves thanks, and time for questions. That repetition is useful, because people learn where to look.

All hands against town hall

Many companies use the two names interchangeably, and there is no official line between them. Where a distinction is made, an all hands is mostly presented, with leaders walking through results and priorities and a short question time at the end, while a town hall is built around the questions, with leaders mainly listening and answering. Atlassian's account of its own meetings shows how blended they can be: weekly half hour global town halls, about a quarter of which are devoted entirely to questions, with questions submitted in advance and voted up by staff. Whatever it is called, the format should be chosen for the job. News that needs explaining suits a presented all hands; a change people are anxious about needs time for questions.

When the meeting matters most

Cadence depends on size and pace. Slack's guide suggests weekly meetings for small teams with fast moving priorities, fortnightly for mid sized companies, monthly for larger organisations and quarterly where the message is long term strategy, while stressing that quality matters more than frequency. The meeting after a bad quarter, a restructure, an acquisition or a leadership change matters far more than a routine one, because silence at those moments is read as bad news. Distributed teams raise the stakes again. When staff sit in different cities and time zones, a recorded all hands with a written summary may be the only place a warehouse team and a sales team hear the same message.

Common mistakes

The first is turning the meeting into a series of department reports, each running over, so the important news is squeezed into the last five minutes. The second is metrics without meaning: a revenue chart with no target and no comparison teaches nobody anything. The third is dropping question time when the agenda runs long, which tells staff their questions are optional. The fourth is changing the order every month, so people cannot find the part they care about. The fifth is saving difficult news for the end, or leaving it out, when staff already know something is happening. The last is ignoring people who could not attend; record the meeting and send the deck with a short written summary.

All hands decks in the slide builder

The all hands example linked on this page is an eleven slide monthly deck for a food manufacturer that has kept the same order for two years: cover, agenda, the same six numbers, quarterly objectives, customer voices, new starters, a deep dive divider, a process, five priorities with owners, a takeaway and pre submitted questions. A deck like that can be generated from a brief and then saved, so next month starts from the same structure with new numbers. While presenting, speaker notes can pop out into a separate window on your own screen, and pen tools let you circle the number you are talking about. Pen tools and recording are paid features. A share link serves whatever version was last saved, but anyone who opens it can press N and read the notes, so keep private remarks out of them.

Questions people ask