# thinkdrop.io — full guide corpus

thinkdrop.io is a real-time idea board for brainstorms, retrospectives and workshops: the facilitator shares a link, everyone adds idea cards at once, AI suggests missed angles and writes the summary when the session closes.

Every guide below is also available individually as markdown at https://thinkdrop.io/guides/<slug>.md.
Agent documentation and the free brainstorm API: https://thinkdrop.io/for-agents

You may quote these guides. Please cite thinkdrop.io with a link to the page used.

---
# How to run a brainstorming session

> Source: https://thinkdrop.io/guides/how-to-run-a-brainstorming-session · Last reviewed 2026-08-21 · The thinkdrop facilitation team

To run a brainstorming session, write the challenge as one specific question, invite 4 to 8 people with different perspectives, and set two ground rules: no criticism and quantity first. Give everyone five silent minutes to write ideas before anyone speaks, timebox generation to 20 minutes, then group the ideas into themes and leave with three owned next steps.

## Key facts

- **Group size:** 4–8 participants
- **Total length:** 45–60 minutes
- **Silent generation:** 5 minutes
- **Idea generation:** 20 minutes, timeboxed
- **Ideas to aim for:** 40+ before filtering
- **Decisions to leave with:** 3 owned next steps

## Step by step

1. **Frame one specific question** — Replace a topic with a question. "Onboarding" produces nothing; "What makes a new user abandon setup in the first five minutes?" produces cards. Write it where everyone can see it for the whole session and refuse to widen it mid-session.
2. **Invite 4 to 8 people, deliberately mixed** — Below four you get one person's opinion with witnesses; above eight the quiet half stops contributing. Include at least one person who is close to the problem day-to-day and one who is not — the outsider asks the question everyone else stopped asking.
3. **Set two ground rules out loud** — No criticism during generation, and quantity before quality. Say them at the start rather than assuming them. The first evaluative comment in a session sets the tone for everything after it, so name the rule once and enforce it once.
4. **Generate in silence first** — Give everyone five minutes to write ideas independently before anyone speaks. The first opinion said aloud anchors the room, and research on brainstorming consistently finds that individuals writing separately produce more distinct ideas than the same people talking. Collect the silent cards before opening discussion.
5. **Open the floor and build, timeboxed** — Run 20 visible minutes where people read each other's cards and add to them. Use "yes, and" rather than "no, but". Keep every idea on the board, including the impractical ones — they are the raw material for the ones that work.
6. **Group into themes** — Cluster the cards into five to eight themes and name each cluster in the group's own words. Naming the theme is the moment the session turns from a pile of ideas into an argument you can act on.
7. **Choose and assign three next steps** — Let everyone react to the cards, take the top three, and give each one a named owner and a date. A brainstorm without owners is a meeting people stop attending.

## Why most brainstorms fail

Sessions rarely fail because the team lacks ideas. They fail in three predictable places, and each has a mechanical fix.

- The question is too broad, so every answer is also too broad. Fix: one specific question, written down.
- The loudest person speaks first, so everyone else converges on their framing. Fix: silent generation before discussion.
- No one owns the output, so the ideas expire in the notes. Fix: three named owners before anyone leaves.

## Facilitator behaviours that change the outcome

The facilitator's job during generation is not to contribute — it is to protect the rules. Restate the question when the group drifts, write down ideas people say out loud so they are not lost, and interrupt evaluation with "park it, we'll judge after the timer". During grouping, the job flips: push the group to name themes precisely rather than accepting vague labels like "communication".

## Running it asynchronously

For distributed teams, open the board 24 hours before the call and let people add cards on their own time. You arrive at the live session with 40 cards already on the board and spend the meeting on grouping and deciding, which is the part that genuinely needs everyone present.

## A 60-minute agenda that works

| Time | Phase | What happens |
| --- | --- | --- |
| 0–5 min | Frame | Read the question aloud, state the two ground rules |
| 5–10 min | Silent generation | Everyone writes cards independently, no talking |
| 10–30 min | Build | Read each other's cards, add and extend |
| 30–45 min | Group | Cluster into 5–8 named themes |
| 45–55 min | Prioritise | React and vote, pick the top three |
| 55–60 min | Assign | Owner and date for each of the three |

## FAQ

**How many people should be in a brainstorming session?**

Four to eight — fewer produces one viewpoint, more silences the quieter half of the room.

**How long should a brainstorming session last?**

About 60 minutes, with idea generation timeboxed to roughly 20 of them.

**Should brainstorming be silent or spoken?**

Both: five silent minutes first, then spoken building on what everyone wrote.

**What is the most common brainstorming mistake?**

Evaluating ideas while they are still being generated, which stops people offering anything unfinished.

**How do you end a brainstorming session?**

With three chosen ideas, each having a named owner and a date, not with a list to review later.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/how-to-run-a-brainstorming-session.

---

# Brainstorming ground rules that actually get enforced

> Source: https://thinkdrop.io/guides/brainstorming-ground-rules · Last reviewed 2026-08-21 · The thinkdrop facilitation team

The core brainstorming ground rules are: defer judgment, go for quantity, welcome unusual ideas, build on others' ideas with "yes, and", stay on the one framed question, one conversation at a time, and make ideas visible to everyone. Rules only work when the facilitator states them aloud at the start and enforces the first violation.

## Key facts

- **Number of rules:** 7 — more than that and none are remembered
- **When to state them:** Out loud, in the first two minutes
- **Enforcement moment:** The first violation, not the third
- **Rule that matters most:** Defer judgment during generation

## Step by step

1. **Defer judgment** — No criticism, no "we tried that", no feasibility debate while ideas are being generated. Judgment has its own phase later. Enforce with: "park it — we'll judge everything after the timer."
2. **Go for quantity** — Aim for a visibly large number of cards. Volume is what surfaces the unusual idea; you cannot pick a great option out of six safe ones. Set an explicit target, such as 40 cards in 20 minutes.
3. **Welcome unusual ideas** — The impractical version of an idea is often the raw material for the practical one. Ask explicitly for the version that would be too expensive or too weird — it moves the whole set further from the obvious.
4. **Build on others with "yes, and"** — Participants should extend cards rather than replace them. "Yes, and" produces variants; "no, but" produces a debate. This is the rule that turns a list into a conversation.
5. **Stay on the framed question** — One question per session. When someone raises a genuinely important but different problem, write it on a parking-lot card and return to the question.
6. **One conversation at a time** — In a room, that means no side discussions. On a video call, it means no one talking over the person adding a card. Fragmented attention halves the number of ideas that get written down.
7. **Make every idea visible** — Every idea goes on the shared board where everyone can read it, including ideas said out loud in passing. Invisible ideas cannot be built on, and people stop repeating themselves after the second time they are missed.

## Rules fail silently unless you enforce the first violation

Almost every team knows these rules and almost none follow them, because the first quiet "that won't work" goes unchallenged. The facilitator's single highest-leverage action in the whole session is interrupting that first evaluative comment — politely, once. After that the room self-polices.

## Adapting the rules for senior stakeholders

When a manager is in the room, silent generation stops being optional. Have everyone submit cards anonymously before discussion, and have the most senior person speak last in every round. Otherwise the session measures what the manager already thinks.

## FAQ

**What are the basic rules of brainstorming?**

Defer judgment, go for quantity, welcome unusual ideas, build on others, stay on one question, one conversation at a time, and keep every idea visible.

**Why is deferring judgment the most important rule?**

Because a single early criticism teaches everyone in the room to only offer ideas they can already defend.

**Should brainstorming ideas be anonymous?**

Anonymous cards help when there is a seniority gap or the topic is sensitive; otherwise attribution helps people build on each other.

**How do you handle someone who dominates the session?**

Use written silent rounds so contribution is measured in cards rather than airtime, and call on people by name during discussion.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/brainstorming-ground-rules.

---

# How to facilitate a sprint retrospective

> Source: https://thinkdrop.io/guides/how-to-facilitate-a-sprint-retrospective · Last reviewed 2026-08-21 · The thinkdrop facilitation team

