Effective problem-solving capability lies not in repeated experience, but in a structural approach that can be consistently applied even in unfamiliar situations encountered for the first time. This article provides step-by-step guidance on the principle of "deeply understanding the problem" and practical methods for problem analysis and finding alternatives that can be applied across diverse situations. It explains in accessible terms, through real-world cases, the importance of solid analysis over quick execution, techniques for distinguishing real problems from solutions, and practical frameworks for generating and evaluating alternatives.
1. The True Meaning of Problem-Solving Ability
Many companies emphasize "excellent problem-solving skills" in their job postings, but when you really think about what this means, the core is the ability to find breakthroughs even when facing unfamiliar, new problems.
"Very few people can consistently solve problems they've never encountered before."
Most people can only solve problems they've dealt with before. For example, someone who built marketing attribution at a previous job simply reproduces it the same way. However, truly exceptional problem-solving ability depends on whether you can take a structural approach when facing problems without a guide or encountering them for the first time.
2. The Trap of Fast Execution: Discussing Solutions Before Defining the Problem
Especially in fast-growing organizations, teams often jump straight to execution plans (solutions) before sufficiently understanding the problem. But when you leap into the "solution space" first:
"If you don't properly understand and define the problem, there's a great risk of choosing the wrong solution."
In these cases, you think you "moved fast," but end up wasting even more time going back and redoing things later.
For example, when a startup was trying to implement an account scoring system for its sales team, most people jumped straight into discussions about external vendors or machine learning models. But the fundamental questions -- "What is the score actually needed for?" and "What are the specific requirements?" -- were missing entirely.
3. The Difficulty of Reversing Decisions and Calculating the 'Cost of Being Wrong'
When assessing the type of problem, the most important criterion is "the cost of making a wrong decision." And the key factor determining this cost is how easily (or difficulty) the decision can be reversed.
- Easily reversible decisions (e.g., experimenting with meeting formats) allow for quick tries and corrections.
- Decisions that are difficult (or expensive) to reverse and have significant business impact (e.g., entering a new market, large-scale organizational changes) require much more caution and structured problem definition and analysis.
"Jeff Bezos compares these decisions to 'one-way doors' and 'two-way doors.'"
In other words, the goal is to minimize expected loss (Expectation Cost), and the more irreversible the decision, the more effort is required.
4. Breaking Big Decisions into Small Experiments
Even for high-barrier decisions, risk can sometimes be reduced by dividing them into small experiments (tests).
Always ask yourself: "Can I gather data through an initial small-scale experiment to resolve the uncertainty of the decision?"
For example, when considering whether to enter the UK market, a wise step-by-step approach would be to have U.S.-based sales personnel contact UK customers first before opening a local office.
This way, instead of going "all-in" with billions from the start, you can incrementally test the possibility and expand organizational investment as needed.
5. The 'Opportunity Cost' of Limited Resources and the Ripple Effect of Choices
You must recognize the trade-offs where one choice excludes another and the constraints on future options.
For example, when considering whether to publicly counter a competitor's policy change, you must clearly recognize that such a position connects to future organizational strategy as well.
"The greater the ripple effect of a decision, the more effort should be put into problem analysis and the decision itself."
6. Recurring Problems Require Automation/Principle-Based Approaches
If problems recur, the approach to solving them should be different.
Types of Recurring Problems
- The exact same task is repeated (e.g., classifying customer inquiries every week) -> Automation
- Similar problems recur (e.g., whether legal review is needed per project) -> Establishing policies and principles
"You should check whether you've been repeating stopgap measures without addressing the root cause."
The recurring debates within Uber's organization were also a case where the real cause was not a policy issue ("when to give additional incentives") but rather the "definition of roles and authority."
7. Distinguishing the Real Problem from 'Tasks That Look Like Problems'
In actual work, you don't usually receive the problem itself -- most of the time, you receive "do this task" (i.e., a solution someone has already thought of). That's why you can only propose effective solutions by uncovering the context of the real problem, not the given task.
"If you haven't sufficiently understood the problem, you can't come up with a proper solution."
- Example: When receiving a request to "pull the number of companies by country," you should recognize that the actual core problem is market entry prioritization to propose better analysis and solutions.
However, if the big direction has already been established above (e.g., "market entry is confirmed, just deciding which country"), you should also be careful not to obsess over excessive "why" questions and waste others' time.
8. Generating Alternatives: Using the MECE Framework and Issue Trees
When generating solution candidates (options) for a problem, they should be MECE (Mutually Exclusive, Collectively Exhaustive). This ensures you can verify that all alternatives have been identified without gaps or overlaps.
"In fact, 'Do nothing' is an option that must always be included."
While gathering diverse ideas through team brainstorming, the final step of having one person organize and structure them in a MECE format is essential.
For complex problems, visual structuring tools like issue trees are also very useful.
9. Comparing Options: Practical Evaluation Criteria and Quick Screening Strategies
First establish a clear evaluation framework for comparing alternatives by criteria (e.g., effectiveness, cost efficiency, implementation timeline, etc.). The key principles are:
- Focus analysis on the factors with the greatest impact
- Immediately eliminate candidates that fail to meet mandatory requirements to minimize the analysis workload
"The goal of analysis is to screen out as many candidates as early as possible and reach maximum conclusions in minimum time."
Additionally, if the final execution/decision authority rests with someone else, it's important to have the sense to anticipate what they will prioritize and establish comparison criteria accordingly.
10. How to Effectively Drive Decisions (Preview)
Since this article has covered problem structuring and option evaluation methods, the remaining step is the process of efficiently presenting options to the decision-maker and getting approval. The next article will cover:
- How to present options and recommendations
- Know-how for running an efficient decision-making process
- Tips for preventing the endless rehashing of already-decided issues
- Major decision-making frameworks used by companies
Stay tuned and subscribe!
Conclusion
Effective problem-solving ability comes not from repeated experience, but from a structured, analytical approach. "Correctly defining the problem" is half the battle, and MECE structuring plus substantive review of alternatives determines the quality of the solution. The attitude of "solving how to solve the problem" goes further than improvisational execution.