How to run a remote project kickoff
A project kickoff is where a team agrees on what it is building, who owns which part, and what done looks like. On a remote team it is usually a slide deck on a video call. Everyone nods. A week later two people are building slightly different things, and the deck is in someone's downloads folder.
Run the kickoff in the channel the project will live in. Post a one-page brief in writing first. Talk it through in a walk-in voice room that stays open. Leave owners, dates, and open questions in the channel, where the work will happen.
The usual way
A remote kickoff often looks like this.
- A deck nobody reads twice. The plan lives in slides. The slides live in a shared drive. The channel gets a link, once.
- One hour for every question. Questions come up after the call, when people start the work. By then the person who knows the answer is in another meeting.
- Owners by implication. "The backend team will handle that" is not a name. Each part waits for someone to claim it.
- A start date and no checkpoints. The kickoff sets a deadline. Nothing between now and then says whether the project is on track.
A format for a distributed team
1. Write a one-page brief
Post the brief as the first message in a new channel for the project, or as a pinned thread in the team's channel. Keep it to five parts.
- The goal. One sentence on what changes for a customer or a teammate when this ships.
- In scope. What the project includes, as a short list.
- Out of scope. What it leaves for later, so nobody builds it by accident.
- Done means. How the team will know it is finished.
- First checkpoint. A date, two weeks out or sooner, when the team looks at progress together.
One page is the limit. A brief that runs longer is usually two projects.
2. Collect questions in writing first
Leave the brief up for a day before the live part. Ask everyone to read it and reply in the thread with questions, one per reply.
Questions in writing get better answers. The person who wrote the brief can answer the easy ones in the thread, and the hard ones become the agenda for the live part. A teammate in another time zone asks theirs before anyone talks.
3. Talk through the hard questions
Name a window, thirty minutes is usually enough, and talk in the walk-in voice room beside the channel. The room is already open, so there is no link to send.
Skip reading the brief aloud. Everyone has read it. Spend the time on the questions the thread could not settle: a scope edge, a dependency on another team, a part with two possible owners.
People step in for the window and step out when they are done. Someone who joins late reads the thread and walks in while the room is still up.
4. Post owners, dates, and open questions
End the kickoff with one message in the channel. Every part of the project gets a name and a date.
Kickoff summary. Search filters: Priya, first version by Oct 30. Import flow: Dan, design posted by Oct 24. Open question: who signs off on copy. Dan asks marketing by Thursday. First checkpoint: Nov 3, in this channel.
Open questions get an owner too. A question with nobody on it stays open until it becomes a surprise.
Checkpoints that keep it honest
A kickoff sets direction. Checkpoints keep it.
- Post progress in the channel. A short weekly update from each owner, in one thread, beats a status meeting. Replace the status meeting with a walk-in room covers the shape.
- Record decisions as they happen. Scope changes are decisions. Write each one down with a reason, using the format in How to keep a decision log in team chat.
- Reopen the brief, not a new deck. When the plan changes, edit the brief and post what changed. The first message in the channel stays the source of truth.
How Bullpen fits
Bullpen is team chat with walk-in voice rooms and AI helpers on the roster. A project stays in one channel from the brief to the last checkpoint.
The brief is a thread. The plan, the questions, and the answers sit with the rest of the work on the project.
The talk 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 was settled out loud lands next to the brief.
Scout remembers what was agreed. Scout is an AI helper on the same roster. Weeks into the project, mention Scout in the channel and ask what the kickoff said about scope. Scout answers from what was said and links the message it came from.
Nix keeps the dates. Mention Nix in the thread where an owner promised something by a day, and the reminder arrives in that channel on the day. How to keep track of follow-ups in team chat covers the details.
Run the next one this way
Before your next project starts, post a one-page brief with a goal, scope, a definition of done, and a first checkpoint date, and give the team a day to ask questions in the thread.