To facilitate a sprint retrospective, start by reviewing whether last retro's actions happened, then give the team five silent minutes to write cards about specific moments in the sprint. Group the cards, discuss only the top three, and end with two or three actions that each have a named owner. Keep the whole session to 60 minutes for a two-week sprint.

## Key facts

- **Length:** 60 minutes for a two-week sprint
- **Attendees:** The delivery team only, 5–9 people
- **Silent writing:** 5 minutes before any discussion
- **Topics discussed:** Top 3 only
- **Actions taken away:** 2–3, each with an owner
- **First agenda item:** Did last retro's actions happen?

## Step by step

1. **Check last retro's actions first** — Open with the actions from the previous retrospective and mark each done or not done. Nothing improves a team's engagement with retros faster than evidence that the last one changed something — and nothing kills it faster than three sprints of unactioned lists.
2. **Set the frame and the safety rule** — State that the goal is the system, not the people. The prime directive — everyone did the best they could with what they knew at the time — is worth saying aloud when the sprint went badly.
3. **Collect in silence, about specific moments** — Ask about moments rather than feelings: "which handoff cost us the most time?" beats "what went badly?". Five silent minutes, everyone writing cards, no discussion.
4. **Group and name the themes** — Cluster the cards and let the team name each cluster. Themes almost always collapse into three or four real issues even when there are thirty cards.
5. **Vote, then discuss only the top three** — Give everyone three votes. Discuss the top three themes properly rather than skimming all of them — a retro that touches everything changes nothing.
6. **Write actions that are small enough to finish** — "Improve communication" is not an action. "Anna posts the deploy checklist in the channel before each release" is. Two or three of those, each with a name and a sprint deadline.

## Prompts that get past "it was fine"

Generic prompts get generic answers. These are the ones that reliably produce real cards:

- Which moment did you feel most blocked, and who could have unblocked you?
- Where did we spend time that produced nothing we kept?
- Which handoff between people or teams cost us the most?
- What did we decide last retro that we actually did?
- What would have made this sprint one day shorter?

## Rotate the format, not every sprint

Start/Stop/Continue, Mad/Sad/Glad, 4Ls and sailboat all work; the format matters far less than the prompts and the follow-through. Change format when the team is visibly bored of the current one, roughly every five or six sprints, not every time.

## When the retro is a blame session

If discussion turns to a person, restate the question as a system question: not "why did you miss it" but "what would have caught this before release?". If it keeps happening, switch to anonymous cards for a few sprints.

## 60-minute retrospective agenda

| Time | Phase |
| --- | --- |
| 0–10 min | Review last retro's actions |
| 10–15 min | Silent card writing |
| 15–25 min | Group and name themes |
| 25–30 min | Vote |
| 30–50 min | Discuss the top three |
| 50–60 min | Agree 2–3 actions with owners |

## FAQ

**How long should a sprint retrospective be?**

About 60 minutes for a two-week sprint, and 90 for a month-long one.

**Who should attend a retrospective?**

The delivery team that did the work — adding managers or stakeholders changes what people are willing to say.

**How many actions should come out of a retrospective?**

Two or three, each small enough to finish inside the next sprint and each with a named owner.

**What do you do when a retrospective has nothing to discuss?**

Ask about a specific moment in the sprint instead of the sprint as a whole — silence usually means the question was too broad.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/how-to-facilitate-a-sprint-retrospective.

---

# Silent brainstorming and brainwriting

> Source: https://thinkdrop.io/guides/silent-brainstorming-brainwriting · Last reviewed 2026-08-21 · The thinkdrop facilitation team

Silent brainstorming, also called brainwriting, has every participant write ideas independently before anyone speaks. It removes anchoring on the first idea said aloud and lets quieter and more junior participants contribute at full weight. A typical round is five minutes of writing, then a pass where everyone builds on someone else's cards.

## Key facts

- **Writing round:** 5 minutes
- **6-3-5 method:** 6 people, 3 ideas, 5 rounds — 108 ideas in 30 minutes
- **Best for:** Mixed seniority, remote teams, sensitive topics
- **Weakness:** Less energy in the room; needs a discussion phase after

## Step by step

1. **Frame the question and show it** — Everyone writes against the same written question. In silent formats there is no chance to clarify mid-round, so the wording has to stand on its own.
2. **Write independently for five minutes** — No talking, no reading each other's cards yet. Ask for a target number per person — three is a good floor — so nobody stops at their first idea.
3. **Pass and build** — Reveal the cards and give a second round where each person extends other people's ideas rather than adding new ones. This is where brainwriting gets its combinatorial advantage over pure individual work.
4. **Repeat for as many rounds as the topic needs** — Classic 6-3-5 runs five rounds of three ideas each with six people. Two or three rounds is usually enough for a working session.
5. **Then discuss out loud** — Silent generation is not a substitute for discussion — it is what makes discussion useful. Group, vote and debate as normal once the cards exist.

## Why it outperforms open discussion for generation

Two things damage spoken brainstorming: production blocking (only one person can talk at a time, so ideas are forgotten while waiting) and anchoring (everything after the first suggestion is a variation on it). Writing in parallel removes both. The trade-off is energy — a silent room feels flat, so pair it with a lively discussion phase.

## Running it asynchronously

Brainwriting is the format that survives being spread across time zones. Open a shared board, post the question, and give people 24 hours to add cards on their own. Then run a short live call for grouping and deciding only.

## Silent formats compared

| Method | How it runs | Best for |
| --- | --- | --- |
| Simple brainwriting | 5 silent minutes, then reveal | Any session, as the opening round |
| 6-3-5 | 6 people write 3 ideas, pass 5 times | Maximum volume in 30 minutes |
| Round-robin | Each person adds to the next person's sheet | Forcing genuine build-on |
| Async board | Open 24h before the call | Distributed teams and time zones |

## FAQ

**What is brainwriting?**

A brainstorming format where participants write ideas independently and pass them on to be extended, instead of calling them out.

**Is silent brainstorming better than talking?**

It produces more distinct ideas during generation; discussion is still better for grouping and deciding.

**What is the 6-3-5 method?**

Six participants each write three ideas in five minutes, then pass their sheet on, for five rounds.

**Does silent brainstorming work remotely?**

Yes — it is the format best suited to remote and asynchronous work, since everyone writes in parallel on a shared board.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/silent-brainstorming-brainwriting.

---

# How to run a remote brainstorming session

> Source: https://thinkdrop.io/guides/remote-brainstorming-session · Last reviewed 2026-08-21 · The thinkdrop facilitation team

For a remote brainstorming session, keep it to 45 minutes, put every idea on one shared board rather than in chat, and start with five minutes of silent writing so the call does not become a queue for the microphone. Camera-on for discussion, camera optional while writing, and end with three owned actions posted in the channel.

## Key facts

- **Length:** 45 minutes maximum on video
- **Group size:** 4–8; split larger groups into breakouts
- **Silent writing:** 5 minutes, cameras optional
- **Where ideas live:** One shared board, never chat
- **Async option:** Board open 24h before the call

## Step by step

1. **Send the question before the call** — Remote sessions have no warm-up. Post the question and open the board a day ahead so people arrive with something in their head, and some cards already on the board.
2. **Use one shared board, not chat** — Ideas typed into a video call's chat are gone the moment the call ends and cannot be grouped or voted on. One live board that everyone can edit is the single biggest difference between a remote brainstorm that works and one that does not.
3. **Open with five silent minutes** — On a call only one person can speak at a time, which makes production blocking worse than in a room. Parallel writing removes the queue entirely.
4. **Cut the session to 45 minutes** — Video attention drops well before the 60 minutes an in-person session can hold. Move grouping to the board asynchronously if you run out of time; the decision is the part that needs the call.
5. **Call on people by name** — Remote silence is ambiguous — it can be thinking, a muted mic, or disengagement. Round-robin by name during discussion so nobody drops out invisibly.
6. **Post the outcome where the team lives** — Three actions with owners, in the team channel, within an hour. Remote teams forget verbal commitments faster because there is no shared room to remember them in.

## Across time zones, go asynchronous first

When there is no overlapping hour that suits everyone, run generation entirely on the board over 24 to 48 hours and use the single live slot only for grouping and deciding. This produces more cards than a synchronous session, because people add ideas when they actually have them rather than in a scheduled 20-minute window.

