How to run a remote all-hands meeting
An all-hands is the one meeting where the whole company hears the same thing at the same time. On a remote team it is usually an hour on a video call with forty tiles, a slide per department, and five minutes of questions at the end that nobody asks.
Run it the other way around. Post the updates in writing first, collect questions in a thread for a day, and use the live part only for the questions. Keep the answers in the channel, where people who missed it can read them.
The usual way
A remote all-hands often looks like this.
- Updates read aloud. Each team lead reads their slide. Everyone could have read it faster on their own.
- Questions at the end. The Q&A gets whatever time is left. The hard questions come up a day later in a DM.
- One time zone wins. The call lands at a reasonable hour for headquarters and at dinner or dawn for everyone else.
- A recording nobody opens. The hour gets saved as a video. Finding the one answer you need means scrubbing through it.
A format for a distributed company
1. Post the updates a day early
Make a channel for company-wide news, or use the one you have. A day before the all-hands, each team lead posts a short update in one thread. Three parts each is enough.
- What shipped. The work that landed since the last all-hands.
- What is next. The one or two things the team is working on now.
- Where they need help. A decision, a hire, a dependency on another team.
Written updates take a minute to read and stay in the channel. Someone in another time zone reads them over coffee instead of at midnight.
2. Collect questions in writing
Post a second thread for questions, one per reply. Leave it open until the live part starts.
Questions in writing are easier to ask and easier to answer well. The leadership team can sort them, answer the simple ones in the thread, and save the rest for the live part. A teammate who is nervous about asking out loud can still ask.
3. Keep the live part short
Pick a window, thirty minutes is usually enough, and talk in a walk-in voice room beside the news channel. The room is already open, so there is no meeting link to send around.
Skip the updates. Everyone has read them. Go through the open questions in order, and answer each one plainly. When the answer is "we have not decided", say who is deciding and by when.
People walk in for the window and walk out when they are done. Someone who arrives late reads the thread and catches up.
4. Post the answers in the thread
After the live part, reply under each question with the answer that was given. One answer per question, in writing, next to the question it answers.
Q: Are we hiring for the support team this quarter? A: Yes, one role. Maya posts the description in #hiring by Friday.
That thread is the record. Next month, the answer to "what did they say about hiring" is a search away instead of forty minutes into a video.
Make it a habit
- Same day, same channel. A fixed rhythm, monthly or every other week, means nobody has to ask when the next one is.
- Rotate the window. If the company spans many time zones, move the live part between two slots so the same people are not always up early.
- Write decisions down. Anything decided at an all-hands is a decision. Log it with a reason using the format in How to keep a decision log in team chat.
- Drop what nobody reads. If a section of the update gets no questions three months running, cut it.
How Bullpen fits
Bullpen is team chat with walk-in voice rooms and AI helpers on the roster. An all-hands can live in one channel from the first update to the last answer.
The updates and questions are threads. They sit in the news channel with everything else the company has announced.
The live part is the channel's walk-in voice room. It stays open beside the channel. People walk in for the window and leave when they are done.
Wren writes the notes. Wren is an AI helper. In that walk-in voice room, Wren posts notes and action items back to the channel the room belongs to. What leadership said out loud lands next to the questions.
Scout remembers the answers. Scout is an AI helper on the same roster. Weeks later, mention Scout in the channel and ask what was said about a topic. Scout answers from what was said and links the message it came from.
Nix keeps the promises. When someone says they will follow up by a date, mention Nix in that thread and the reminder arrives in the channel on the day. How to keep track of follow-ups in team chat covers the details.
Try it at the next one
Before your next all-hands, ask each team lead for a three-part written update a day early, and open a questions thread at the same time.