The Wrong Problem, Solved Brilliantly
A team at a Learn2 client spent three months building an automated customer onboarding system. Beautiful solution. Elegant engineering. One problem: customer churn didn't change.
They had solved the wrong problem brilliantly. The onboarding wasn't the issue. The handoff from sales to success was. Different problem entirely.
Three months. Significant budget. Zero impact. Not because the team lacked talent or effort. Because nobody reframed the problem before solving it.
Why Teams Solve the Wrong Problem
In the Save the Titanic experience, participants face what seems like a straightforward problem: the ship is sinking. Fix the ship.
Except that's not the real problem. The real problem is: how do you coordinate a complex operation with limited information, competing priorities, and a ticking clock? The ship is the symptom. The coordination challenge is the root cause.
Teams that fixate on the ship sink it. Teams that reframe the problem around coordination save it.
This is the Problem = Solution principle. The way you define the problem determines the solutions you can see. Define it wrong, and no amount of effort produces the right answer. Teams that solve symptoms instead of root causes are almost always working with the wrong problem statement.
The Reframing Exercise
This takes 15 minutes and changes the trajectory of projects that have been stuck for months.
Step 1: Write the problem as you currently see it. Put it on a whiteboard. "Customer churn is too high." "Project delivery is always late." "Employee engagement scores are dropping."
Step 2: Ask "for whom?" five different ways. Customer churn is too high — for whom? For the company? For the customer? For the sales team who sold the wrong fit? For the success team who can't support the volume? Each "for whom" reveals a different problem behind the same symptom.
Step 3: Flip the problem into an opportunity. Instead of "customer churn is too high," try "how could we make customers so successful in their first 30 days that leaving never occurs to them?" The flip changes the energy from defensive to creative. It opens solution spaces that the original framing closed.
Step 4: Apply the [5 Whys](/bridge-the-gap). Take your reframed problem and ask why five times. Why don't customers succeed in the first 30 days? Because they don't know which features to use. Why? Because onboarding doesn't connect to their specific goals. Why? Because we onboard everyone the same way. Now you have a solvable problem: personalized onboarding based on customer goals. That's different from "reduce churn."
Step 5: Test the reframe. Ask your team: "If we solved this reframed problem, would the original problem disappear?" If yes, you've found the real problem. If no, reframe again.
Why Reframing Is Hard
Reframing feels like going backward. Your team has been working on the problem for weeks. They have momentum. Suggesting the problem itself might be wrong feels like throwing away progress.
It's not. It's turning a constraint into an advantage. The constraint of having to re-examine your assumptions produces better solutions than the freedom to keep running in the wrong direction.
When ArcelorMittal's 710 leaders went through the experience with Duke Corporate Education, the reframing moment was consistently rated as the most valuable learning. Leaders watched their teams struggle with what they thought was the problem. Then, through the debrief, they saw the actual problem. The shift was immediate.
One participant said: "I realized we've been solving the wrong version of every problem for two years. Not because we're not smart. Because we never stopped to check."
The Yes And Connection
Reframing requires building on existing thinking rather than dismissing it. When someone says "the problem is X," responding with "no, the problem is Y" creates defensiveness. Responding with "yes, and what if we looked at it from this angle" creates exploration.
The Yes And framework makes reframing collaborative instead of combative. The original problem statement isn't wrong. It's incomplete. Reframing adds the missing dimension.
Reframing in Practice
Your team could practice this tomorrow. Take a problem you've been stuck on for more than two weeks. Run the five-step exercise. If the reframed version doesn't feel dramatically different from the original, you haven't gone deep enough.
The best reframes feel uncomfortable. They challenge assumptions the team has treated as facts. "We assumed the problem was pricing. It's actually positioning." "We assumed the problem was talent. It's actually role clarity." "We assumed the problem was technology. It's actually communication."
A 3.5-hour immersive experience teaches reframing through direct experience. When the ship is sinking and your first three approaches fail, you're forced to look at the problem differently. That forced reframing becomes a skill teams carry into every project.
The innovation technique of pausing before solving is the micro-version of reframing. Both require the discipline to examine the problem before attacking the solution.
Book a 20-minute walkthrough and I'll show you how the simulation teaches teams to reframe problems under pressure — the exact skill that separates stuck teams from breakthrough teams.
Read next: Why Your Team Defaults to the First Idea