How to run a remote brainstorming session
A brainstorm is where a team puts a pile of options on the table before it picks one. On a remote team it is usually a video call with a digital whiteboard. The first idea spoken sets the direction. By the end of the hour the board is full of sticky notes, and nobody opens it again.
Put the brainstorm in the channel that owns the problem. Collect ideas in writing first. Talk in a walk-in voice room that stays open. Leave a shortlist in the channel, with a name next to each next step.
The usual way
A remote brainstorm often looks like this.
- One calendar slot for everyone. One link, one hour. A teammate in another time zone joins at the end of their day, or reads about it later.
- The first idea wins. Someone speaks in the first two minutes. Most of what follows is a version of that idea.
- A board in another tool. The sticky notes live in a whiteboard app. The team's channel never sees them.
- No owner for what comes next. The call ends on "great session." The best idea waits for someone to pick it up.
A format for a distributed team
1. Write the question in one sentence
"Ideas for onboarding?" gets ideas for everything. Write a sharper question at the top of a thread in the channel.
"How might a new teammate ship a small change in their first week?"
One question per brainstorm. If the thread turns up a second one, name it and park it for another day.
2. Collect ideas in writing first
Leave the thread open for a day. Ask for one idea per reply, in a sentence or two. Hold replies to other people's ideas until the live part.
Writing first gives every person the same say. The quiet teammate and the one in another time zone get their ideas in before anyone talks. Every idea arrives in the thread on equal footing, so the loudest one does not get a head start.
3. Group the ideas, then talk
Before the live part, the host reads the thread and groups the replies into a few themes. Post the themes as one message in the thread.
Then name a short window, twenty or thirty minutes, and talk in the walk-in voice room beside the channel. The room is already open, so there is no link to send. Spend the time on the themes rather than reading every idea aloud. Combine ideas, build on them, and add the ones the conversation turns up.
People step in for the window and step out when they are done. A teammate whose day starts later reads the thread and walks in while the room is still up.
4. Leave a shortlist with owners
End with three ideas or fewer. Each one gets a message in the channel with the same three fields: the idea, who owns the next step, and by when.
Shortlist: a starter task tagged in every repo. Owner: Sam. By Friday, Sam posts three candidate tasks in this thread.
The rest of the ideas stay in the thread. They are searchable, and the next brainstorm on the same problem can start from them.
Prompts for a brainstorm that stalls
- Worst idea first. Ask for the worst possible answer, then flip it. The opposite is often a useful start.
- Half the time. What if this had to work in half the time, or with half the people?
- Borrow from elsewhere. How does another team, or another industry, solve the same problem?
- What we tried before. What did the team try last time, and what happened?
The last one is the prompt teams skip most often. It is also where Scout helps.
How Bullpen fits
Bullpen is team chat with walk-in voice rooms and AI helpers on the roster. A brainstorm stays in one channel from the question to the shortlist.
The ideas are a thread. The question, the written ideas, and the themes sit with the rest of the work on that problem.
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. The ideas spoken out loud land next to the ideas written in the thread.
Scout remembers what was tried. Scout is an AI helper on the same roster. Before the window starts, mention Scout in the channel and ask what the team already tried on this problem. Scout answers from what was said and links the message it came from.
Nix keeps the next step. Mention Nix in the thread where an owner promised a next step 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.
When the shortlist turns into a choice, How to keep a decision log in team chat is the shape for recording it.
Run the next one this way
Post the one-sentence question in your team's channel the day before the brainstorm, and end the live part with a shortlist of three, each with an owner and a day.