## What breaks in remote sessions specifically

Three failure modes are unique to remote:

- Ideas scattered across chat, docs and the call — nothing can be grouped. Fix: one board.
- The two people with the best connection dominate. Fix: written rounds.
- No one can tell whether the group is done. Fix: a visible timer and an explicit phase change.

## FAQ

**How long should a remote brainstorming session be?**

45 minutes on video, or spread generation across 24 hours on a shared board and use the call only to decide.

**What tools do you need for remote brainstorming?**

A video call plus one shared board everyone can write on in real time — chat and documents are not substitutes.

**How do you keep remote participants engaged?**

Silent written rounds, a visible timer, and calling on people by name during discussion.

**Can brainstorming work without a live meeting?**

Yes — asynchronous generation on a shared board usually produces more ideas, with one short call to group and decide.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/remote-brainstorming-session.

---

# Brainstorming techniques compared

> Source: https://thinkdrop.io/guides/brainstorming-techniques-compared · Last reviewed 2026-08-21 · The thinkdrop facilitation team

The main brainstorming techniques are brainwriting, SCAMPER, Crazy 8s, Six Thinking Hats, mind mapping, reverse brainstorming, starbursting and affinity mapping. Choose by what the session needs: brainwriting for volume, SCAMPER to improve an existing thing, Crazy 8s for fast divergence, reverse brainstorming when the team is stuck, and affinity mapping to make sense of the result.

## Key facts

- **Highest volume:** Brainwriting / 6-3-5
- **Fastest:** Crazy 8s — 8 ideas in 8 minutes
- **Best for improving something existing:** SCAMPER
- **Best when the team is stuck:** Reverse brainstorming
- **Best for making sense of output:** Affinity mapping

## Step by step

1. **Brainwriting** — Everyone writes independently, then builds on each other's cards. The default opening round for almost any session, and the highest-volume technique per minute.
2. **SCAMPER** — Walk an existing product or process through seven prompts: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse. Useful precisely because it forces angles a team would not choose on its own.
3. **Crazy 8s** — Eight ideas in eight minutes, one per minute. The time pressure is the point: it stops people polishing their first idea and forces them past the obvious three.
4. **Six Thinking Hats** — The group deliberately adopts one mode at a time — facts, feelings, risks, benefits, creativity, process. Good for mixed groups where one person always plays critic and another always plays optimist.
5. **Mind mapping** — Branch outwards from the central question. Best when the problem has structure worth exposing, weakest when you just need volume.
6. **Reverse brainstorming** — Ask how to cause the problem instead of how to solve it. "How could we guarantee new users churn in week one?" unlocks a stuck room in about two minutes, and every answer inverts into a fix.
7. **Starbursting** — Generate questions rather than answers — who, what, when, where, why, how. The right technique early, before the team has agreed what the problem even is.
8. **Affinity mapping** — Not a generation technique but the convergence step: cluster the cards into named themes. Almost every session should end with it.

## Pick by the failure you are trying to avoid

Techniques are not interchangeable. If the room is quiet, the problem is psychological safety — use silent brainwriting. If the ideas are all minor variations, the problem is anchoring — use Crazy 8s or reverse brainstorming. If you have 60 cards and no decision, the problem is convergence — use affinity mapping and dot voting.

## Technique selection

| Technique | Use it when | Time |
| --- | --- | --- |
| Brainwriting | You need volume and equal participation | 10–20 min |
| SCAMPER | Improving something that already exists | 30 min |
| Crazy 8s | The team keeps circling the obvious | 8 min |
| Six Thinking Hats | Mixed group with fixed roles | 45 min |
| Mind mapping | The problem has structure to expose | 20 min |
| Reverse brainstorming | The room is stuck | 15 min |
| Starbursting | The problem is not yet defined | 20 min |
| Affinity mapping | You have cards and need a decision | 15–20 min |

## FAQ

**What is the most effective brainstorming technique?**

Brainwriting produces the most distinct ideas per minute, which is why it works as the opening round for nearly every session.

**What is SCAMPER used for?**

Improving something that already exists, by forcing seven specific angles on it.

**When should you use reverse brainstorming?**

When a group is stuck — asking how to cause the problem unlocks answers that invert directly into solutions.

**How do you narrow down after brainstorming?**

Cluster the cards into named themes with affinity mapping, then dot-vote and take the top three.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/brainstorming-techniques-compared.

---

# How long should a brainstorming session be?

> Source: https://thinkdrop.io/guides/how-long-should-a-brainstorming-session-be · Last reviewed 2026-08-21 · The thinkdrop facilitation team

A brainstorming session should last 45 to 60 minutes, with idea generation timeboxed to 15 to 20 minutes inside it. Remote sessions should be capped at 45 minutes because video attention drops sooner. Beyond an hour, idea quality falls and the group starts repeating itself, so run a second session rather than extending the first.

## Key facts

- **In-person session:** 60 minutes
- **Remote session:** 45 minutes
- **Idea generation:** 15–20 minutes, timeboxed
- **Silent opening round:** 5 minutes
- **Crazy 8s round:** 8 minutes
- **Point of diminishing returns:** ~60 minutes

## Step by step

1. **Budget 60 minutes in person** — Five to frame, five silent, twenty building, fifteen grouping, ten deciding, five assigning. That split leaves enough room for the two phases teams usually skip: grouping and assigning.
2. **Budget 45 minutes remotely** — Cut the building phase, not the deciding phase. Attention on video degrades faster, and a session that ends without owners was not worth the calendar slot.
3. **Timebox generation visibly** — Put a timer where everyone can see it. Open-ended generation produces fewer ideas than a visible 20-minute limit, because the deadline is what stops people editing themselves.
4. **Split rather than extend** — If the topic genuinely needs more, run two sessions a few days apart. The gap does real work — people arrive at the second one with ideas they had in the shower.

## Where the time actually goes wrong

Most sessions overrun on generation and then run out of time for convergence, which is why so many end with a photo of a board and no decision. Protect the last 20 minutes: grouping, voting and assigning are what turn a session into work.

## Asynchronous sessions run on a different clock

When the board is open for 24 to 48 hours, generation is effectively unlimited and cheap, and the only synchronous cost is a 20 to 30 minute call to group and decide. For distributed teams this is usually the better trade.

## FAQ

**How long should a brainstorming session be?**

45 to 60 minutes, with idea generation timeboxed to 15 to 20 of them.

**Can a brainstorming session be too long?**

Yes — past about an hour, idea quality drops and the group starts restating what is already on the board.

**How long should a remote brainstorm be?**

45 minutes maximum on video, or asynchronous generation plus a short call to decide.

**How much time should be left for choosing ideas?**

At least the final 20 minutes, for grouping, voting and assigning owners.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/how-long-should-a-brainstorming-session-be.

---

# What is brainstorming?

> Source: https://thinkdrop.io/guides/what-is-brainstorming · Last reviewed 2026-08-21 · The thinkdrop facilitation team

Brainstorming is a structured group technique for producing a large number of ideas about one specific question before any of them are judged. Alex Osborn described it in 1953 with four rules: defer criticism, welcome wild ideas, aim for quantity, and combine and improve on others' ideas. Evaluation happens afterwards, as a separate step.

## Key facts

- **Coined by:** Alex Osborn, Applied Imagination (1953)
- **Original rules:** 4 — defer judgement, wild ideas, quantity, build on others
- **Typical group size:** 4–8 participants
- **Typical length:** 45–60 minutes
- **Core principle:** Separate generating from judging
- **Main failure mode:** Evaluating ideas while still generating them

## Step by step

