HomeFrameworksCreative Ideation › Reverse Brainstorming
// framework

Reverse Brainstorming

Various

Reverse Brainstorming inverts the problem — asking how to cause the problem rather than solve it — then flips each answer into a preventive action, surfacing specific fixes that positive framing consistently misses.

// description

Reverse brainstorming inverts the problem statement. Instead of asking "How do we solve X?" the group asks "How could we cause X?" or "How could we make this as bad as possible?" Participants find it much easier and more entertaining to generate ways to worsen a situation, and the energy in the room is typically higher than in a conventional brainstorming session. Once the list of ways to cause the problem is complete, each item is flipped into a preventive or corrective action.

// history

The technique has no single credited inventor and appears in various forms across creativity literature. It is sometimes called "negative brainstorming" or "reverse assumption." Its psychological basis is well established: people are generally better at identifying threats and failures than at envisioning success, a tendency reverse brainstorming exploits productively.

// example

An Etsy seller with a customer retention problem asks "How could we guarantee every customer never returns?" Ideas pour out: send damaged products, ignore complaints for two weeks, use ugly packaging, charge hidden fees, spam customers daily. Flipping each one produces actionable improvements: audit quality control, implement 24-hour response policy, redesign packaging, review pricing transparency, reduce email frequency to weekly. The reverse framing surfaces specific problems the seller had been vaguely aware of but had never articulated directly.

// katharyne's take

I love this for product launch planning. Instead of "how do we make this launch successful?" I ask "how do we guarantee this launch fails?" The answers are almost always more honest and specific than the positive version. Nobody says "just try harder" when the question is negative — they say "launch on Christmas Eve," "don't tell your email list until the day of," "price it too high with no justification." Each failure cause becomes an item on your launch checklist. This is essentially how I build my launch playbooks.

// creative uses
// quick actions
// prompt ideas
Run a reverse brainstorm on my [Etsy shop / KDP book launch / digital product business]. Ask: "How would I guarantee [the problem I want to solve — e.g. no one buys, my email list never grows, my course has terrible completion rates]?" Generate 12 specific ways to cause that failure — be detailed and honest, not generic. Then flip each one into a preventive action and tell me which three fixes would have the highest impact if I implemented them this week.
I want to improve [my Etsy conversion rate / my email open rate / my KDP review rate]. Instead of asking how to improve it, ask: "How would I guarantee it stays terrible forever?" Generate 10 specific failure causes for [metric] in my context — [briefly describe your shop/product/audience]. Then reverse each one into a concrete improvement. Format the output as two columns: what causes the problem, what fixes it.
Use reverse brainstorming to help me design a better [course / community / digital product]. My current [course/product] is: [describe it briefly]. Ask: "How would I design this so students never finish it / buyers feel disappointed / members disengage within a month?" Give me 10 specific design failures, then flip each one into a design principle I should follow. Prioritise the five flips that would make the biggest difference to the actual user experience.
See also: Provocation (Po) · Assumption Reversal · Brainstorming
← Lotus Blossom Technique Starbursting →