How to run a remote launch day
Launch day is the day a lot of small things have to happen in the right order, by different people, at roughly the same time. On a remote team that usually means a calendar invite for a "launch call", a dozen DMs, and a spreadsheet nobody updates after ten in the morning.
Run it from one channel instead. Write the run sheet down before the day, keep a voice room open for the hours that matter, and post every step as it happens. When the day ends, the channel is the record.
The usual way
A remote launch day often looks like this.
- The call that never ends. Someone opens a video call at nine "for the launch" and it runs until six. Half the people on it are muted and doing other work.
- Updates in DMs. The person who pushed the release tells the person who sends the email. Nobody else knows it happened.
- A checklist in a doc. It was accurate yesterday. Today the boxes get ticked late or not at all.
- The "did we" question. At four in the afternoon someone asks whether the announcement post went out. Three people go looking.
A format for a distributed team
1. Make one launch channel
Create a channel for the launch a week ahead, named after the thing you are shipping. Everyone involved joins it: engineering, design, support, whoever writes the announcement. Everything about the day goes there, and nowhere else.
2. Write the run sheet as a pinned message
Post the plan in the channel and pin it. One line per step, in order.
- The step. Deploy, flip the flag, publish the post, send the email, update the docs.
- The owner. One name per step.
- The time. A rough time, in one time zone everyone agrees on.
- The check. How you know it worked. The page loads, the email arrived, the post is live.
A run sheet in the channel is one scroll away from the work. Nobody has to find the doc.
3. Post each step as it happens
When a step is done, the owner replies in a thread under the run sheet: what they did and the check they ran. A short line is enough.
Done: flag on for everyone at 10:02. Signup page loads in a private window.
That thread answers the "did we" question before anyone asks it. Someone joining late reads it top to bottom and knows exactly where the launch stands.
4. Keep a voice room open for the busy hours
Some parts of a launch go faster out loud: the deploy, the first hour after the announcement, the moment something looks wrong. Talk in a walk-in voice room beside the launch channel for those hours.
People walk in when their step is close and walk out when it is done. No one has to sit on a call all day to be reachable. Anything decided out loud still goes in the thread, so the written record stays complete.
5. Post a short recap at the end
When the day is over, the launch lead posts a recap in the channel. Three parts is enough.
- What shipped. The steps that went out, with links.
- What changed. Anything that ran differently from the run sheet, and why.
- What is next. Follow-ups with an owner and a date.
Make it repeatable
- Copy the run sheet. The next launch starts from the last one. Steps that kept slipping move earlier.
- Name a launch lead. One person reads the thread all day and calls out a step that is late.
- Log the decisions. Anything decided on launch day is a decision. Write it down with a reason using the format in How to keep a decision log in team chat.
- Have the war room ready. If something breaks, move to the format in How to run an incident war room for a remote team and link it from the launch thread.
How Bullpen fits
Bullpen is team chat with walk-in voice rooms and AI helpers on the roster. A launch can live in one channel from the run sheet to the recap.
The run sheet and updates are a thread. Every step and every check sits under the plan, in order.
The busy hours happen in the channel's walk-in voice room. It stays open beside the channel. People walk in for their step 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, so what was decided out loud lands next to the run sheet.
Nix keeps the follow-ups. When the recap lists a follow-up with 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.
Scout remembers the launch. Scout is an AI helper on the same roster. Months later, mention Scout and ask when the flag went on or who sent the email. Scout answers from what was said and links the message it came from.
Try it on your next launch
A week before your next launch, make the channel and pin a run sheet with one owner and one check per step.