10 Team Brainstorming Techniques That Actually Work

Most brainstorming sessions fail in the first ten minutes. Someone senior speaks first, the room quietly converges on their idea, and the next forty-five minutes are spent rationalising a decision that was already made. We see this pattern constantly in the discovery workshops that kick off our Odoo implementations: a room full of capable people, a whiteboard, and almost no new thinking. The problem is rarely the people. It is the technique, or the absence of one.

Good facilitation is the difference between a meeting that produces a decision and one that produces a follow-up meeting. Below are ten techniques we actually use when we run requirements workshops, process-mapping sessions, and go-live retrospectives with clients across Manufacturing, Real Estate, E-commerce, and Distribution. Each one solves a specific failure mode, so the real skill is matching the technique to the moment.

1. Brainwriting (Silent Idea Generation)

Instead of shouting ideas into the room, everyone writes silently for five to seven minutes, then passes their sheet to the next person to build on. It neutralises the loudest-voice problem and the anchoring effect of whoever speaks first. We open almost every requirements workshop this way because the warehouse supervisor who never interrupts the regional manager often holds the detail that breaks an ERP rollout. Use it when seniority gaps or strong personalities are likely to flatten the discussion.

2. The Crazy Eights

Fold a sheet into eight panels and force eight rough ideas in eight minutes, one per minute. The brutal time limit is the point: it kills perfectionism and pushes people past their first, most obvious answer to the more interesting fourth and fifth ones. Reach for Crazy Eights when a team is fixating on a single solution too early, such as insisting there is only one way to structure an approval workflow. The volume reveals options nobody had considered.

3. Mind Mapping

Start with the core problem in the centre and branch outward into causes, sub-problems, and connections. Mind mapping is strongest when a topic is sprawling and nobody can see how the pieces relate. When a distribution client tells us their order-to-cash process is broken, a map quickly exposes whether the real issue lives in sales, inventory, or invoicing. Use it early, during diagnosis, before anyone proposes solutions.

4. SCAMPER

SCAMPER is a checklist of prompts applied to an existing thing: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse. It is built for improving what already exists rather than inventing from scratch. We lean on it when a client wants to optimise a current process instead of replacing it. Asking what we could eliminate from an invoice-approval chain often surfaces three redundant sign-offs that were quietly added years ago and never removed.

5. Round-Robin

Go around the group one person at a time, each contributing a single idea, no skipping and no commentary until everyone has spoken. Round-robin guarantees participation, which matters in mixed-seniority or cross-functional rooms where juniors default to silence. It is also a cultural fit for many of our UAE clients, where a structured turn gives quieter team members explicit permission to contribute. Use it when you suspect the same two or three voices would otherwise dominate.

6. Reverse Brainstorming

Instead of asking how to solve a problem, ask how to cause it. How would we guarantee a delayed go-live? How would we ensure staff never adopt the new system? Inverting the question is liberating because criticising is easier than creating, and every failure mode you invent maps directly to a safeguard. We run a reverse session before every major deployment, and the answers reliably become our pre-go-live risk checklist.

7. The Six Thinking Hats

Edward de Bono's method has the whole group think in one mode at a time: facts (white), feelings (red), caution (black), optimism (yellow), creativity (green), and process (blue). The power is in synchronising the room so the optimist is not fighting the sceptic in the same breath. It shines for emotionally charged decisions, like whether to customise Odoo heavily or adapt the business to standard workflows, where unmanaged debate turns into a standoff. Give the cautious analysis its own dedicated slot and it stops poisoning every other idea.

8. Affinity Mapping

After a burst of idea generation you are left with fifty sticky notes and no structure. Affinity mapping is the cleanup: cluster related notes, name each cluster, and the themes emerge on their own. This is a convergence technique, not a generation one, so it belongs in the second half of a session. It is how we turn a chaotic wall of pain points into the three or four workstreams that actually shape a project plan.

9. Dot Voting

Give each person a fixed number of dots and let them vote on the ideas worth pursuing. Dot voting solves the problem of generating thirty ideas and having no fair way to choose. Because it is anonymous and fast, it avoids the politics of arguing each option to death. We use it to prioritise feature requests in phased rollouts: when a client wants everything in phase one, dot voting forces the honest conversation about what actually goes live in the first 90 days and what waits.

10. The Question Burst

Spend four minutes generating only questions about the problem, with no answers allowed. Teams that jump straight to solutions often solve the wrong problem precisely. Forcing a wave of questions reframes the challenge and surfaces hidden assumptions. When a client says they need a custom report, a question burst, asking who reads it, how often, and what decision it drives, frequently reveals that a standard Odoo dashboard would have done the job. Use it whenever a team has converged on a solution suspiciously fast.

Choosing the Right Technique

The techniques fall into two families, and most failed sessions confuse them. Divergent techniques widen the field, while convergent ones narrow it toward a decision. A quick rule of thumb:

• Generate options: Brainwriting, Crazy Eights, Mind Mapping, SCAMPER, Reverse Brainstorming, Question Burst.
• Ensure participation: Round-Robin, Brainwriting.
• Organise and decide: Affinity Mapping, Dot Voting, Six Thinking Hats.

Run them in that order. A session that diverges without ever converging produces energy and no decision; one that converges without diverging produces a fast, narrow, and usually wrong answer. The facilitator's job is to call the switch explicitly: we have enough ideas, now we choose. Three more habits matter regardless of technique. Set a strict time box for each phase, because constraints drive creativity far better than open-ended discussion. Capture everything visibly on a wall or shared screen so ideas compound instead of evaporating. And always assign an owner and a date to each decision before the room empties, or the whole exercise quietly dissolves into nothing by Monday.

From Brainstorm to Built System

A good session ends with prioritised, owned decisions, but a list of decisions is not yet a working business process. At Oakland, the UAE's number one Odoo Gold Partner and part of the ARMOR Group, structured facilitation is how we begin every engagement. We use these same techniques in our discovery workshops to map your real processes, agree priorities, and design an Odoo system that fits how your team actually works, from VAT-compliant invoicing to WPS-ready payroll. With 120-plus implementations behind us and a 90-day go-live model, we turn the best ideas from the whiteboard into software your team uses every day. If your next big decision deserves more than another circular meeting, talk to our team about a discovery workshop.