The all-hands is a broadcast with a reach problem. Leadership spends real preparation on an hour of strategy, numbers, and direction — and then delivers it to whoever happened to be available at that hour. In any company past a certain size, "whoever's available" is a fraction: time zones, shifts, PTO, client calls. The fix on offer is "the recording's in the drive," which is not a fix — an hour-long internal video is opened by almost no one, and the announcements that were supposed to align the company align the half that showed up.
There's a second, quieter loss on the other side of the room. The Q&A — the questions people actually asked — is the most honest signal leadership gets about what the company is thinking. And it evaporates the moment the call ends.
Key takeaways
- The all-hands under-delivers twice: announcements don't reach the absent half, and the Q&A signal is lost. Both are format problems, not effort problems.
- A recording becomes a five-minute summary that broadcasts to the company channel — where the absent half will actually read it, unlike a recording link (product facts below).
- The Q&A, captured in the summary, is a barometer: what people asked, and which themes recur across meetings — read by hand, but readable at all for the first time.
- Honest scope: the product summarizes and broadcasts; the "barometer" is you reading the questions across summaries, not an automated sentiment dashboard.
The reach problem
An all-hands optimizes for the room, but the room is a minority. The people who most need the context — the distributed half, the ones who couldn't attend — get it worst: a recording is a poor delivery mechanism because it asks for the one thing a busy person won't spend on internal comms, an uninterrupted hour. So the announcement that a reorganization is coming, or that the roadmap shifted, lands unevenly, and the "wait, when did we decide that?" confusion that follows is a communications failure wearing an attendance costume.
The delivery that works is the opposite shape: short, pushed to where people already are. Process the recording and the all-hands returns as a structured summary — announcements, numbers, decisions — and broadcasts itself to the company's Telegram or Slack channel, where the absent half reads it with their coffee (product facts). The same broadcast-not-recording logic serves distributed stand-ups in async stand-ups; an all-hands is that pattern at company scale.
The Q&A barometer
Here's the asset most companies throw away. The questions asked in an all-hands Q&A are uniquely candid data: they're what employees chose to raise in front of leadership, which is a filtered but real signal of what's on their minds — anxiety about a change, confusion about a priority, enthusiasm about a direction. In the live meeting they're answered and forgotten. Captured in the summary, they persist (product fact: summaries capture the meeting's content, including the questions raised).
Read across several all-hands, the Q&A becomes a barometer. Do the same worries keep surfacing? Did a change land or generate a wave of questions? Is one topic quietly dominating what people ask about? These are leadership questions the recurring Q&A can answer — and the searchable archive makes "what did people ask when we announced the last reorg?" a lookup (product facts).
State the boundary plainly: this barometer is you reading the questions across summaries, supported by search and multi-meeting reports — not an automated sentiment score or a mood dashboard. Read it at the level of themes, not individual scoring of who asked — the point is what the company keeps raising, not judging the people who raised it. The product captures and organizes the questions; the reading of them stays human, which is appropriate, because interpreting what a team's questions mean is a leadership judgment, not a metric.
The archive as institutional memory
Beyond any single meeting, the all-hands archive becomes the company's spoken record of its own direction. "When did we announce the new structure?" and "what did we actually commit to on the Q3 goals?" resolve to a search with a date and a quote (product facts). For a fast-growing company where half the team wasn't there for the last three pivots, that record is onboarding into the company's own story.
One honest note on scope: this is a general recording-summary-broadcast workflow, not a dedicated internal-comms platform. There's no all-hands template and no built-in engagement analytics — it turns the meeting into a readable, broadcastable, searchable record, and the internal-comms craft around it stays yours.
Sources and method
Product facts (structured summaries capturing meeting content including Q&A, broadcast of summaries to Telegram/Slack channels, full-text search and multi-meeting reports, archive questions with quoted answers) describe MeetResult as documented in the product catalog at the time of writing. No sentiment analysis, engagement dashboard, or all-hands template is claimed — the "barometer" is manual reading supported by search. Internal recording is the company's responsibility. No statistics are cited or invented.
Related: Async stand-ups without losing the conversation · Your meeting week needs a bottom line · How to turn a meeting recording into tasks · Nearly everyone gets the all-hands (use case)
Process your next all-hands in @meetresultbot: broadcast the summary to the company channel, then read the Q&A as the signal it always was. New accounts include free processing minutes.