How to Solve the Right Problem

If you want to be a more effective problem solver, this blog is centered around the idea of identifying good problems to solve. However, I have always resisted the temptation to merely tell people to “solve the right problem.” In fact, it frustrates me now when writers offer that advice as if it will help anyone.

The reason I focus on not solving the wrong problem (which I call avoiding a type 3 error) is because it’s both easier and more actionable.

When people identify a problem to solve, they generally are stating what they think the right problem is. It’s not like people walk around saying “well, I know this isn’t the right problem to solve, but I’d rather solve the wrong one.”

However, people do often have concerns about a particular problem that they recognize might make it not-right. If my car is making a weird noise, I suspect the issue is something that needs to be repaired, not just that I’d like the car to be quieter.

My solution is comparison; If you have a statement of a problem, we can compare it to other versions of the problem and pick the best one. Solving the wrong problem means you have an issue with your choice of problem, but you solve it anyway. Not solving the wrong problem means you either feel good about your choice of problem, or at least you’ve considered your alternatives and found nothing better.

Going back to the car example: I might have a choice to replace a broken component, or to remove it so it won’t be noisy. Since cars generally need each component to work, replacing it is almost certainly the better problem. But the comparison is what makes it clear we have a better option.

By re-framing “solve the right problem” as “don’t solve the wrong one” we have a more effective way to think about our alternatives. Ultimately, I believe that shift in view can help all of us be better problem-solvers.