All Hands Meeting Without the Catch-All Hour
Copy a timed all-hands agenda, protect 20-33% for Q&A, run hybrid as one-device rules, and replace the hour with a memo.
Updated 18 min read
An all hands meeting is a company-wide gathering for updates, goals, and questions with leadership. GitLab writes the agenda first and keeps live attendance optional. Slido protects 30 of 90 minutes for Q&A.
Default length is 45-60 minutes. Skip the hour when a memo would carry the same facts.
This guide is for ops, people, internal comms, and founders who run the hour. It covers timed agendas, leftover Q&A, hybrid rules, and the test for replacing the live slot with a written update.
Key Takeaways
- Name one purpose for the hour. "Everyone is invited" is an attendee list, not an agenda.
- Copy a timed agenda and protect 20-33% of the clock for questions. Unused slide time rolls into Q&A, never the reverse.
- Close leftover questions in writing within 24-48 hours. Do not dump them on first-line managers with no extra context.
- Run hybrid as remote-first rules: one person, one laptop, one camera; remote questions first; presenter mic, audience mic, and speakers.
- Replace the live hour when the content is a broadcast, nobody is in an emotional event, time zones make one slot exclusionary, and you will actually close the loop in writing.
What Is an All Hands Meeting?
An all-hands is a scheduled session where the whole company hears from leadership in one room or one stream. Slack, Predictive Index, and Slido treat "all-hands," "town hall," and "company-wide meeting" as workplace synonyms.
Civic "town hall" search is a different query. Keep this page on the workplace meeting.
Lucid is blunt: "All Hands" only names who is invited. You still have to name the job: information that cannot live in Slack, belonging, mission, or cross-functional alignment. Skip that sentence and the hour becomes a scattershot webinar.
Gable (May 2026) gives three tests. The meeting should give information that cannot come from Slack, create space for questions leadership would rather dodge, and make a distributed team feel like one company.
Predictive Index splits an information-driven all-hands from a more open Q&A town hall. Pick one shape per invite.
Lindsay Kaplan (Workshop) names the failure mode that produces both shapes at once:
"All hands can become a catchall or a panacea that's expected to do everything to engage and inform and fix culture and inspire and align and when it's meant to do all of these things, I'd argue that it ends up doing nothing particularly well."
Her filter is operational: if a topic is not relevant to every employee, it does not go in the company all-hands. Department tours belong in division copies.
Why the Standing Invite Fails in 2026
Cadence is a quality decision, not a tribal default. Granola (July 2026) publishes a size table: under 50 people, weekly 20-30 minutes; 50-150, bi-weekly or monthly 30-45; 150-300, monthly 45-60; 300-500, monthly or quarterly 60-75.
Noota says most companies land monthly, and a tight 45 beats a rambling 90. Coommit puts the hybrid sweet spot at 45-60 minutes; under 30 feels rushed.
Predictive Index tells you not to host monthly out of perceived obligation. Prefer a sustainable 45-minute monthly over a quarterly 2-3 hour slog. Corporate Christie is blunter: if the sales cycle is not closed and there is nothing meaningful to say, wait.
"You don't need an all hands every month. If your sales cycle isn't closed or there's nothing meaningful to update, wait. Maybe every other month is a Slack update with a video from the CEO… and then save your all hands to be a real performance."
Corporate Christie (14:32)
On r/managers, weekly is described as a tax. The least-hated live form is quarterly, about 45 minutes, with leftover Q&A.
Atlassian (~2019/2020, nearly 4,000 people) went the other way: local monthly all-hands failed at global scale, so they ran weekly 30-minute company-wide town halls with timezone re-runs. Do not copy that cadence in 2026 without checking whether they still run it.
Set cadence from two questions: how fast do facts change, and is live time actually dialogue? Stretch to 90 only when about 30 of those minutes are Q&A.
How an All-Hands Works: Four Jobs, One Hour
You need four jobs on the same invite: a timed agenda, leftover Q&A, hybrid rules, and a kill switch for the recurring hold.
Job 1: A Timed Agenda With One Archetype
Share the agenda 24-48 hours ahead (Slack's window) or 72 hours, minimum 24 (GitLab). GitLab's rule is "no agenda, no attenda." Justworks wants one primary objective, employee input weeks ahead, and a named producer.
Gable names five archetypes: Alignment, Celebration, Transparency Q&A, Strategic shift, or Post-mortem. Pick one, maybe two, never all five. The day-of Slack reminder should state that purpose in one sentence.
Job 2: Protected Q&A Plus a Leftover Write-Up
Q&A is the point of the live hour. Cutting it when slides run long tells the room that leadership updates outrank employee questions. Protect 20-33% of the clock.
Collect and rank questions in public. Write every leftover answer after the call.
Job 3: Remote-First Delivery Rules
Hybrid fails when the room is a TV show and remotes are an audience. Treat one device per person, remote questions first, a dedicated remote emcee, and an audio triad (presenter mic, audience mic, speakers) as operating rules.
Job 4: A Kill Switch for the Recurring Invite
Send the memo when the content passes an email test, nobody is in a high-stakes emotional window, one live slot excludes time zones, and you will close leftover Q&A in writing. Keep the standing calendar hold only when live time is dialogue on top of a pre-read.
Tobi Lütke treats a standing meeting as a bug to root-cause:
Meetings are a usually a bug. If you properly root cause them, you will find a trust issue, a clarity issue, or a missing API. Meetings can paper over these, but it’s much better to fix root cause.
Root-cause the trust, clarity, or missing interface. Do not paper over it with another 60 minutes.
Agenda Structure: Copy a Clock, Then Defend It
Steal a timed clock. Leave the 40/20/40 mnemonic, the 5 P's, and Robert's Rules to generic meeting advice.
Template | Length | Q&A block | Best fit |
|---|---|---|---|
45 min | 12 min (~27%) | 50-500 FTE | |
Slido (own meeting) | 90 min | 30 min (33%) | 300+ / 25 countries |
60 min | 10 min (~17%) | Monthly default | |
60 / 30 min | 15 / 8 min | Hybrid equity | |
r/managers pattern | 45 min quarterly | remainder | Division copy |
Granola's 45-Minute Split
Granola (July 2026) times a 50-500 FTE meeting as: wins 5, metrics 8, roadmap 10, peer recognition 5, live Q&A 12, close 5. Extra time from short segments rolls forward to Q&A, never extra slides.
A timekeeper gives a two-minute warning. Peer shoutouts are collected the week before, specific and peer-driven. Granola says putting Q&A at the end "signals that it is optional."
Slido's 90-Minute Monthly
For 300+ people across 25 countries, Slido runs: icebreaker 5-7, business updates 15, priorities 15, special session 10, team updates 10, AMA 30 (about one-third), close 3. Speakers use polls and quiz questions instead of only reading slides. They close with the same short feedback survey each month.
Noota's 60-Minute Rule
Welcome 5, performance 10, department highlights 20 (3-4 minutes per team), spotlight 5, looking ahead 10, Q&A 10, wrap 2-3. That is Noota's monthly default, capped at 3-5 topics.
The written rule: "If an update can be written in an email, skip it, or send it ahead of time."
Spinach is similar: 3-5 minutes per department, and at least 10 minutes forward-looking, because that block is what produces action items. Raw numbers without context do not.
A 45-Minute Quarterly That Managers Tolerate
u/Dlrocket89 in r/managers (April 2026) describes a quarterly that is "honestly not bad": 10 minutes on financials, 15 on strategy, 15 highlighting work from named teams, rest for Q&A. Division-level copies beat the company-wide hour because the content is closer to the work.
Share It Early, Close It in Public
Coommit argues for a canvas rather than a slide deck: a North Star sentence, 3-5 live charts, wins and losses pre-filled async, decisions with owner and date, a live ranked Q&A wall. Close with a commitment record. Open the next meeting by marking last cycle Done, On Track, or Slipping.
Justworks adds a producer who owns timing and technology so speakers can stay on the room. Without that name, leftover questions become hallway talk.
Q&A Handling: Time-Share, Then Write the Leftovers
Sample-question banks fill the Q&A search results. The operator problem is different: how much of the hour is dialogue, and what happens to the questions you did not reach.
Source | Q&A share | Treat as |
|---|---|---|
Slido own meeting | 30 of 90 = 33% | Default ceiling |
Atlassian (~2019/2020) | ~25% of a 30-min week | Historical primary |
20-25% fixed | 10-12 min in a 45 | |
15 of 60; 8 of 30 | Cites Atlassian 25% | |
10-15 min reserved | "Pushed to the wayside" | |
10 of 60 ≈ 17% | End block | |
7 of 60 ≈ 12% | Failure mode |
Protect 20-33%. Roll unused slide time into Q&A. Do not use a 7-minute AMA as the standard.
Devon Owens (Workshop, 39:51) says the failure is shrinking questions to two minutes so people do "mental gymnastics" about whether there is time.
On r/managers, the constructive pattern is publish first, then talk:
"I keep suggesting that they publish everything they want to say in advance, and save the event for Q&A. Spending an hour reading slides out loud and then leaving isn't very useful."
u/Snurgisdr in r/managers (April 2026)
Collect, Rank, Moderate
Open the question tool days before. Slido opens Monday for a Friday meeting and posts the link in #general.
Let people upvote in the 24 hours before. During the hour, keep collecting.
Gable routes every question through one digital tool, including people sitting in the room. Do not use raw Zoom chat as the queue. Slido highlights the live question fullscreen.
A moderator treats Q&A as an interview: groups similar questions, pulls the right exec, reads remote questions aloud. Gable assigns a dedicated remote facilitator whose job is the chat and the remote experience.
Kaplan's phrasing still matters. "What questions do you have?" opens the floor. "Any questions?" invites silence.
Corporate Christie collects ahead because people will not put a face on "our benefits kind of suck."
Use one digital Q&A queue. Slido publishes the leftover playbook operators copy. Mentimeter is the named alternative.
If the recap lives in Slack, Polly fits that channel.
Anonymity and Pre-Screening
Granola, Slido, and Lattice argue anonymous questions lower the barrier. Lucid warns anonymity can unleash trolls, and some companies are moving away.
Be explicit. Tell people if you will filter.
Hard questions are a design choice. Collect and rank in public. Brief execs on topics, not scripted answers.
Take the spicy ones live. Write the leftovers. Pre-screening to protect leaders makes the queue performative within two or three cycles.
Lattice (Alioto): if policy is still forming, say the policy is in development rather than allude to layoff "what ifs."
Juraj Holub at Slido says name off-limits areas and why (salaries, confidential deals) instead of silently dropping questions.
r/managers remembers what happens when ranking works:
"Anonymized questions from employees with voting on which questions should be answered. It flipped the sessions to subjects that people actually cared about. It also made the execs really mad and didn't last long."
u/Snurgisdr in r/managers (December 2025)
If leadership kills the ranked queue, the meeting is no longer for questions. Stop calling it Q&A.
Leftovers Are an Operating System
Never leave a question unanswered. Slido documents three write-up paths.
A financial-institution CEO emails every employee who asked by name. Marks & Spencer takes 20 live minutes, then 30-40 leftover questions into later team meetings. Internal comms gathers answers and posts them in Slack.
Granola puts unanswered Q&A with written responses in the 24-hour recap.
Skip any of those and first-line managers inherit the blast radius:
"It is terrible for the lower managers, we get all the questions after the town hall and have no more information than the ICs. We also get all the fallout if a dumb policy is announced."
u/rpm429 in r/managers (April 2026)
Mentimeter on LinkedIn (August 2026) names the same leak: opinions exist; they move to the hallway if you do not take them. Kaplan's "after show" is a leftover venue.
GitLab designs for skippers. Put the recording in the agenda within 12 hours. Write leftover answers in the recap so skippers still get the questions.
Remote and Hybrid Delivery: Rules, Not Gear
The all-hands-specific operating rules live here. Sibling pages on a distributed team and remote productivity already cover the rest of remote work.
Gable splits three formats. In-person plus stream works when fewer than 30% of people are remote, and it creates remote-equity risk. Hybrid-by-default (30-70% remote) means everyone joins from their own device, even in the same building.
Fully virtual fits when more than 70% are remote. Use office days for social time around the meeting, not during it.
Hybrid-by-default sounds wasteful. It is how you stop the room from becoming a TV set.
Coommit states the camera rule: one person, one laptop, one camera, even in the same conference room. Call on remote questioners first for the first 15 minutes.
Liane Davey calls hybrid "the worst of both worlds" unless everyone joins via the technology. Toggle cameras by mode: off when the work product is a document; on when the mode is conversation. An all-hands is a conversation.
Workshop (Devon Owens, 31:19) does not require cameras. They require a visible chat, displayed on in-office screens. Camera-on is not the same as engagement.
Audio, Screens, Roles
Catchbox publishes the audio triad: presenter mic, audience mic (otherwise remotes miss half the conversation), and speakers so the room hears remotes. Host/moderator plus dedicated tech.
Their cost math: 80 people times 5 minutes of troubleshooting is about 7 hours of lost productivity. Workshop's cube puts slides on one screen and the participant chat on the other.
Zoom splits the stack. Meetings are interactive, up to 1,000 people. Webinars are broadcast plus controlled Q&A, up to 100,000 view-only.
Assign roles before the hour: slides, Q&A/chat, polls, security. Dry-run the room. A one-way stream means Q&A cannot be a floor mic.
Atlassian (~2019/2020) added timezone re-runs (breakfast replay in Austin), pre-recorded remote presentations, and upvote Q&A after local monthly all-hands failed at global scale.
GitLab is the remote operating system. Bias to async. No agenda, no attenda.
Attendance optional across 65+ countries.
Pre-record presentations so live time is Q&A. Use 25- and 50-minute meetings.
Post the recording within 12 hours. Confirm decisions 24-48 hours later for other timezones.
r/managers rejects games, raffles, and "HOW'S EVERYONE DOING TODAY" as manager-soothing theater. Connection, when people want it, is optional coffee chats beside the meeting, not a slot inside a mandatory all-hands.
When a Written Update Should Replace the Live Hour
Google does not currently rank a dedicated "cancel the all-hands, send a memo" page. The operators who already did the work are GitLab, Float, and teams that pre-record the broadcast half.
David Heinemeier Hansson put the remote version in 2020:
The productivity boost from working remotely does not come from replacing all those in-office meetings with a bunch of video calls. It comes from turning all those meetings into write-ups instead. Status updates, pitches, ideas. Write. Them. Down.
Matt Mullenweg (June 2023) asked the diagnostic question: are you having a remote-work problem, or a too-many-meetings problem? If the invite does not make it obvious why you are needed, Kaplan says people correctly ask whether the slides would suffice.
On r/managers the same diagnosis is a joke with a body count:
"90% of town halls could just be an email that people ignore, instead it's an online town hall that people ignore."
u/vulcanstrike in r/managers (April 2026)
An email that people ignore is still cheaper than an hour the whole company ignores together. The working substitute is a written record plus a leftover question path: an async meeting with a named owner.
GitLab: Handbook First, AMA Optional
Write the announcement in the handbook or an issue. Post with those links. Offer an optional AMA.
If a meeting still happens, pre-record the presentation; live time is Q&A only. Attendance is optional. Cancel in the first minute if there is no outcome.
Float Remote Roadshow (2021)
Float broke a quarterly live Zoom at 30+ people across 15+ countries: midnight logins, Q&A when people needed sleep. The replacement (December 2021) was a 48-hour global lineup. Six sessions, each 15-20 minutes of presentation plus 10-15 minutes of live Q&A, Slack leftovers, optional calendar holds, recordings after each session.
Content rule: it had to be "synchronous-worthy."
Float's line: "The word update should be avoided because it signals that the information could be delivered async." Dated: do not imply Float still runs this format without a 2026 check.
The design still holds. Split the broadcast across time zones. Keep live minutes for questions.
Adjacent: Atlassian's Loom Challenge
Atlassian (June 2024) asked employees to replace one meeting with a Loom in two weeks. Kickoff was a global town hall. They still use live all-hands as a launch ritual.
Atlassian reports 93% watched a Loom; 43% had a meeting replaced; 5,000 hours freed. Best suited to presentations, status, demos, and training: one person talks most of the time. Use this for "replace the broadcast half." Do not claim it killed Atlassian's town hall.
Keep Live When the Hour Is Dialogue or News
Keep the live hour when the news is high-stakes and emotional. Atlassian dedicated an hour to the Hipchat/Stride shutdown. Predictive Index says some information does not fit a memo.
During layoffs or restructuring, Slido argues you increase update frequency and create safer question space. That is process, not legal advice. Announce from the top, not the grapevine.
Dialogue also earns the slot: at least 25% Q&A on top of a pre-read. So does a company still under 50 people, when this is the only full-team culture touchpoint (Granola). Even then, status can still be written.
Google TGIF is the cautionary thinning. Weekly became monthly on 15 November 2019 after leaks.
Leak-control that quietly kills Q&A is the pitfall. Label what is confidential. Answer the rest.
The Four-Part Replace Test
Replace or shrink to AMA-only when all four are true:
- Content is a status, metrics, or roadmap broadcast that passes Noota's email test or GitLab's handbook-first test.
- No high-stakes emotional event is in flight.
- Time zones make a single live slot exclusionary (Float, GitLab, Atlassian re-runs).
- You will close the loop: leftover Q&A in writing, recap within 24 hours, recording in 12 hours.
If you publish the memo but leave the recurring invite, you did not replace the meeting.
Recap and Follow-Through
Granola wants the recap within 24 hours: summary, decisions, action items with owners and deadlines, unanswered Q&A with written responses, transcript. Open the next all-hands with last cycle's commitments.
Put the artifact in one Slack channel or canvas, not six tools. GitLab wants the recording within 12 hours. Aim the written recap inside 24 hours so people who skipped live still get decisions and leftover answers.
Coommit proposes coverage targets (vendor-colored, not independent studies): Q&A coverage 80%+, commitment-to-completion 75%+ (below 50% is theater), recall 70% one week later, remote vs in-office NPS delta under 10 points.
Use them as internal dashboards. Do not cite them as research.
Common All-Hands Mistakes to Avoid
Catch-All Panacea
Kaplan's trap: the hour is asked to inform, engage, fix culture, inspire, and align. Christie's version is the department-update conveyor belt.
Name one archetype. If a topic is not relevant to every employee, cut it.
Cutting Q&A When Slides Run Long
Protect 20-33%. Unused slide time rolls into questions. A 7-minute AMA after 53 minutes of deck is a broadcast with applause lights.
Leftovers Dumped on First-Line Managers
u/rpm429's problem is structural. Every unanswered question needs a written owner in the recap. Managers should not learn the "real" answer in Slack DMs after the stream.
Room Bias and One Camera at the Back
One laptop per person. Remote questions first for 15 minutes.
Presenter mic, audience mic, speakers. A dedicated remote emcee.
A single camera at the back of a conference room is a webinar you pretend is a conversation.
Pre-Screening Questions to Protect Leaders
Collect and rank in public. Brief execs on topics.
Take the spicy ones. Name off-limits areas.
A filtered queue dies in two or three cycles, and employees notice.
Six Artifacts Nobody Opens
One recap home. Recording in 12 hours, written leftovers in 24.
Adding Slack, Loom, and Notion on top of the calendar creates more places to miss the decision.
Games Inside a Mandatory Hour
r/managers treats icebreakers, raffles, and forced cheer as manager-soothing theater. Optional coffee chats can live next to the meeting. They do not belong inside it.
