When Your Team Hits a Wall, Flip the Problem
We’ve all been there. The planning call where everyone agrees there’s a problem, past attempts have failed, and the path forward feels murky at best. Your team is stuck, the silence is getting uncomfortable, and someone eventually mutters, “So... what do we do?”
One technique that I like to do: Invert the problem entirely.
What Is Inversion?
Inversion is simple. Instead of asking “How do we solve this?” you ask “How could we guarantee this gets worse?”
Rather than wrestling with how to prevent a failure, you map out every possible way to cause it. Once you see all the ways to create the problem, you’ve essentially built your prevention checklist in reverse.
The classic example: You want to improve your app’s sign-up completion rate. Traditional thinking asks, “How do we get more people to finish the sign-up?” Inversion asks, “What would make people abandon sign-up halfway through?”
Suddenly, ideas flow: Too many form fields. Confusing error messages. Requiring password complexity that feels excessive. No clear progress indicator. Each answer becomes something concrete to investigate and address.
Why Inversion Works
It breaks analysis paralysis
When you’re stuck trying to solve a complex problem, your brain can hit a wall. Inversion sidesteps that wall entirely. It’s easier to imagine ways to break something than to envision the perfect solution and that lower barrier gets your team talking and thinking again.
It surfaces blind spots
Traditional brainstorming tends to reinforce what you already believe might work. Inversion forces you to think from the opposite direction, revealing assumptions you didn’t know you were making and risks you hadn’t considered.
It creates actionable strategies
“Improve user engagement” is vague. But “Stop doing the five things that would kill user engagement” is concrete. Inversion naturally produces a prioritized list of what not to do, which often clarifies what you should do.
A Real Example
I recently worked with a team optimizing a user flow. They had two paths leading to the same information, but wanted users to take Path A because it simplified downstream operations.
The team spent weeks asking: “How do we get users to choose Path A?”
At a certain point we did the exercise of flipping it: “How would we guarantee users pick Path B instead?”
Within minutes, the answers poured out:
Make Path A harder to find
Add extra steps to Path A
Use confusing labels on the Path A button
Hide the benefits of Path A
Make Path B load faster
Suddenly, we weren’t speculating anymore. We realized Path A was harder to find in the current design. The button label was ambiguous. We hadn’t communicated the benefits clearly.
Once we addressed these friction points, the things that would actively drive users away, adoption of Path A improved significantly.
How to Use Inversion
Next time your team is stuck, try this:
Spend 10 minutes mapping out how you could cause the exact result you don’t want. Be specific and be creative. Get your team to contribute the most absurd ideas they can think of.
Then review your list. Some items will be obviously irrelevant. But others will be your action items. The real risks you need to mitigate, the hidden friction you need to eliminate.
The clearest path forward often starts by walking backwards.