How to run a great all-hands meeting

TL;DR: A great all-hands meeting is a strategic alignment tool, not a status broadcast. Structure the agenda around interactive elements like live Q&A and peer recognition rather than slide-reading. Protect at least 20-25% of total meeting time for live Q&A and treat it as a fixed block, not the segment that gets cut when earlier sections run long. Match your cadence to company size: weekly under 50 people, monthly at 150 to 300. Document decisions during the meeting so the recap writes itself. Follow the framework below to build a repeatable, high-trust all-hands format.

Company all-hands meetings often start with high energy but can end with disengaged employees who open other tabs while leaders read slides verbatim. The Q&A either runs long because nobody collected questions in advance or runs short because nobody asks anything at all. By the time the recap lands in the inbox two days later, half the context is already gone.

The problem is not the all-hands format. The problem is treating the meeting as a one-way broadcast rather than a company-wide conversation. When leaders design the all-hands as a product, with a clear purpose, a repeatable structure, and a documented output, it becomes one of the most efficient alignment tools available.

Key drivers of a high-impact all-hands meeting

The all-hands meeting sits at the intersection of culture and communication. Its purpose is not to inform employees of things they could have read in a Slack message. Its purpose is to build shared context, surface concerns, and reinforce a sense of collective direction that written updates cannot replicate.

Effective all-hands meetings share common principles: interactive design that involves employees rather than just addressing them, structured transparency that shares the "why" behind decisions, and documented outcomes that stay searchable after the call ends. Every structural choice in the sections below connects back to these principles.

Where to place the Q&A

Morale is built through transparency and recognition, not through polished slide decks. The structural choice that matters most is where you place the Q&A. Putting it at the end signals that it is optional. Making it the centerpiece of the agenda signals that employee questions are the point.

Determining the ideal all-hands meeting frequency

There is no universal cadence that works for every company. The right frequency depends on how fast context changes, how distributed the team is, and how much communication already flows through async channels.

Weekly for startups under 50 people

At fewer than 50 employees, context changes fast enough that a weekly all-hands keeps the whole company moving in the same direction. At this size, the all-hands also functions as a culture touchpoint and is often the only moment the full team sees each other.

Scaling to monthly all-hands meetings

As teams grow past 150 employees, weekly meetings become logistically difficult and risk feeling repetitive. Monthly cadences give leadership enough time between sessions to gather meaningful updates and give employees enough time to develop questions worth asking. Monthly meetings work best when they are anchored to a consistent date and follow a predictable structure, which reduces preparation time because everyone knows what is coming.

When to shift your all-hands cadence

Consider this framework when assessing whether your current cadence still fits your company:

Designing a repeatable all-hands agenda

A repeatable agenda structure reduces preparation time for every subsequent meeting. Below is a proven 45-minute format for the 50 to 500 FTE stage, structured around the elements that consistently drive engagement in distributed all-hands sessions.

Granola's pre-meeting briefs feature helps meeting organizers walk in with open threads and relevant context already surfaced, so leaders can focus on being present rather than scanning notes before the call starts. That small shift, from reactive to prepared, changes the tone of the entire session.

1. Recent wins and milestones

Open with a five-minute wins segment. Tie each milestone back to company mission rather than listing it in isolation. "We closed our biggest enterprise deal this quarter" lands differently when you add "and it validates the segment we committed to 18 months ago." This framing keeps the company narrative coherent and gives employees a sense of forward momentum.

2. Product roadmap updates

For product managers, the all-hands roadmap update is one of the highest-leverage moments in the quarter. It connects customer evidence to engineering priorities in front of the entire company. Product managers can use this four-step workflow:

1. Centralize and synthesize. Before the meeting, pull the most relevant customer insights from the research repository. Granola's folder-level chat lets product managers query across months of discovery calls with a single question: "What are the top enterprise pain points from Q2 interviews?" Source-linked citations validate the synthesis.
2. Connect insights to strategic priorities. For each roadmap item in the update, pair it with the customer evidence that drove the decision. The insight explains the "why" behind the priority and builds stakeholder trust in the research process.
3. Present the "why" alongside each item. Balance vision and realism. Provide a high-level view covering the timeline, key bets, and the customer evidence that supports each, without overloading slides with detail.
4. Make it audience-appropriate. The all-hands audience includes engineers, sales, and operations. Plain language travels furthest. "Three enterprise customers told us they abandon onboarding at step four" is clearer than "our discovery synthesis revealed onboarding friction at the fourth funnel stage."

