Reverse brainstorming: solve problems backwards

Reverse brainstorming is a technique for solving stuck problems by inverting the question: instead of asking how do we achieve X, ask how could we guarantee the opposite of X. The list of "ways to fail" you produce tends to surface obstacles, blind spots, and assumed constraints that a straightforward "how to succeed" brainstorm would have missed.

The technique is rooted in the older Charlie Munger maxim of inversion: "Invert, always invert. Many hard problems are best solved when they are addressed backward." Munger borrowed the discipline from the 19th-century mathematician Carl Gustav Jacob Jacobi, who famously said that for hard problems, man muss immer umkehren — one must always invert.

Why backwards thinking works

Forward brainstorming ("how do we improve retention?") activates everyone's existing assumptions about what's possible. The group converges on familiar ideas because the familiar shapes the search space.

Backwards brainstorming ("how could we destroy retention?") suspends the familiar. The mind has fewer rehearsed answers to the inverted question, so it generates fresh ones. And inverted answers point at causes the forward question would have left invisible — the small daily frictions, the silently-accumulating dissatisfactions, the things we already know but haven't been willing to name.

The output of a reverse brainstorm is rarely "do the opposite of these failure ideas". It's "the failure ideas reveal what was actually broken that we kept not seeing".

When to use it

• The team has been stuck on the same problem for weeks and is recycling the same proposed solutions
• A project has clearly visible symptoms but unclear root causes (revenue is flat, users are churning, morale is dropping — but everyone has a different theory)
• You're about to double down on a strategy and want one last filter to catch what could undermine it
• A pre-launch sanity check when a premortem feels too heavy

Skip reverse brainstorming for problems with clear root causes (where 5 Whys works), or for routine optimization (where the answer is in the data).

How to actually run one in 45 minutes

1. State the goal clearly (5 min). "Increase signup conversion from 8% to 12% by end of Q3." Get the team to read the goal aloud, then write it on the wall in plain view.
2. Invert the goal (2 min). "How could we guarantee signup conversion drops to 4%?" or "What would absolutely kill conversion?" Write the inverted goal in bigger letters than the original. Resist softening — the inversion only works if it's bracing.
3. Silent generation: 10 minutes of individual writing. Each person lists every way they can think of to cause the failure. No discussion, no judging, no sorting. Quantity over quality.
4. Round-robin read-out (15 min). Each person reads one item from their list. Capture each on a sticky note. Continue until exhausted. Encourage absurd answers — they often unblock obvious ones the group was too polite to say.
5. Cluster and translate (10 min). Group the failure-causes by underlying theme. Each cluster becomes a candidate problem area for the real (forward) work.
6. Decide what to do (5 min). For the top 2–3 clusters, identify a concrete action that addresses the cause. The action need not be the literal inverse of the failure cause — usually it's a different intervention informed by what the failure cause revealed.

What makes a reverse brainstorm actually work

Permission to be uncomfortable. The good answers to "how could we destroy this" often name things people have noticed but kept polite about. The facilitator's job is to make it socially safe to say them.

Silent writing first. If you go straight to open discussion, the highest-status person in the room defines the search space. Silent writing protects the divergent phase from premature convergence.

Don't translate too early. It's tempting to immediately map each "failure cause" to its "fix". Resist. Let the failure causes accumulate; the patterns only become visible at scale.

Re-read the original goal at the end. After 30 minutes of imagining failure, the team can lose sight of what success was supposed to be. Reading the original goal back grounds the closing decisions.

A worked example

A product team's goal: "Make the new onboarding flow drive 60% activation within 7 days."

Inverted: "How could we make sure activation stays below 20%?"

The first 5 minutes of silent generation surfaced answers like:

• "Don't let the user do anything useful in their first session"
• "Send 4 transactional emails on day one"
• "Make the first action require a credit card"
• "Hide the value proposition behind a 6-step setup wizard"

By minute 20 the answers got sharper:

• "Show them what other people built before they've built anything themselves"
• "Make the empty state feel like work, not progress"
• "Force them to invite teammates before they've experienced value"

The team's actual onboarding had three of these patterns. The forward question ("how do we improve activation?") had been live for two months and produced incremental ideas. The inverted question, in 30 minutes, produced a redesign brief.

Related ideas

Reverse brainstorming is one application of the broader principle of inversion — solving by characterizing what you don't want and working backwards. Related forms:

• Premortem — the project-level version: assume the project failed and ask what caused it
• 5 Whys — narrower: walk one observed problem back to its root
• First Principles — orthogonal: instead of inverting, decompose to atoms and rebuild
• SWOT — the Threats quadrant is a mini-inversion baked into a broader framework

The common thread: when forward thinking is stuck, ask the inverse. Failure modes are often easier to see clearly than success paths.

Open the Reverse Brainstorming entry → for the worksheet template.