How to Run Remote Brainstorming Sessions

How should you run remote brainstorming?

Run it in four phases with the writing first: a silent generation round on a shared board, a clustering pass, a short discussion of the clusters that matter, then a vote that informs a named decider. Keep generation and judgement in separate time blocks, and never let the discussion start before every idea is written down.

That answer is short because the method is simple. The difficulty is discipline: video calls push people toward talking, and talking is exactly what degrades idea volume.

Why does the usual video brainstorm produce so few ideas?

The standard remote brainstorm fails for structural reasons, not because the team is unimaginative. Three losses show up consistently, and all three get worse on video.

Production blocking. In a turn-taking conversation only one person can speak at a time. Anyone with an idea while someone else talks must hold it, and held ideas are often lost, judged redundant, or forgotten. The classic research is unambiguous: in four experiments published in the *Journal of Personality and Social Psychology* in 1987, Diehl and Stroebe tested free riding, evaluation apprehension, and production blocking, and found production blocking accounted for most of the productivity loss.

Evaluation apprehension. People censor themselves when the audience includes a manager or a sceptic. On video the audience is a grid of silent faces, a poor condition for proposing something half-formed.

Reduced social cues and narrowed attention. A 2025 analysis in *MIT Sloan Management Review* described research covering more than 1,400 participants across laboratory and field experiments: videoconferencing significantly reduced the number of creative ideas generated compared with in-person collaboration. The proposed mechanism is attentional — staring at a screen narrows peripheral awareness and cognitive scope. The practical implication is awkward but useful: for creative generation, audio-only may outperform video, and writing outperforms both.

Add the remote-specific drag — notifications, multitasking, the two seconds of lag before anyone speaks — and the eight-idea outcome becomes predictable.

What does the written-first format look like?

The format has four phases and one rule: no talking during generation. It borrows from the nominal group technique, a structured method developed in the 1970s and still used in healthcare and research prioritisation, where silent written generation followed by round-robin sharing consistently outperforms open discussion for both volume and equity of contribution.

Phase 1: frame the question (5 minutes)

State one question, not a topic. “How do we cut onboarding from 14 days to 5?” is a question. “Onboarding improvements” is a topic, and topics generate vague ideas. Put the question, constraints, and useful context on the board before people join.

Constraints belong in the brief, not in evaluation. “Must work with the current HR system” prevents twenty unusable ideas. “No budget” prevents ideas you might want.

Phase 2: silent writing (8–10 minutes)

Everyone types ideas onto the shared board, one per card. Name the target: “aim for eight, do not filter.” Quantity is the goal, because the useful idea usually sits downstream of several obvious ones.

Two details matter. Keep microphones muted and cameras optional during this phase; the silence is the method, and a facilitator who fills it with chatter destroys it. Make cards anonymous when the topic is sensitive or the hierarchy steep — anonymity raises candour and costs nothing on a shared board.

Phase 3: cluster and clarify (15 minutes)

Group similar cards, then read the clusters aloud. The facilitator sorts while everyone watches — three to five minutes for 70 cards — then each cluster gets a one-sentence summary and a check: “did we lose anything genuinely different?”

Discussion happens here, not in phase 2, and should clarify rather than advocate. “What did you mean by this?” is allowed. “That will never work” is not, yet.

Phase 4: converge with a vote and a decider (15 minutes)

Give each person three to five dots and let them spend them on any cards, including their own. The vote is not a decision; it is a heat map. Then the named decider chooses two or three ideas and says why, in the meeting.

That last step separates a brainstorm from a discussion group. A session that ends with “great, we’ll circulate these” produces nothing. Decide who takes which idea forward, by when, and what “forward” means — a test plan, a customer call, a prototype spike.

> Practical tip: Put the decision on the agenda as an item with a named owner. “14:50–15:00: Priya selects two ideas for the October test cycle” is a different meeting from one that ends at “any other business”.

How do the formats compare?

The pattern: as soon as writing precedes talking, volume goes up. The verbal column is not a strawman — it is the honest baseline for a well-run traditional session.

How do you build a 60-minute agenda?

A visible countdown on screen does more than any tool; nobody needs a speech about time management.

Notice what is missing: introductions, a warm-up, and a round of “how is everyone”. With a recurring team those cost eight minutes and add little.

A worked example with numbers

A product team of 12 runs this agenda on “how do we reduce support tickets by 30%?”.

• Silent writing produces 74 cards. One person submits 11, another 3 — the distribution is itself useful information.
• Clustering reduces 74 cards to 26 clusters; 4 duplicate existing initiatives and are dropped.
• Four dots each puts 48 votes across 22 clusters. The top cluster has 9 votes, the second 7.
• The decider picks two — a self-service password reset (9 votes) and a help-centre search rewrite (7) — and rejects the third with a stated reason: it needs a platform change already scheduled for Q1.

Total meeting cost: 12 people × 1 hour = 12 person-hours, or $780 at a loaded $65 per hour. The alternative most teams choose — three follow-up meetings over five weeks to “align on priorities” — costs about $2,340 plus five weeks of delay.

Does silent writing really produce better ideas?

Yes for volume and originality, with a caveat about feasibility. The evidence is consistent across laboratory and field settings.