3. Methods for meaningful peer shoutouts

Structured peer recognition drives engagement. The highest-impact recognition is specific and peer-driven rather than top-down. In the all-hands context, this means creating a format where anyone on the team can name a colleague and describe the specific impact they had, rather than awarding a generic "employee of the month." Collect shoutouts through a shared Slack channel or form in the week before the meeting so the segment runs smoothly on the day.

Proven tactics for high-impact Q&A

The Q&A is the most important part of the all-hands. Dedicate at least 20% to 25% of total meeting time to it: for a 45-minute meeting, that is 10 to 12 minutes of live questions, protected as a fixed block rather than the segment that gets trimmed when earlier sections run long.

Three tactical decisions determine whether your Q&A surfaces real concerns or safe questions: anonymous submission, upvoting priority, and documented follow-up.

• Anonymous vs. named questions: Anonymous submission tools lower the barrier for sensitive topics. Employees who would not publicly challenge a strategic decision will often submit the question anonymously, and these are frequently the most valuable questions for leadership to address. A hybrid approach works best: collect both named and anonymous questions in advance, then let the facilitator group and reframe them so no individual is singled out during the live session.
• Prioritizing questions during the call: Upvoting systems surface questions that matter to the most people. This prevents the meeting from being dominated by one vocal individual while quieter employees with widely-shared concerns go unheard. Ask employees to vote on questions in the 24 hours before the meeting so the facilitator arrives with a ranked list ready to work through.
• Addressing leftover questions: Not every question gets answered live. Create a documented process for follow-up: post the unanswered questions in the meeting recap alongside written responses from the relevant leaders, and link back to any follow-up discussion in Slack. Granola's chat-with-meetings feature lets leaders query the transcript after the meeting to help identify questions that came up, including those that went unanswered.

Tracking key decisions and action items

Every action item discussed during the all-hands needs three things: an owner, a deadline, and a place to track it. Without all three, the item exists in a conversational limbo where everyone assumes someone else is handling it. Decisions made during the all-hands have a short half-life without documentation, and within a week, the exact wording of a commitment, the person who made it, and the timeline attached to it will vary depending on who you ask.

Writing and sharing the all-hands recap

The recap is the bridge between live alignment and sustained execution. It needs to reach everyone who attended and everyone who could not.

Drafting your all-hands meeting recap

Granola's human-in-the-loop note enhancement is well-suited to all-hands documentation. The organizer jots rough highlights during the meeting: "Budget question re: headcount," "Q3 roadmap change flagged by engineering." When the meeting ends, clicking "Enhance notes" pulls in the transcript context and fills in the detail around each highlight. Your notes stay in black, AI additions appear in gray, and you control what stays.

The result is a structured recap that reflects your judgment about what mattered, not a generic summary of everything that was said. For more on structuring post-meeting communication, the meeting recap email guide covers format and templates that work across different meeting types.

Ensuring async access to meeting recaps

Remote and distributed teams depend on async access to meeting outcomes. Distributing a well-structured recap within 24 hours of the all-hands closes the institutional knowledge gap and reduces the repeat-question load in subsequent meetings. The recap should include the company update summary, decisions made, action items with owners and deadlines, unanswered Q&A questions with written responses, and a link to the full transcript for anyone who wants to go deeper. For teams that need to decide between formal and informal documentation, the meeting minutes vs. notes guide explains when each format applies.

Creating a searchable all-hands archive

Over time, the all-hands becomes a living record of how the company thought, decided, and communicated. Querying that archive saves hours of manual search and prevents repeat conversations. Ask "What did we say about the enterprise sales motion in January?" and get an answer in seconds.

Granola's Chat feature queries across your meeting notes with inline citations, so you can ask "What recurring employee concerns have come up across the last six all-hands sessions?" and get source-linked answers from specific meetings. When notes are organized into shared team folders, this extends to the broader team's meeting history, turning documented all-hands sessions into organizational memory that outlasts personnel changes.

Pitfalls that undermine your all-hands meeting