1. **Start from a question, not a topic** — Brainstorming is aimed at a single, answerable question. "Retention" is a subject; "What makes a customer cancel in month two?" is a brainstorming question. The narrower the question, the more concrete the ideas.
2. **Defer judgement** — No critique, no "we tried that", no cost objections during generation. This is the rule that produces the volume; it is also the one groups break first, usually within the opening two minutes.
3. **Welcome wild ideas** — Impractical ideas are cheap and they widen the range the group is willing to consider. It is far easier to tame an extreme idea than to make a cautious one interesting.
4. **Go for quantity** — Quantity is the proxy you can actually manage. Set a visible target — 40 cards, say — because groups that chase a number stop self-editing and the later ideas are usually the less obvious ones.
5. **Combine and improve** — Ideas belong to the board, not their author. Read what others wrote and extend it: "yes, and" rather than "no, but". Most usable outcomes are a merge of two half-ideas.
6. **Judge in a separate pass** — Once generation stops, switch modes explicitly: group into themes, react or vote, then pick the two or three worth owning. Announce the switch out loud so nobody is still generating while others are critiquing.

## Group brainstorming vs individual brainstorming

Decades of research on "production blocking" find that the same people writing ideas alone produce more distinct ideas than they do talking in one room, because only one person can speak at a time and everyone else is holding their thought. The practical answer is not to abandon the group but to write first and talk second: silent generation captures the range, discussion combines and improves it.

## When brainstorming is the wrong tool

Brainstorming produces options. It does not produce decisions, and it is a poor fit for questions that already have a correct answer.

- The question has one verifiable answer — research it instead.
- The decision is already made and the meeting is looking for agreement — say so instead.
- The group lacks the context to have an opinion — brief them first, brainstorm later.
- The real constraint is capacity, not ideas — prioritise the backlog instead.

## Where the technique came from

Alex Osborn, an advertising executive, formalised brainstorming in Applied Imagination in 1953 after running "think-up" sessions at his agency. His central claim was that judgement suppresses imagination, so the two activities must be separated in time. Almost every modern variant — brainwriting, crazy 8s, six thinking hats — is a different mechanism for enforcing that separation.

## Brainstorming formats compared

| Format | How it works | Best for |
| --- | --- | --- |
| Classic verbal | Group calls out ideas, one scribe | Small, high-trust groups |
| Brainwriting | Everyone writes silently, then swaps | Mixed seniority, quiet teams |
| Online board | Everyone posts cards at once | Remote and hybrid groups |
| Asynchronous | Board open for 24h, then a short call | Distributed timezones |

## FAQ

**What is brainstorming in simple terms?**

Generating as many ideas as possible for one question, with all judgement postponed until afterwards.

**What are the four rules of brainstorming?**

Defer judgement, welcome wild ideas, aim for quantity, and build on other people's ideas.

**Who invented brainstorming?**

Advertising executive Alex Osborn, who published the method in Applied Imagination in 1953.

**Is brainstorming actually effective?**

Yes when generation is silent and individual first, and less so when the group only talks, because people block each other.

**What is the difference between brainstorming and ideation?**

Ideation is the whole process of creating and refining ideas; brainstorming is one technique used inside it.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/what-is-brainstorming.

---

# 17 brainstorming tips that change the output

> Source: https://thinkdrop.io/guides/brainstorming-tips · Last reviewed 2026-08-21 · The thinkdrop facilitation team

The tips that change a brainstorm's output are structural, not motivational: ask one narrow question, have everyone write silently for five minutes before anyone speaks, set a visible idea target, timebox generation to 20 minutes, ban evaluation until the timer ends, and finish by assigning three ideas to named owners with dates.

## Key facts

- **Silent start:** 5 minutes, before any discussion
- **Generation timebox:** 20 minutes
- **Idea target:** 40+ cards
- **Group size:** 4–8 people
- **Ideas carried forward:** 3, each with an owner
- **Facilitator contribution:** None during generation

## Step by step

1. **Send the question 24 hours early** — People who have slept on the question arrive with ideas. The ones who did not think about it still start from zero in the silent round, so nothing is lost.
2. **Make the question uncomfortably narrow** — If the question could be answered by three different departments in three different ways, it is too broad. Split it and run two shorter sessions.
3. **Start silent, always** — Five minutes of independent writing before anyone speaks removes the anchoring effect of the first idea said out loud, and gives you a floor of cards even if the discussion is slow.
4. **Put a number on the wall** — "Forty cards before we stop" changes behaviour more than "lots of ideas". Groups chasing a count stop pre-filtering, and the second half of the list is where the unusual ideas live.
5. **Park every objection out loud** — When someone evaluates during generation, say "park it" and write the objection on a card of its own. The concern is preserved, the rule holds, and you only have to do it once or twice.
6. **Rotate who reads out** — If one person always summarises, their framing wins. Ask a different participant to read a cluster back to the group and the interpretation shifts with them.
7. **End with owners, not applause** — Three ideas, three names, three dates, written where the team will see them again. Without that, the session's output is a screenshot nobody opens.

## Tips for the facilitator

The facilitator protects the structure rather than contributing content.

- Do not add your own ideas during generation — your role makes them weigh more than they should.
- Restate the question every time the group drifts, without apologising for it.
- Write down ideas people only say out loud; unrecorded ideas do not survive the meeting.
- Watch for the person who has not posted anything and give the room a second silent round.
- Keep the timer visible; a timebox nobody can see is not a timebox.

## Tips for the group

Participants can improve the session without any authority over it.

- Write short cards — one idea per card, so it can be grouped and voted on.
- Read other cards before writing more; that is where combinations come from.
- Post the obvious idea anyway. Someone has to, and it clears the way for the next one.
- Say "yes, and" out loud; the phrase does real work in keeping the tone additive.

## Tips for remote and hybrid sessions

Remote brainstorms fail for a different reason than in-person ones: not dominance, but silence that no one can interpret. Use a shared board so contribution is visible without speech, keep video sessions to 45 minutes, and let cards accumulate asynchronously before the call so the live time is spent grouping and deciding rather than typing.

## Common problem, mechanical fix

| Problem | Fix |
| --- | --- |
| One person dominates | Silent written round; read cards anonymously |
| Ideas are all obvious | Set a card target and keep going past the lull |
| Group critiques too early | Name the rule, park objections on their own cards |
| Nothing happens afterwards | Three owners and dates before anyone leaves |
| Remote group is silent | Shared board where posting replaces speaking |
| Session overruns | Visible timer, hard stop on generation |

## FAQ

**What is the single most effective brainstorming tip?**

Have everyone write ideas silently for five minutes before anyone speaks.

**How do you stop one person dominating a brainstorm?**

Collect written cards first so every contribution is visible before discussion starts.

**How do you brainstorm when the group runs out of ideas?**

Push past the lull with a card target, or change the constraint — half the budget, twice the users, no engineers.

**Should the facilitator contribute ideas?**

Not during generation; the facilitator's ideas carry extra weight and narrow the group's range.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/brainstorming-tips.

---

# Brainstorming session templates you can run today

> Source: https://thinkdrop.io/guides/brainstorming-session-templates · Last reviewed 2026-08-21 · The thinkdrop facilitation team

A brainstorming template is a timed agenda plus starter prompts, so the session begins without setup. The five that cover most needs are a 30-minute quick brainstorm, a 60-minute classic session, a sprint retrospective, a problem-solving session using how-might-we framing, and an asynchronous board left open for 24 hours.

## Key facts

- **Templates here:** 5, each with a timed agenda
- **Shortest:** 30 minutes
- **Longest live session:** 60 minutes
- **Asynchronous window:** 24 hours plus a 20-minute call
- **Starter cards per template:** 5–6
- **Cost to run on thinkdrop:** Free to start, $0.99/month after trial

## Step by step

1. **Pick the template that matches your time, not your ambition** — A well-run 30-minute session beats a 90-minute one that loses the room at minute forty. Choose by the time you genuinely have.
2. **Replace the question with your own** — Each template's starter cards are prompts, not answers. Swap in the specific question you need ideas for before you share the board.
3. **Post the agenda where participants can see it** — People contribute differently when they know a grouping phase is coming — they write more freely, because they know filtering happens later.
4. **Run the silent phase without exception** — Every template starts silent. It is the single step that most changes the range of what gets written.
5. **Close the board and send the summary the same day** — The output of a session is a written record with owners. Sent within the hour it gets read; sent two days later it does not.

## Session templates

### 30-minute quick brainstorm

Best for: One narrow question, a small team, no time to prepare. Length: 30 minutes.

Agenda:

