Reverse Brainstorming Technique With Examples

Published October 15, 2026 · Updated October 15, 2026 · 8 min read · by the Sakura5 team

The reverse brainstorming technique flips your question from “How do we solve this?” to “How could we cause this, or make it worse?”, collects every answer you can think of, and then reverses each one into a possible fix — for example, “How could we make sure no customer ever renews?” quickly surfaces “hide the renewal date” and “never ask for feedback”, which flip into a renewal reminder and a check-in email. It works because people are far better at spotting ways things go wrong than at inventing ways they go right.

That asymmetry is the whole trick. Ask a team for ideas to improve onboarding and the room goes quiet. Ask them how to make onboarding miserable and the answers arrive faster than anyone can write them down, because everyone has lived through a bad version. Reverse brainstorming turns that easy, slightly gleeful criticism into raw material.

Below: why normal brainstorming stalls, a five-step workflow, two short reverse brainstorming examples, one full worked example with real numbers, the traps to avoid, and a short FAQ.

Why normal brainstorming stalls

A standard brainstorm asks for positive ideas, and positive ideas come with a hidden cost: they feel like commitments. Suggest “we should rebuild the signup flow” and you’ve just volunteered for a project. So people suggest safe, small things, or nothing at all.

The second problem is anchoring. The first reasonable idea becomes the template, and the next ten are variations of it. You end up with a long list that is really one idea wearing different clothes.

Reverse brainstorming sidesteps both. Saying how to sabotage something commits you to nothing, so people say more. And because failure has many more shapes than success, the answers spread across the whole problem instead of clustering around the first suggestion. You also get a free diagnosis: if a “how to make it worse” idea is something you already do, you’ve found a real problem, not just a hypothetical one.

The reverse brainstorming technique, step by step

Set aside 30 to 45 minutes. It works alone or in a group of up to about eight; beyond that, split into smaller groups and combine the results.

1. State the real problem in one sentence

Be specific. “Improve the website” is too vague to reverse. “Get more visitors to finish the free trial signup” is not. If you can’t say what success looks like, the reversed version will be just as fuzzy.

2. Write the reversed question

Turn the goal inside out. There are two common forms: “How could we cause this problem?” and “How could we make this outcome as bad as possible?” Pick one and write it down where everyone can see it. “How do we make sure nobody finishes the trial signup?” is a good reversed question: concrete, a little absurd, easy to answer.

3. Generate sabotage ideas without judging

Give yourself ten to fifteen minutes and write down every way to cause the problem, including silly ones. The silly ones are often exaggerations of something real. “Make the form 40 fields long” sounds like a joke until you count the fields on your actual form. Don’t argue, don’t fix anything yet, and don’t stop at the obvious answers.

4. Flip each sabotage idea into a solution

Go through the list one item at a time and ask: what is the opposite of this, and what would it look like in practice? One bad idea can produce several fixes. “Ask for a credit card before showing anything” flips into “show the product first”, “delay the card request until day three” or “offer a no-card trial”. Write all of them.

5. Check which sabotage you’re already doing

This is the step most guides skip, and it’s the most valuable one. Mark every sabotage idea that describes something you currently do, even partly. Those marked items are your priority list: real problems, already named, with fixes sitting right next to them. Pick the two or three flipped solutions with the best effort-to-impact ratio and give each a next step and an owner.

A mind map suits this better than a list because the structure matches the method. Put the reversed question in the center, the sabotage ideas as branches, and their flipped solutions as children of each branch. In Mindmap AI you can generate a starting map from the reversed question in one line, and with MindMap Pro tap any sabotage branch to expand it into more ideas with AI. Treat what it suggests as extra prompts, not answers — the checking in step 5 still has to come from you.

Reverse brainstorming examples

Two short examples show how the flip works in different settings.

A school club with falling attendance. Reversed question: “How do we make sure nobody comes back after their first meeting?” Sabotage ideas: never learn new members’ names, spend the first 20 minutes on admin, change the meeting room without telling anyone. Flipped: a name round at the start, admin moved to the last five minutes, one fixed room with a reminder message the day before.

