meeting-all-hands

name	meeting-all-hands
description	Plan and run a company or department all-hands meeting. Use when preparing for a quarterly all-hands, town hall, or company-wide meeting where leadership addresses the full organization.

All-Hands / Town Hall Meeting Planning

What an All-Hands Is For

An all-hands is a leadership communication event. Its purpose is to:

• Build alignment on where the company/team is going
• Reinforce culture and shared purpose
• Give employees direct access to leadership
• Address uncertainty or hard questions honestly
• Celebrate wins and people

What it is NOT: A collection of department status updates read off a slide.

Audience & Scale

Scale	Format Recommendation
< 50 people	Single room or video call; high interactivity possible
50-200 people	Auditorium or large video call; moderate interactivity
200-500 people	Video production quality needed; structured Q&A
500+ people	Broadcast model; pre-screened Q&A; breakout by team after

Recommended Cadence

Frequency	Best For
Monthly	Fast-moving startups, high uncertainty periods
Quarterly	Most companies — aligns with business cadence
Bi-annual	Large orgs; supplement with team-level all-hands

Agenda Template (60-minute format)

1. Opening — CEO/Leader (5 min)

• Personal tone, not formal
• Acknowledge what the company has been through recently (hard or good)
• Set the theme/narrative for today's meeting
• One question to anchor on: "What do we most need the team to understand after this meeting?"

2. Company Pulse — Where We Stand (15 min)

• Key metrics: What are they, where were we 90 days ago, where are we now
• Be honest — good and bad. Trust is built by not spinning.
• 3 wins since last all-hands (specific, named)
• 1-2 challenges acknowledged directly
• Avoid: Death by data. Pick 3-5 metrics maximum. Use visuals.

3. Strategic Focus — Where We're Going (15 min)

• What are the top priorities for the next quarter?
• What's changing? What's NOT changing?
• How does each team connect to these priorities?
• If there's been a pivot or a hard decision — explain the "why" directly

4. Spotlight / Recognition (5 min)

• Name specific individuals or teams who went above and beyond
• Be concrete: "The infra team kept us live during the AWS outage on May 3rd with zero customer impact — that was exceptional."
• Avoid generic praise; it dilutes the signal

5. Open Q&A (15 min)

• This is the most valuable part — don't cut it
• Use a moderated format: submissions via Slido, anonymous option
• Answer hard questions directly; "I don't know but I'll find out" is a valid and trusted answer
• Avoid: filtering out critical questions — employees notice and trust drops

6. Close (5 min)

• Re-anchor on the 1-2 things you want people to leave remembering
• Call to action: what do you want employees to DO differently after this?
• Personal close — something human, not corporate

Content Preparation

4 Weeks Before

• Align leadership on key messages
• Decide what metrics/data to share
• Collect spotlight nominations
• Build slide structure (no content yet)

2 Weeks Before

• Draft slides; review with leadership
• Prepare Q&A simulation: list the 10 hardest questions employees will ask and draft honest answers
• Schedule dry run

1 Week Before

• Full dry run with all presenters — time it
• Open Q&A submission (Slido, anonymous form) in advance so real questions surface
• Confirm AV / hybrid setup

Day Before

• Final slide review
• Brief all presenters on timing and handoffs
• Test tech setup end-to-end

Slide Design Principles

• One idea per slide — not a wall of text
• Data with narrative — show the number, but say what it means
• Photos of people — employees want to see themselves and colleagues
• No jargon — plain language; if you can't explain it simply, you don't understand it well enough
• Slide count: For a 60-min all-hands, aim for 20-30 slides maximum

Q&A Best Practices

Collecting Questions

• Use Slido, Mentimeter, or Google Forms — anonymous submissions increase honesty
• Open submissions 48 hours in advance for thoughtful questions
• Collect live questions during the meeting for real-time topics

Answering

• Don't deflect hard questions — paraphrase and address directly
• "I don't know" + follow-up commitment is more trusted than a non-answer
• If the question is common: "I see a lot of versions of this question — here's what I'm hearing..."
• Assign a follow-up owner when the answer needs more research

Moderation

• Assign a moderator (not the CEO) to manage flow
• Group similar questions
• Reserve right to combine/reframe: "This is a version of..."
• Don't read the question robotically — internalize it and respond naturally

Hybrid All-Hands

• Use a camera operator so remote viewers see speaker, not just slides
• Run a separate chat moderator for remote Q&A
• Display chat questions alongside in-room questions — treat them equally
• Record and share within 24 hours for those who couldn't attend live

Common All-Hands Mistakes

Mistake	Impact	Fix
Pure status update format	Employees feel like they got a report, not a conversation	Lead with narrative, not metrics
No hard topics addressed	Erodes trust — employees know what's happening	Name the elephant in the room
No Q&A or filtered Q&A	Signals leadership doesn't want accountability	Open, anonymous, unfiltered
Too long (>90 min)	Attention collapses; message is lost	Hard cap at 75 min; cut content, not Q&A
Generic recognition	Feels performative	Specific names + specific actions
No follow-through on Q&A commitments	Trust killer	Assign owners; publish answers async

Post-Meeting

• Publish the recording and slide deck within 24 hours
• Publish written answers to questions that came in but weren't addressed live
• Manager cascade: ask team leads to hold a quick team debrief to reinforce the messages
• Survey: simple 2-question pulse ("What resonated? What's unclear?")