- 0–3 min — Read the question aloud, state the two ground rules
- 3–8 min — Silent card writing, no talking
- 8–18 min — Build on each other's cards
- 18–25 min — Group into themes and react
- 25–30 min — Pick two, assign owners

Starter cards:

- What would we try if we had one week and no budget?
- What has a customer asked for twice this month?
- What is the smallest version of this we could ship?
- What are we doing only because we have always done it?
- What would a competitor do here?

Start this template: https://thinkdrop.io/guides/brainstorming-session-templates

### 60-minute classic session

Best for: A significant question with a mixed group. Length: 60 minutes.

Agenda:

- 0–5 min — Frame the question, ground rules
- 5–10 min — Silent generation
- 10–30 min — Build, extend, combine
- 30–45 min — Cluster into 5–8 named themes
- 45–55 min — Vote and pick the top three
- 55–60 min — Owner and date for each

Starter cards:

- What is the real problem behind the one we were asked to solve?
- Who is affected by this that is not in the room?
- What would make this ten times easier rather than ten percent better?
- What is the boring option we are avoiding?
- What would we regret not trying?
- What constraint would we remove first?

Start this template: https://thinkdrop.io/guides/brainstorming-session-templates

### Sprint retrospective

Best for: A team closing a sprint or a release. Length: 45 minutes.

Agenda:

- 0–5 min — Recap the sprint, no discussion
- 5–12 min — Silent cards: went well / did not / change
- 12–30 min — Discuss the most-reacted cards only
- 30–40 min — Agree two changes for next sprint
- 40–45 min — Owners and how we will know it worked

Starter cards:

- What went well that we should keep doing deliberately?
- Where did we lose the most time?
- What surprised us this sprint?
- What did we decide but not do?
- What should we stop doing entirely?

Start this template: https://thinkdrop.io/guides/brainstorming-session-templates

### Problem-solving (how might we)

Best for: A recurring problem nobody has framed properly. Length: 60 minutes.

Agenda:

- 0–10 min — Describe the problem, no solutions allowed
- 10–20 min — Rewrite it as three "how might we" questions
- 20–25 min — Vote on which question to solve
- 25–45 min — Generate ideas against that one question
- 45–60 min — Cluster, choose, assign

Starter cards:

- How might we remove the step people complain about most?
- How might we make the failure obvious before it costs anything?
- How might we solve this for the ten percent hardest cases?
- How might we make the current workaround unnecessary?
- How might we solve this without building anything?

Start this template: https://thinkdrop.io/guides/brainstorming-session-templates

### Asynchronous 24-hour board

Best for: Distributed teams across timezones. Length: 24 hours plus a 20-minute call.

Agenda:

- Day 1, morning — Open the board with the question and prompts
- Day 1 — Everyone adds cards on their own time
- Day 2, morning — Facilitator clusters the cards into themes
- Day 2 call, 0–10 min — Walk the themes
- Day 2 call, 10–20 min — Vote, choose, assign owners

Starter cards:

- Add one idea you would not say out loud in a meeting.
- What does this look like from your timezone or market?
- What do you already know that the rest of us probably do not?
- Which of the cards above would you build first, and why?
- What is missing from this board?

Start this template: https://thinkdrop.io/guides/brainstorming-session-templates

## What a good template actually contains

A template earns its place by removing decisions from the facilitator at the moment they are busiest. That means three things: a timed agenda with phase boundaries, a small set of starter prompts so the board is never empty, and an explicit end state — what the group leaves with. Anything beyond that is decoration.

## Adapting a template to your team

Shorten the generation phase before you shorten the grouping phase; groups usually have enough ideas and too little time to make sense of them. If your team is quiet, add a second silent round rather than more discussion. If it is loud, run generation entirely on cards and use speech only during clustering.

## Which template to use

| Situation | Template | Length |
| --- | --- | --- |
| Narrow question, little time | 30-minute quick brainstorm | 30 min |
| Significant question, mixed group | 60-minute classic | 60 min |
| End of a sprint | Sprint retrospective | 45 min |
| Recurring, badly framed problem | How might we | 60 min |
| Team across timezones | Asynchronous board | 24h + 20 min |

## FAQ

**What is a brainstorming template?**

A timed agenda plus starter prompts, so a session can begin without the facilitator designing it first.

**How long should a brainstorming template run?**

Thirty minutes for one narrow question, sixty for a significant one, or asynchronously over 24 hours for distributed teams.

**Can I run these templates for free?**

Yes — you can start any of them on a free thinkdrop board and share the link with your team.

**How many starter cards should a template have?**

Five or six: enough that the board is never empty, few enough that they do not define the answer.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/brainstorming-session-templates.

---

# 60 brainstorming questions that unstick a session

> Source: https://thinkdrop.io/guides/brainstorming-questions · Last reviewed 2026-08-21 · The thinkdrop facilitation team

A good brainstorming question is specific, open, and answerable by everyone in the room. Use opening questions to start the board, reframing questions when ideas repeat, provocation questions when the group runs dry, and prioritisation questions to close. Rewriting the question is usually faster than pushing a stuck group harder.

## Key facts

- **Questions listed:** 60, grouped by purpose
- **Best question length:** One sentence
- **Questions per session:** One main question, 2–3 provocations
- **When to reframe:** After ~10 minutes with no new angle
- **Worst question type:** Anything answerable with yes or no

## Step by step

1. **Open with a question everyone can answer** — The first question sets participation. Ask something every person in the room has direct experience of — what they have seen, heard or tried — rather than something only the specialists can address.
2. **Reframe when ideas start repeating** — Repetition is a signal about the question, not the group. Rewrite it: change the actor, the timescale, the constraint, or invert it entirely.
3. **Provoke when the board goes quiet** — Drop in a constraint question — half the budget, ten times the users, no engineers, ship on Friday. Artificial constraints reliably produce ideas the open question did not.
4. **Close with a question about commitment** — "Which of these would you personally start on Monday?" surfaces the difference between ideas people like and ideas people will do.

## Opening questions

Use one of these as the board's main question, or as the first prompt card.

- What is the real problem behind the one we were asked to solve?
- What would we do if we had to fix this by Friday?
- What has a customer told us twice in the last month?
- What do we all quietly know is not working?
- If we started this from scratch today, what would we not rebuild?
- Who is affected by this that is not in this room?
- What is the smallest version of this we could ship?
- What did we assume when we set this up, that is no longer true?
- Where do people work around our process?
- What would make this ten times easier rather than ten percent better?

## Reframing questions

Reach for these when ideas start repeating each other.

- How might we make the problem irrelevant instead of solving it?
- What would this look like if it were free?
- What if we only had one week?
- Who has already solved a version of this, in any industry?
- What would we do if this were our only product?
- What would we stop doing to make room for this?
- How would we cause this problem deliberately?
- What does the person who disagrees with us see?
- What would the simplest possible version look like?
- What if the constraint we are working around is the actual product?

## Provocation questions

Constraint questions for when the board goes quiet.

- What would we do with half the budget?
- What would we do with ten times the users?
- What if no engineer were available for a month?
- What would a competitor announce tomorrow that would worry us?
- What is the laziest possible solution?
- What is the most expensive one, and what does it teach us?
- What would we try if failure had no consequences?
- What would we do if this had to work offline?
- What if we had to explain it in one sentence to a new customer?
- What if we removed the feature everyone assumes is essential?

## Prioritisation questions

Use these once generation has stopped and you are choosing.

- Which of these would you personally start on Monday?
- Which one, if it worked, makes the others unnecessary?
- What is cheap to test and quick to learn from?
- Which idea are we avoiding because it is uncomfortable rather than wrong?
- What would we regret not trying by the end of the quarter?
- Which of these needs a decision rather than more work?
- What can one person finish without waiting for anyone else?
- Which idea has an obvious owner already in the room?

## Question type by moment in the session

| Moment | Question type | Example |
| --- | --- | --- |
| Start | Opening | What is the real problem behind this one? |
| Ideas repeat | Reframing | What would this look like if it were free? |
| Board goes quiet | Provocation | What would we do with half the budget? |
| Choosing | Prioritisation | Which would you start on Monday? |

## FAQ

**What makes a good brainstorming question?**

One sentence, specific, open-ended, and answerable by everyone present rather than only the experts.