The risk of cutting Q&A time

When the presentation runs long and the facilitator trims the Q&A to compensate, employees notice immediately. The implicit message is that leadership's updates are more important than employee questions. Protect the Q&A block by capping each agenda section with a hard time limit. If a section runs short, carry the extra time forward to Q&A rather than filling it with additional slides.

Why unfinished tasks kill meeting value

Action items discussed without owners and deadlines decay immediately. When employees see that you never followed through on commitments from the last all-hands, they stop treating the current one as a meaningful decision-making forum and start treating it as theater. Publish a brief accountability update at the top of each all-hands: here is what we committed to last time, here is where each item stands.

Running the live all-hands session

Timeboxing your all-hands meeting

Running over time is a trust issue, not just a scheduling inconvenience. When the meeting consistently runs long, employees may stop believing the stated end time and start mentally blocking extra time. Assign a timekeeper role and treat each agenda block as a fixed container. For a 45-minute all-hands, the breakdown looks like this:

Brief presenters in advance with hard time limits, and designate someone to give a visible two-minute warning during each segment.

When to mandate all-hands attendance

Mandatory attendance makes sense when the meeting covers material that genuinely affects everyone: a strategic pivot, a restructuring, or a company-wide initiative launch. For routine monthly updates, consider designating some sessions as optional for people in deep work phases, provided the recap is comprehensive enough that they can stay fully informed asynchronously. The goal is high voluntary attendance through strong meeting quality, not compliance through enforcement.

Tactics to energize remote attendees

Remote participants disengage faster than in-room ones because there are fewer social cues pulling their attention back. These tactics help:

• Use live polls or word clouds in the opening segment to create immediate participation
• Name specific remote attendees during shoutout segments rather than only recognizing people who happen to be in the office
• Run the Q&A from a dedicated chat channel so remote employees can submit and upvote questions at the same pace as in-room attendees
• Keep video on for at least the first and last five minutes to create social presence at the meeting's bookends

Granola's multi-language transcription supports remote teams across 10 languages, including English, French, German, Spanish, and Japanese.

Managing silence during all-hands sessions

Silence at the start of a live Q&A does not mean no one has questions. It usually means no one wants to go first. Solve this structurally by pre-loading the Q&A with two or three submitted questions before opening the floor. The facilitator reads a submitted question, answers it, and this breaks the silence without requiring anyone to put themselves forward voluntarily.

If the room stays quiet despite seeded questions, it is often a signal that employees do not yet trust that honest questions will be received well, and that is a culture issue requiring a different intervention.

Try Granola for free. Download the Mac, Windows, iOS, or Android app, connect your calendar, and capture your next all-hands without a visible bot in the room so your Q&A stays candid.

FAQs

How often should a 150-person company run an all-hands meeting?

Monthly is the standard once a company passes roughly 150 employees, continuing through the 150 to 300 range. A monthly cadence gives leadership enough time to gather meaningful updates between sessions and gives employees enough time to develop genuine questions worth raising.

How much time should be allocated to Q&A?

Dedicate at least 20% to 25% of total meeting time to Q&A. For a 45-minute meeting, that means 10 to 12 minutes of live questions.

Can Granola transcribe meetings in multiple languages?

Yes. Granola supports transcription in 10 languages, with additional language support on iOS and Android. The multi-language setting also handles mixed-language conversations automatically within the same meeting.

How do I handle sensitive topics during the all-hands Q&A?

Collect questions anonymously before the meeting so employees can raise concerns without attaching their name to them. For sensitive company announcements, having senior leaders deliver the message directly and maintaining consistent messaging across every audience can help build trust.

Key terms

All-hands meeting: A company-wide gathering where leaders share business updates, celebrate milestones, and address employee questions to ensure organizational alignment.

Institutional knowledge loss: The accumulated loss of context and decisions that occurs when meetings are not documented systematically, leading to repeated conversations and slower decision-making.

Timeboxing: The practice of allocating a fixed, maximum time limit to a specific agenda item so the meeting stays on schedule and the Q&A block is protected.

eNPS (Employee Net Promoter Score): A single-number metric that measures how likely employees are to recommend their organization as a good place to work. What constitutes a favorable score varies by industry and company size. Check your engagement platform's benchmarking data for a relevant reference range.