Reverse Brainstorming
Reverse Brainstorming: Invert your problem β "How could we make this worse?" β then flip the answers to generate solutions. It's easier to think of ways to cause a problem than to solve it, and inverting those causes often surfaces novel solutions that direct brainstorming misses. Charlie Munger's inversion principle, applied to idea generation.
What Is Reverse Brainstorming?β
Reverse Brainstorming builds on a key psychological insight: it is cognitively easier to think of how to cause a problem than how to solve it. When asked "how do we improve customer retention?", most people draw on familiar solutions. When asked "how do we make customers leave as fast as possible?", the mind generates vivid, specific, often darkly funny answers that, when inverted, produce surprisingly useful solutions.
The technique is a practical application of the inversion principle β the mental model that Charlie Munger attributed to algebraist Carl Gustav Jacob Jacobi: "Invert, always invert." Where direct thinking produces polished but conventional solutions, inverted thinking forces you into different cognitive territory and surfaces systemic problems that forward-thinking misses.
Reverse brainstorming also reduces the social pressure of creative sessions. "How do we make the product terrible?" feels playful rather than high-stakes, which lowers inhibition and generates more honest responses. It's particularly effective for teams that have become defensive about existing approaches, because the exercise invites critique by framing it as creative imagination rather than evaluation.
How It Worksβ
Step 1: Define the real problem clearly
β "We want to improve employee engagement"
Step 2: Invert the problem
β "How would we destroy employee engagement?"
β "What would guarantee employees hate working here?"
β "How do we make this as bad as possible?"
Step 3: Brainstorm answers to the inverted question freely
β No filtering; capture everything
β The worse the better at this stage
Step 4: Flip each reversed idea into its opposite
β "Ignore feedback completely" β "Create structured feedback loops"
β "Never celebrate wins" β "Celebrate wins publicly and specifically"
β "Give no autonomy" β "Define clear areas of ownership"
Step 5: Evaluate and select
β Which flipped solutions are actionable and novel?
β Which expose problems you hadn't explicitly identified?
Three Real-World Examplesβ
Customer Experience at an Airlineβ
An airline's CX team struggling to improve NPS tried reverse brainstorming: "How do we make the flying experience as miserable as possible?"
Answers included: make boarding chaotic and unclear, give passengers no information when delays happen, make seats cramped and uncomfortable, charge for everything without advance warning, lose luggage without any follow-up.
Inverted: create clear, zone-based boarding with regular announcements; send proactive delay notifications with estimated resolution times; invest in seat ergonomics; price transparency with all fees visible at booking; real-time luggage tracking with automatic compensation. The exercise surfaced five specific, addressable pain points the team had known about but hadn't framed as primary priorities.
Product Onboarding Redesignβ
A SaaS company reversed their onboarding problem: "How do we guarantee new users give up in the first 10 minutes?"
Results: show the most complex feature first; require users to read long documentation before touching the product; ask for credit card before they see any value; use technical jargon in all prompts; give no indication of progress.
Inverted: start with the simplest high-value action; make the product interactive before any documentation; delay payment until the user has experienced a key moment of value; write all copy in plain language; show a progress indicator throughout onboarding. The team's conversion rate from trial to paid improved significantly after implementing the inverted recommendations.
Supply Chain Resilience Planningβ
A logistics director asked their team: "How do we maximise supply chain disruption risk?"
Answers: single-source every key component; carry minimal inventory; have no supplier backup agreements; make contracts with no force majeure clauses; keep no visibility into supplier sub-tiers.
Inverted: dual-source all critical components; maintain safety stock for 60-day disruption buffer; pre-qualify backup suppliers; update contracts with resilience clauses; implement sub-tier supplier mapping. This produced the company's supply chain resilience roadmap.
When to Use Itβ
β Reverse Brainstorming excels when:
- Direct brainstorming is producing obvious, uninspired answers
- The team is defensive about the current approach
- You want to surface problems you haven't consciously identified
- The team needs creative activation before a conventional session
β Less effective when:
- The problem is highly technical and the inversion doesn't map cleanly
- The team is too literal to make the leap from reversed idea to solution
- Time is very short and facilitation overhead isn't worthwhile
| Pairs well with | Why |
|---|---|
| Inversion | Reverse brainstorming is inversion applied to idea generation |
| Six Thinking Hats | Black Hat thinking is a focused version of reverse brainstorming |
| Pre-mortem | Pre-mortem is reverse brainstorming applied to project failure |
| SCAMPER | SCAMPER and reverse brainstorming both bypass conventional idea generation |
Common Misuses and Limitationsβ
Stopping at the inverted list without flipping. Generating a great list of "how to make it worse" and not systematically converting each item into a positive solution misses most of the value. Every item on the reversed list should be explicitly flipped.
Flipping too literally. "Never listen to customers" doesn't flip to "always listen to customers" in a useful way β that's obvious. The deeper flip is: "What listening mechanism would this make us design?" Push past the obvious opposite.
Using it only for creative problems. Reverse brainstorming is equally valuable for risk analysis, strategy stress-testing, and UX research. "How do we make this interface confusing?" produces UX insights faster than most usability testing.
Skipping the evaluation step. Not all flipped ideas are good ideas. The evaluation step is where judgment returns β which inverted insights are actually novel and actionable?
Related Modelsβ
| Model | Relationship |
|---|---|
| Inversion | The mental model that underlies reverse brainstorming |
| Pre-mortem | Pre-mortem = reverse brainstorming for project risk |
| Six Thinking Hats | Black Hat = structured reverse brainstorming |
| Constraint Relaxation | Both techniques move thinking outside conventional frames |
Frequently Asked Questionsβ
How is reverse brainstorming different from a pre-mortem?
A pre-mortem is a specific, focused application: imagine the project has failed; what went wrong? It's reverse brainstorming applied to one specific domain (project failure) with a time-travel framing (future failure already happened). Reverse brainstorming is more general β it can be applied to any problem, not just project risk. Also, pre-mortems typically generate plausible failure scenarios; reverse brainstorming aims for any way to make things worse, including absurd or extreme ones, which sometimes surface the most useful insights when inverted.
Does reverse brainstorming work for complex technical problems?
Yes, but the inversion must be thought through carefully. For "how do we improve database query performance?", the reversal "how do we make queries as slow as possible?" generates: full table scans on every query, no indexing, N+1 queries everywhere, lock entire tables during reads, fetch 10Γ more data than needed. Inverted: proper indexing strategy, query optimisation, eager loading, row-level locking, projection queries. The reversal works; it requires a facilitator who can translate between the problem domain and the inversion.
How long should a reverse brainstorming session take?
For most problems: 20β45 minutes total. Roughly: 5 minutes framing and inversion; 10β15 minutes brainstorming the reversed question (the fun, generative part); 10β15 minutes systematically flipping each item and noting which flipped ideas are novel or actionable; 5 minutes selecting priorities. The session is faster than conventional brainstorming because the inversion activates different thinking and breaks through typical blocks quickly.
Further Readingβ
- Osborn, A. (1953). Applied Imagination β the brainstorming framework within which reversal techniques developed
- Michalko, M. (2006). Thinkertoys β comprehensive creative thinking toolkit including reversal techniques
- Munger, C. (2005). Poor Charlie's Almanack β inversion as a general mental model
Apply with AIβ
π Run a reverse brainstorming session with MindMax β
This page is part of the MindMax Mental Models Knowledge Base.