A 2025 study in the *Journal of Creative Behavior* randomly assigned 157 working students to 57 small groups and compared synchronous virtual brainwriting with video-based oral brainstorming. Brainwriting groups generated significantly more ideas, more original ideas, a higher proportion of good-quality ideas, and greater elaboration. During selection, brainwriting groups chose higher-originality ideas while video groups favoured feasibility — worth knowing if your goal is incremental improvement rather than novelty.

An industrial study published in 2015 tested brainwriting inside a technology company and found that alternating individual writing with periodic review of the group’s ideas produced the best results, and that group-then-individual beat the reverse. The practical reading: do not choose between alone and together. Alternate.

The virtual nominal group literature points the same way. A 2024 scoping review in *PLOS One* covering 32 studies found that among authors who responded to a follow-up survey, 80% considered the virtual version comparable or superior to the in-person original.

Two honest limits. Most of these studies measure idea counts and expert-rated originality, not business outcomes; 74 ideas is not yet value. And written ideas are shorter, so nuance gets lost — which is why the discussion phase still matters.

When should you skip the live session and go async?

Go async when the problem is complex, the team spans time zones, or a status hierarchy suppresses dissent. Go live when you need commitment, conflict resolution, or a decision people will only accept if they heard the reasoning.

The async pattern: send the question and a blank board, give 24 to 48 hours, and require one contribution before the deadline. Then hold a single 45-minute session to cluster, discuss, and decide. Generation happens between other work, which is often when people have their best ideas.

The person-hour arithmetic

A 12-person live session costs 12 person-hours of calendar time. The async version:

• 12 people × 30 minutes of writing, spread across two days = 6 person-hours
• Facilitator preparation and clustering: 1.5 hours
• A 45-minute decision session with 8 attendees (the rest read notes) = 6 person-hours
• Total: about 13.5 person-hours, but only 45 minutes of shared calendar time

The person-hour total is similar. The real gain is calendar compression — one 45-minute block instead of a 60-minute one, with prior thinking time — plus participation from people who cannot attend a fixed slot. Whether that is a win depends on how expensive coordination is. For a team across eight time zones, it usually is.

One warning: async sessions decay. Response rates drop when the deadline is soft or the ask is vague. Set the deadline explicitly, chase individually, and close the loop publicly. A team that contributes and never hears the outcome will not contribute twice.

What does the facilitator actually do?

The facilitator’s job is to protect the process, not to have ideas. Five behaviours matter.

Hold the question. One question per session. If a second appears, put it on a parking-lot card and move on.

Enforce the phases. When someone evaluates during generation, say “hold that for the discussion” and keep the timer running. You will rarely need to say it twice.

Protect airtime. In discussion, go cluster by cluster and ask the people who have not spoken. A round of one sentence each costs little and flattens the room.

Keep energy without filling silence. Silent writing feels strange for two minutes. Resist narrating; a visible timer is enough reassurance.

Close the loop. Send a three-line summary within 24 hours: question, decision, next action with owner and date. Highest-return task in the process, most often skipped.

The facilitator should not usually be the decider. If they are, the room reads the vote as theatre. Separate the roles, or say explicitly when you switch hats.

Which tools do you actually need?

Very few. A shared document with a table handles 30 ideas for free. A whiteboard becomes worthwhile above roughly 50 cards, where dragging beats sorting text.

The tool is not the method. A shared doc, a timer, and enforced silence beat an expensive whiteboard with no structure. Choose the cheapest tool that survives clustering.

What are the common mistakes?

Starting with “any ideas?”. Open prompts produce silence, then the loudest suggestion, then agreement. Write the question in advance and allow two minutes of thinking.

Letting the senior person go first. The first idea anchors the rest. Write silently, or have the most senior person speak last.

Skipping the decision. A session without a named decider and a next action produces a document, not a result.

Confusing volume with value. Seventy ideas is an input; clustering and selection create value.

Running it too often. Brainstorming suits problems where the solution space is genuinely open. Using it for decisions already made teaches people to disengage.

No follow-up loop. If contributors never learn what happened to their ideas, participation collapses within two or three sessions.

What are the trade-offs?

The honest summary: written-first remote brainstorming is the better default for generating options and the worse choice for building commitment. If a decision needs buy-in more than novelty, a clear discussion structure will do more than any ideation technique.

Where does a project platform fit?

Ideas die between the board and the backlog. A session ends with two selected ideas, someone promises a document, and three weeks later nobody can find the notes or remember which version won.

Doitify addresses that handoff: a selected idea becomes a task with an owner, due date, checklist, and comments inside the workspace where the project already runs, so the session’s output sits next to the work it produced. Meeting notes stay alongside, keeping question, vote, and outcome in one place. Doitify is our product, so weigh that accordingly.

Conclusion

Remote brainstorming fails for predictable reasons: turn-taking, self-censorship, and a screen that narrows attention. The fix is not a better tool or a more energetic facilitator. It is a sequence — write first, cluster second, discuss third, decide last — with the phases kept apart.

Start with one question, eight minutes of silence, and a visible timer. Cluster what comes out, discuss only to clarify, vote to inform rather than decide, and have a named person choose two ideas and explain why. Then send the three-line summary within a day.

If you change one thing this quarter, move the writing before the talking. The rest is refinement.

If this post on remote brainstorming was helpful, you might also enjoy Project Reporting: The Complete Guide (Types, Templates, Best Practices) and How to Automate Repetitive Project Tasks (Step-by-Step).