**How many questions should a brainstorm have?**

One main question, plus two or three provocations held back for when the group slows down.

**What questions should you avoid in a brainstorm?**

Yes-or-no questions and questions so broad that different departments would answer entirely different things.

**What do you ask when a brainstorm stalls?**

A constraint question — half the budget, ten times the users, ship on Friday — which reliably produces new angles.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/brainstorming-questions.

---

# Group vs individual brainstorming: what the evidence says

> Source: https://thinkdrop.io/guides/group-vs-individual-brainstorming · Last reviewed 2026-08-21 · The thinkdrop facilitation team

Individuals working alone usually generate more distinct ideas than the same people brainstorming out loud together, because only one person can speak at a time and the rest lose their thought. Groups are better at combining and evaluating ideas. The practical format is hybrid: generate alone in silence, then combine and choose as a group.

## Key facts

- **Better at volume:** Individuals writing separately
- **Better at combining:** Groups
- **Main group cost:** Production blocking — one speaker at a time
- **Other group costs:** Evaluation apprehension, social loafing
- **Recommended format:** Silent individual generation, then group synthesis
- **Silent phase length:** 5–10 minutes

## Step by step

1. **Generate alone, in writing** — Give everyone the question and five to ten silent minutes. Nobody speaks, nobody sees each other's cards yet. This is the phase that produces the range.
2. **Pool everything before discussing** — Put all the cards on one board at the same time so no single idea gets the advantage of being first. Read before talking.
3. **Combine as a group** — Now use the group for what it is good at: spotting that two cards are the same idea, that a third solves a problem in a fourth, and that a fifth is only interesting if you invert it.
4. **Evaluate together, decide explicitly** — Groups evaluate better than individuals because objections surface from different angles. React or vote, then name the owner — a group that evaluates without deciding just produces a longer list.

## Why groups under-produce ideas

Three effects are consistently identified in the research literature on group ideation, and all three are structural rather than a matter of effort or attitude.

- Production blocking: only one person can talk at a time, so everyone else waits, rehearses and forgets.
- Evaluation apprehension: people withhold unfinished ideas in front of colleagues and managers.
- Social loafing: individual contribution is invisible in a group, so effort quietly drops.

## What groups are genuinely better at

The same group that under-produces raw ideas outperforms individuals at recognising which ideas matter. Combination is inherently social — one person's half-formed card becomes useful when someone with different context extends it. Evaluation benefits from disagreement, and commitment is far stronger when the choice was made in the room rather than delivered afterwards.

## The hybrid format in practice

Send the question in advance so people can think alone. Open the session with silent writing on a shared board. Reveal all the cards at once, then spend the majority of the live time grouping, arguing and choosing. This is the format most modern facilitation guidance converges on, and a shared online board makes it the default rather than something the facilitator has to enforce.

## Group vs individual, by dimension

| Dimension | Individual | Group |
| --- | --- | --- |
| Number of distinct ideas | Higher | Lower |
| Range of perspectives | Limited to one | Wide |
| Combining half-ideas | Weak | Strong |
| Evaluating quality | Biased toward own ideas | Stronger |
| Commitment to outcome | Low for others | High |
| Time cost | Low | High |

## FAQ

**Is group brainstorming better than individual brainstorming?**

Not for producing ideas — individuals writing alone generate more distinct ideas — but groups are better at combining and choosing them.

**What is production blocking?**

In a spoken group only one person talks at a time, so everyone else waits and loses the idea they were holding.

**What is the best of both approaches?**

Silent individual writing first, then group discussion to combine, evaluate and decide.

**Does brainwriting solve the problem?**

Largely, yes: everyone writes in parallel, so no one is blocked, and the ideas still circulate through the group.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/group-vs-individual-brainstorming.

---

# How to choose an online brainstorming tool

> Source: https://thinkdrop.io/guides/online-brainstorming-tools · Last reviewed 2026-08-21 · The thinkdrop facilitation team

Choose an online brainstorming tool by how little it asks of participants. The features that change outcomes are guest access with no account, real-time cards so everyone posts at once, a silent generation mode, simple reactions or voting, and an automatic written summary. Infinite canvases and template galleries rarely decide whether a session works.

## Key facts

- **Most important feature:** Participants join without an account
- **Second:** Real-time cards from everyone at once
- **Third:** A written summary after the session
- **Typical setup time to aim for:** Under 2 minutes
- **thinkdrop price:** $0.99 per month, 7-day free trial
- **thinkdrop guest access:** Yes — link only, no signup

## Step by step

1. **Check what participants have to do before contributing** — Count the steps between receiving a link and posting a first card. Every account, install or workspace invitation removes a share of the room, and it is usually the least persistent people whose ideas you most wanted.
2. **Confirm cards appear in real time** — Everyone posting at once is the mechanism that removes production blocking. A tool where people take turns, or where updates lag by seconds, quietly reverts you to a spoken meeting.
3. **Look for a silent generation phase** — Either a hidden-cards mode or simply a board people can write to before discussion opens. Without it the facilitator has to enforce silence verbally every session.
4. **Check how the group chooses** — Reactions or votes need to be one click and visible instantly, otherwise prioritisation eats the last fifteen minutes. The option to disable downvoting matters for retrospectives.
5. **Check what you leave with** — A screenshot of sticky notes is not an outcome. Look for an export or an automatic summary that names the themes, the most-supported ideas and the next steps.
6. **Price it per month, for real usage** — Per-seat pricing punishes exactly the behaviour you want — inviting more people. Prefer tools where participants are free and the facilitator pays a small flat amount.

## Features that look important but rarely are

Tool comparisons are dominated by capabilities that do not affect whether a session produces decisions.

- Infinite canvas: impressive in a demo, hard to read back a week later.
- Huge template galleries: you will use two of them, repeatedly.
- Freehand drawing: unusable for the half of the room on a laptop trackpad.
- Video conferencing built in: your team already has a call tool they prefer.

## Where AI actually helps

Two moments justify AI in a brainstorming tool. The first is the lull, when the group has exhausted the obvious and a set of unexplored angles restarts the board. The second is the write-up, which is the step that most often never happens: a summary naming themes, the best-supported ideas and next steps turns a session into something the team can act on the same day.

## How thinkdrop approaches it

thinkdrop is deliberately narrow: a facilitator creates a board and shares a link, participants join with no account, cards and reactions appear live, AI tops up the board when it stalls and writes the summary when the session closes. Boards can repeat weekly, biweekly or monthly for recurring rituals. It costs $0.99 per month after a one-time 7-day free trial, and participants are always free.

## A checklist to evaluate any tool

| Question | Why it matters |
| --- | --- |
| Can participants join without an account? | Every signup step loses contributors |
| Do cards appear live for everyone? | Removes waiting-to-speak blocking |
| Is there a silent generation phase? | Prevents anchoring on the first idea |
| Is voting one click? | Prioritisation must not eat the session |
| Is there a written summary? | Otherwise nothing survives the meeting |
| Is pricing per seat? | Per-seat pricing discourages inviting people |

## FAQ

**What is the best online brainstorming tool?**

The one your participants can join from a link without an account and post to in real time; everything else is secondary.

**Do participants need an account to use thinkdrop?**

No — only the facilitator who creates the board needs an account, and participants join from the link.

**How much should an online brainstorming tool cost?**

Little, and not per seat; thinkdrop is $0.99 per month for the facilitator with a one-time 7-day free trial.

**Can AI run a brainstorm for you?**

It can generate starter cards and write the summary, but the choosing and the ownership still have to come from the group.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/online-brainstorming-tools.

---

# Brainstorming with remote and hybrid teams

> Source: https://thinkdrop.io/guides/brainstorming-with-remote-and-hybrid-teams · Last reviewed 2026-08-26 · The thinkdrop facilitation team

For hybrid brainstorming, put everyone on their own device even if some people share a room, and collect ideas in writing before anyone speaks. The failure mode is not technology — it is that the people physically together dominate the conversation while remote participants wait for a gap that never comes.

## Key facts

- **Session length:** 45 minutes
- **Silent writing:** 6 minutes
- **Devices:** One per person, always
- **Max group size:** 10, then split
- **Camera rule:** On during discussion, optional while writing

