An all-hands at 25 people, 150 people, 600 people, and 2,000 people is not the same product. Scale changes the ritual.
The failure mode is familiar: companies keep the early-stage all-hands format long after the organization has outgrown it. What used to feel candid becomes chaotic, what used to feel inclusive becomes performative, and what used to create alignment becomes another layer of noise.
The operating move is different. Redesign the format as the company scales: clearer pre-reads, tighter agenda ownership, stronger Q&A systems, manager cascade, and post-meeting artifacts.
At 25 people, the all-hands can be raw. Everyone knows the context, the founders can speak plainly, questions can happen live, and the company can tolerate messiness. The risk is not over-production. The risk is skipping the discipline of saying what changed and what matters.
At 150 people, informal context breaks. New employees do not know the backstory. Functions begin interpreting priorities differently. Managers become a real layer. The all-hands needs more structure: clearer agenda, decision follow-up, manager packets, and a way to capture questions that do not fit live.
At 600 people, the ritual is a product. Production quality matters because attention is scarce and trust is fragile. But production quality should serve clarity, not theater. Teams benefit from pre-reads for complex topics, structured Q&A, fewer presenters, better story spine, and explicit links to operating forums.
At 2,000 people, the all-hands should not be the sole place where alignment happens. It becomes one layer in a broader communication and operating system. Manager cascades, regional or functional forums, written strategy notes, operating reviews, dashboards, and local team rituals should handle part of the load.
Scale also changes what employees infer. In a small company, people may forgive rough communication because they have direct access to leaders. In a larger company, ambiguity travels farther and mutates faster. A vague answer from the CEO can become dozens of local interpretations by the end of the day.
The format should therefore evolve deliberately. Shorter live segments, better pre-work, tighter metrics, fewer updates, stronger follow-up, and clearer question handling often beat longer meetings. The goal is not to preserve the feeling of the early company. The goal is to preserve the quality of shared judgment through a different system.
Remote and hybrid work make this more important. When hallway interpretation disappears for some employees but not others, proximity privilege grows. The all-hands has to be designed for people who were not in the room before the room. That means written artifacts, time-zone respect, accessible recordings, and manager follow-up that does not depend on informal context.
Scale also changes participation. In smaller companies, employees can ask follow-up questions casually after the meeting. In larger companies, the meeting may be the usually time many people see the CEO reason in public. That raises the standard for clarity, accessibility, recording quality, and written follow-up. The bigger the company, the more expensive ambiguity becomes.
The design question is therefore not “How do we keep the old intimacy?” It is “Which parts of intimacy mattered?” Usually the answer is directness, access to reasoning, fast question loops, and visible leadership accountability. Those can be preserved through different mechanics: office hours, manager cascades, written recaps, AMAs, regional sessions, and structured follow-up. The broader operating-cadence lens is useful here: https://www.antoinebuteau.com/operating-cadence-series-10-how-to-know-if-youre-running-a-system/
The format should also match the company’s trust level. A high-trust company can handle more raw discussion because employees believe leadership is trying to be direct. A low-trust company may need more explicit evidence, tighter follow-up, and clearer question closure because every ambiguity is interpreted defensively. Scale is not usually headcount. It is also distance from leadership and accumulated trust debt.
The meeting also needs a different preparation ratio as it scales. Early on, a founder might think for ten minutes and speak plainly. Later, the same casualness creates gaps across legal, finance, people, customer, and product implications. More preparation is not bureaucracy when the expense of misinterpretation has increased.
The practical artifact is the scale-stage all-hands design. It should map the company's current headcount, trust level, manager maturity, geography, recording needs, question volume, and topic complexity to a format. That format should be revisited as the company changes.
At 25 people, the design might be founder-led and conversational, with a short written recap. At 150, it might add a manager pre-brief and a decision log. At 600, it might use pre-submitted questions, clearer segment ownership, and a post-meeting FAQ. At 2,000, it might combine global all-hands, regional follow-ups, manager kits, office hours, and written strategy notes.
The mistake is nostalgia. Leaders remember the early all-hands as intimate and try to preserve the format instead of preserving the function. The function was not casualness. It was access to reasoning, fast correction of confusion, and shared understanding of what mattered. Scale asks for new mechanics that protect those things.
The design is working when the company feels farther from the CEO but not farther from the reasoning behind company choices.
Scale also changes memory. Small teams remember what was said because everyone lived the same context. Larger teams need records: clips, recaps, decision logs, manager notes, and follow-up answers. Without that memory layer, the meeting depends on whoever happened to attend live and interpret it accurately.
That is the real design job.
This is part 9 of 10 in All-Hands Meetings That Actually Run the Company.