A personal habit. Reversed question: “How could I guarantee I never go for a morning run?” Sabotage ideas: keep the shoes in the back of a cupboard, check my phone as soon as I wake up, plan a route I find boring. Flipped: shoes by the bed, phone charging in another room, three short routes to rotate. This is reverse brainstorming at its smallest, and it works well for solo problems — our guide to brainstorming alone effectively uses the same move as one of its prompts.

A worked example: the bakery losing weekday customers

Here’s a fuller scenario. Priya runs a neighborhood bakery. Saturday is busy, but weekday sales have slipped from roughly 120 customers a day to about 85 over three months. She has one evening and two of her staff to work on it.

The problem: “Bring weekday customers back toward 120 a day.”

The reversed question: “How could we make sure nobody stops in on a weekday?”

Fifteen minutes of sabotage (22 ideas, a sample):

• Run out of the popular items by 10am.
• Open after people have already gone to work.
• Make the queue slow, with only one person on the till.
• Never change the menu, so there’s nothing new to come back for.
• Only take cash.
• Hide the opening hours, or list the wrong ones online.
• Give regulars no reason to feel recognized.

Checking which sabotage is real (step 5): the team marks four as things they already do. The bakery opens at 8am, but the nearby office workers pass by between 7:15 and 7:45. The almond croissants sell out most days before 10am. The online listing still shows the old Monday closing time from last winter. And there’s one person on the till until 9am.

Flipped solutions for the four real ones:

• Open at 7am on weekdays for a four-week trial.
• Bake a second, smaller batch of almond croissants for the late morning.
• Correct the online hours tonight — five minutes of work.
• Move the second staff member’s start time to 7am so the till is covered during the rush.

The first instinct had been a weekday discount. The reverse brainstorm showed the bakery was effectively closed during the window its weekday customers wanted, and was telling some of them it was closed on Mondays. The discount would have cost margin and fixed none of it. Priya sets a check date four weeks out and keeps the unused sabotage ideas on the map, so if the numbers don’t move, the next round starts from 18 candidates instead of a blank page.

Common traps and how to avoid them

Stopping at the sabotage list. A list of ways to fail is entertaining and useless on its own. The method only pays off in steps 4 and 5. Budget at least as much time for flipping and checking as for generating.

Flipping too literally. “The queue is slow” flips to “make the queue fast”, which isn’t a solution, just a wish. Push each flip until it’s an action someone could take tomorrow: a second till, a pre-order option, a shorter menu during the rush.

Using it for everything. Reverse brainstorming is strongest for improving something that already exists — a process, a product, a habit. For blank-page creative work, like naming a product or finding a story idea, other methods tend to do better; our roundup of creative thinking techniques covers the alternatives. If you want background on the wider family of methods reverse brainstorming belongs to, the overview of brainstorming and its variants is a reasonable starting point.

Keep the map once you’re done. In Mindmap AI, maps sync through your own iCloud across iPhone, iPad and Mac, and the outline view turns the flipped-solutions branch into a clean action list you can paste into a message or a task app.

FAQ

What is reverse brainstorming in simple terms?

Reverse brainstorming means asking how to cause a problem instead of how to solve it. You list every way to make things worse, then turn each one around into a possible fix. It helps because criticizing is easier than inventing, so people produce more ideas, and some of the “bad” ideas turn out to describe what is already happening.

When should you use the reverse brainstorming technique?

Use it when you’re trying to improve something that already exists, such as a process, a service, a product or a habit, and normal brainstorming keeps producing the same few safe ideas. It’s also useful when a group is reluctant to speak up, since suggesting ways to fail feels less risky than proposing a plan.

What is the difference between brainstorming and reverse brainstorming?

Standard brainstorming asks for solutions directly. Reverse brainstorming asks for causes of failure first and converts them into solutions afterwards. The extra step takes a little longer, but it tends to reveal problems you’re already creating without noticing, and it spreads ideas across the whole problem instead of around the first suggestion.

Can you do reverse brainstorming alone?

Yes. Write the reversed question at the center of a page or mind map, give yourself ten minutes to list ways to sabotage the goal, then flip each one into an action. Working alone, the checking step matters even more: be honest about which sabotage ideas describe your current habits, because those are the fixes worth doing first.

← All articles