## Step by step

1. **Give every person their own device** — The moment three people share one laptop in a meeting room, they become one participant and the remote half becomes an audience. One device per person equalises input regardless of where anyone is sitting. In the room, mute all but one machine to avoid feedback.
2. **Send the question before the session** — Remote participants think better when they have not just come out of another call. Send the single question 24 hours ahead and say explicitly that arriving with two ideas is expected, not keen.
3. **Write first, in silence, for six minutes** — Slightly longer than a co-located session, because typing is slower than talking and because remote participants get no non-verbal cue that it is safe to start. Nobody speaks and nobody unmutes until the timer ends.
4. **Read the board before discussing it** — Give two minutes of silent reading. This replaces the natural milling-around that happens with physical sticky notes and stops the discussion being dominated by whoever speaks first.
5. **Call on people by name, in a fixed order** — In hybrid sessions, waiting for volunteers systematically favours the room over the remote participants. Go around a named list once. It feels stiff for the first minute and then it is simply how the meeting works.
6. **Close with owners and a written summary** — Remote participants lose the corridor conversation that follows an in-person session, so the write-up matters more. Three actions, three names, one dated summary sent to everyone before the call ends.

## The hybrid trap

Hybrid is harder than fully remote, not easier. In a fully remote session everyone has the same channel and the same latency. In a hybrid one there are two rooms with different rules: the physical room has side conversations, body language and instant turn-taking, while the remote participants have a 200ms delay and no way to signal that they were about to speak. Every hybrid facilitation technique is really an attempt to make the physical room behave more like the remote one.

## Timezones change the format, not just the time

Past about four hours of spread, stop trying to find a slot. Run the idea generation asynchronously over 24 hours on a board people add to when they are awake, then hold a 25-minute live session for grouping and deciding only. You get more ideas and a shorter meeting.

- Async generation: 24 hours, everyone contributes when awake.
- Live session: 25 minutes, grouping and decisions only.
- Record the live session for anyone who genuinely cannot attend.
- Never make the same region always take the bad slot.

## A 45-minute hybrid agenda

0–3 frame the question. 3–9 silent writing on individual devices. 9–11 silent reading. 11–25 named round, one contribution each, building on what is there. 25–35 group into themes, timeboxed hard. 35–42 vote and pick three. 42–45 assign owners and generate the summary.

## FAQ

**Should remote participants keep cameras on?**

On during discussion, because it is the only turn-taking signal remote people have; optional during silent writing, where being watched while thinking helps nobody.

**How many people is too many for a hybrid brainstorm?**

Ten. Beyond that, split into two boards with two facilitators and merge the results, because the named round alone will consume the session.

**Is fully remote better than hybrid?**

For idea generation, often yes. A fully remote session has one set of rules for everyone, which is why some teams ask the people in the office to join from their own desks.

**What if some participants will not contribute in writing?**

Let them dictate to the facilitator, but keep the card anonymous like everyone else's. The point of writing first is anchoring, not typing.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/brainstorming-with-remote-and-hybrid-teams.

---

# How to get quiet people to contribute

> Source: https://thinkdrop.io/guides/how-to-get-quiet-people-to-contribute · Last reviewed 2026-08-26 · The thinkdrop facilitation team

The reliable way to get quiet people contributing is to change the format rather than the person: start with silent written input, keep idea entry anonymous, and use a named round instead of waiting for volunteers. Asking someone directly to speak up in an open discussion usually produces agreement with whatever was said last.

## Key facts

- **Silent start:** 5 minutes, every session
- **Named round:** One contribution each, no skipping
- **Anonymity:** Generation only, not decisions
- **Air-time target:** No one above 30% of talk time
- **Group size:** Split above 8 people

## Step by step

1. **Start in silence, always** — Five minutes of individual writing before anyone speaks removes the single biggest barrier: having to compete for a gap in a conversation that has already started. It also means the quiet participant's idea exists in writing before the confident participant's idea exists in the air.
2. **Make idea entry anonymous** — Not because people are afraid, but because attribution invites the group to weigh the source instead of the idea. Anonymity during generation regularly surfaces the concern everyone had and nobody wanted to be the one to raise.
3. **Use a named round instead of open floor** — "Anyone else?" is answered by the same three people in every organisation on earth. Go around a list by name, one contribution each, with an explicit "pass" allowed. Passing without penalty is what makes the round safe rather than an interrogation.
4. **Give the question in advance** — People who process before speaking are disadvantaged by surprise, not by the topic. Twenty-four hours' notice of the exact question converts several silent participants into prepared ones.
5. **Interrupt the interrupter, once** — One calm "let's finish that thought" from the facilitator sets the norm for the whole session. Doing it once early is far more effective than doing it repeatedly later, and far more effective than any amount of encouragement aimed at the quiet person.
6. **Attribute credit in the summary** — If an idea from a quiet participant becomes a decision, name them in the write-up. Contributing has to be visibly worth it, or the next session reverts.

## Quiet is not the same as disengaged

Three different things produce silence and they need different responses. Processing style: the person needs time and will contribute in writing. Safety: the person has judged that saying the real thing is costly, which is a management problem the meeting format can only partly fix. Disengagement: the person does not think the session matters, which is usually correct and is fixed by making sessions produce visible outcomes.

- Processing style → silent writing and advance notice.
- Safety → anonymity, and fixing what made it unsafe.
- Disengagement → show that the last session changed something.

## What not to do

Do not put someone on the spot in an open discussion, do not use their name as a prompt for the group to look at them, and do not treat volume as engagement. The person who has said nothing may have written the two best cards on the board, which is exactly why the board matters more than the microphone.

## Measure air time occasionally

Once a quarter, have someone tally roughly who spoke and for how long. Facilitators consistently underestimate their own share, and a single number does more to change behaviour than any amount of intention.

## FAQ

**Does anonymity reduce accountability?**

It does, which is why it belongs to the generation phase only. Once you move to decisions and actions, put names on everything.

**What if someone always passes in the round?**

Let them. A pass that is genuinely free is what makes the round safe; a pass that is questioned turns the round into pressure and people stop writing honestly too.

**Do smaller groups help?**

Substantially. Splitting eight people into two groups of four roughly doubles everyone's available air time and is the cheapest intervention available.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/how-to-get-quiet-people-to-contribute.

---

# Affinity mapping, step by step

> Source: https://thinkdrop.io/guides/affinity-mapping-how-to · Last reviewed 2026-08-26 · The thinkdrop facilitation team

Affinity mapping means sorting a pile of individual notes into themes that emerge from the notes themselves rather than from categories you decided in advance. Group in silence first, name the clusters only after they exist, keep a miscellaneous pile, and timebox the whole thing to fifteen minutes or it will expand to fill the session.

## Key facts

- **Timebox:** 15 minutes for up to 60 notes
- **Silent grouping:** First 5 minutes
- **Target clusters:** 5–8, never more than 10
- **Naming:** After grouping, never before
- **Miscellaneous pile:** Always allowed

## Step by step

1. **Get every idea onto its own card** — One thought per card. A card containing two ideas will be argued about for five minutes and then split anyway, so split it at the start. Short beats complete: the card is a pointer to a conversation, not the conversation.
2. **Read everything before touching anything** — Two minutes of silent reading. Groups that start moving cards immediately end up with themes that reflect the first ten notes read rather than the whole set.
3. **Group in silence** — Five minutes where anyone can move any card and nobody explains why. Cards that get moved back and forth are the interesting ones — they belong to two themes, which is information rather than a problem. Silence stops the exercise turning into a debate about taxonomy.
4. **Name the clusters last** — Only once the piles exist should you name them, and the name should describe what is in the pile rather than the category you hoped for. "Onboarding" is a category; "People do not know what to do after signing up" is a theme, and it is far more useful.
5. **Keep a miscellaneous pile and do not force it** — There is always a set of cards that belong nowhere, and some of them are the most original ideas in the room. Forcing them into a theme is how good ideas get lost. Leave them visible.
6. **Vote on themes, not on cards** — Once themes exist, dot-vote on themes. Voting on individual cards rewards whoever wrote the most cards on a topic rather than the topic's importance.

## Why grouping eats the clock

Affinity mapping is the phase that overruns in nearly every session that overruns. The cause is almost always the same: the group is trying to produce a correct taxonomy rather than a workable one. There is no correct grouping of 60 subjective notes. Aim for good enough to decide on, and set a visible timer.

## When it works and when it does not

It works on a pile of comparable items: research notes, retro observations, ideas from a brainstorm, support tickets. It works badly on items of different types — mixing a strategy statement, a bug and a feature request produces clusters organised by type rather than by meaning. Sort by type first if your pile is mixed.

- Good input: 30–80 comparable, one-thought notes.
- Bad input: fewer than 15 notes, where themes are already obvious.
- Bad input: mixed types — split those into separate maps.

## Doing it remotely

Remotely, silent grouping is easier than in person because nobody can hover. What is harder is seeing the whole set at once, so keep the card count below 60 and give a longer reading window. Automatic clustering is useful as a first draft, provided the group treats it as something to correct rather than accept.

## FAQ

**How many themes should come out of it?**

Five to eight. More than ten means you have re-listed the cards; fewer than four usually means the themes are so broad they cannot be acted on.

**Who moves the cards?**

Everyone, at the same time, in silence. A single person sorting on behalf of the group produces one person's mental model with an audience.

**Can AI do the grouping?**

It can produce a fast first draft, which is genuinely useful on 60 notes. Treat the output as a starting arrangement the group edits, because the disagreements about where a card belongs are where the insight is.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/affinity-mapping-how-to.

---

# How to summarise a workshop

> Source: https://thinkdrop.io/guides/how-to-summarise-a-workshop · Last reviewed 2026-08-26 · The thinkdrop facilitation team

A workshop summary should open with the decisions and owners, not with the agenda. Send it within 24 hours, keep it under a page, and include the ideas that were rejected and why — that section is what stops the same debate reopening in three weeks. The board itself is the appendix, not the summary.

## Key facts

- **Send within:** 24 hours
- **Length:** Under one page
- **Opens with:** Decisions and owners
- **Always include:** What was rejected and why
- **Audience:** Written for the person who missed it

## Step by step

1. **Lead with the decisions** — First three lines: what was decided, who owns it, by when. Most workshop write-ups open with the agenda and the attendee list, which is the part nobody needs. If a reader stops after the first paragraph, they should still know what changed.
2. **Name owners, not teams** — "Marketing will look at it" is an action nobody does. A person's name and a date is the entire difference between a workshop that changes something and a workshop that was pleasant.
3. **Record what was rejected and why** — The most valuable and most commonly omitted section. Without it, the same suggestion returns next month and the group re-runs the discussion from scratch. Two lines per rejected option is enough.
4. **Keep the themes, drop the raw cards** — Summarise the themes that emerged and link to the board for the full set. Pasting 60 raw cards into a document guarantees the document is not read.
5. **Write it for the person who was not there** — The people who attended already know what happened. The summary exists for the person on holiday, the stakeholder who could not join, and the reader in three months trying to understand why the decision was taken. Write for them and it will work for everyone.
6. **Send it within 24 hours** — The summary's usefulness decays fast: after a week the actions have already been overtaken and nobody will read it. A rough summary today beats a polished one on Friday.

## A structure that gets read

Decisions and owners. Themes, three to six of them, one line each. What was rejected and why. Open questions with a named person responsible for closing each. A link to the board. That is the whole document, and it fits on a page.

- Decisions and owners — the top of the page, always.
- Themes — one line each, not a transcript.
- Rejected options — two lines each, with the reason.
- Open questions — each with a name attached.
- Link to the board for anyone who wants the detail.

## Using AI for the first draft

AI is good at turning a board of cards into grouped themes and a readable draft in seconds, which removes the main reason summaries never get sent. The rule is that it drafts and a human confirms: a model will happily write a confident sentence about a conclusion the group never reached, and the facilitator is the only person who can catch it. Never send an unread AI summary.

- AI drafts the themes; the facilitator confirms the decisions.
- Check every named owner and date by hand.
- Delete any conclusion you cannot point to on the board.

## Where the summary should live

Wherever your team already looks. A summary in a tool nobody opens is the same as no summary. Paste it into the channel where the work happens and keep the canonical copy with the board so the ideas and the conclusions stay together.

## FAQ

**How long should a workshop summary be?**

Under a page. If it is longer, it is minutes rather than a summary, and minutes are read by nobody except the person who wrote them.

**Should the summary include everyone's name?**

Attendees, yes, briefly. Attribution of individual ideas, only where it credits someone or clarifies ownership of an action.

**Can AI write the whole summary?**

It can write the draft. A human must confirm the decisions, owners and dates before it is sent, because a plausible invented conclusion in a circulated summary is worse than no summary at all.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/how-to-summarise-a-workshop.

---

# Dot voting: how to pick ideas without a debate

> Source: https://thinkdrop.io/guides/dot-voting-how-to · Last reviewed 2026-08-26 · The thinkdrop facilitation team

Dot voting gives each participant a fixed number of votes to spend across the ideas on a board, with the highest-scoring ideas taken forward. Give roughly one vote per five ideas, vote in silence and simultaneously, and treat the result as a strong signal for the decision-maker rather than as the decision itself.

## Key facts

- **Votes per person:** One per five ideas, 3–5 typical
- **Voting time:** 2–3 minutes
- **Stacking:** Allow up to two on one idea
- **Order:** Silent and simultaneous
- **Take forward:** Top three, no more

## Step by step

1. **Group before you vote** — Vote on themes, not on raw cards. Otherwise a topic that happened to be written up five different ways beats a topic somebody stated once, and you have measured card volume rather than importance.
2. **Set the criterion out loud** — "Vote for what we should do first" and "vote for the best idea" produce different boards. Say which one you mean before dots are spent, because half the room will otherwise silently assume the other.
3. **Give one vote per five ideas** — Twenty ideas, four votes. Too many votes and everything scores; too few and the result is noise. Three to five votes per person is the usual landing spot.
4. **Vote in silence, at the same time** — Sequential or visible voting is just anchoring with extra steps — the first dots placed pull the rest. Hide results until everyone has finished, then reveal.
5. **Allow limited stacking** — Let people put two dots on one idea but not all of them. Stacking lets someone express conviction; unlimited stacking turns the exercise into a single-choice poll.
6. **Discuss the surprises, then decide** — Spend the remaining time on the two ideas that scored unexpectedly high or low. That conversation is the actual value of the vote; the ranking was just the way of finding it.

## What dot voting is good at

It converts a large set of options into a short list in a few minutes without a discussion in which the most senior person speaks first. It also makes disagreement visible: a scattered board tells you the group has no shared priority, which is far more useful to know before a decision than after one.

## What it is bad at

It is not a decision-making method and it is not a democracy. It ignores effort, cost, dependencies and the fact that one person in the room may have information the others do not. Popular is not the same as correct, and the person accountable for the outcome still owns the call — the vote informs them.

- It ignores cost and effort; add a quick impact/effort pass after.
- It rewards familiar ideas over unfamiliar ones.
- It can hide a strong minority objection behind an average score.

## Handling ties and near-ties

A two-point gap between the top ideas is not a result. Either take both forward, or hold a 60-second case for each and re-vote with two dots per person. Do not break a tie by asking who feels strongly, because that measures confidence rather than merit.

## FAQ

**How many dots should each person get?**

About one per five ideas, usually three to five. Fewer than three cannot express nuance; more than six makes everything score.

**Should votes be anonymous?**

Yes during voting, so nobody follows the manager's dots. Once the result is up, the discussion about why should be open.

**Should the facilitator vote?**

Preferably not. If you are running the session you already shape it enough, and abstaining makes the result easier to trust.

**Is the highest-voted idea automatically the decision?**

No. It is the strongest signal in the room, and the person accountable for the outcome should say explicitly whether they are following it and why.

---

Written and maintained by The thinkdrop facilitation team at thinkdrop.io, a real-time idea board for brainstorms, retrospectives and workshops. Free to quote with a link to https://thinkdrop.io/guides/dot-voting-how-to.