Why Defining the Problem is the Foundation of Innovation?

In Design Thinking, identifying and clearly defining a problem is one of the most critical steps. This phase, often underestimated, is essential for steering teams toward creative and meaningful solutions. This article explains why defining the problem matters and how it significantly impacts the success of design projects.

Why is Defining the Problem so Important?

If you’ve ever spoken with me or attended my talk at UX-Conf titled “How to Define Your Value in the Age of AI”, you know how much I emphasize deeply understanding and clearly framing the problem. As a UX Strategist, I firmly believe this step drives both innovation and value creation.

From my experience facilitating workshops, I’ve learned that for Design Thinking to be effective, certain elements must be in place:

• The team must fully grasp the problem. It’s not enough to just read a brief; everyone needs to understand the core of the issue and the challenges it presents.
• The problem definition must guide relevant solutions while staying within the project’s scope.
• A well-defined problem leads to one core solution, even if that solution might take different forms.

Unfortunately, problems are often poorly defined, leading to ineffective or irrelevant solutions. That’s why it’s crucial to properly articulate and, if necessary, challenge how issues are presented by clients or stakeholders.

The Transition from Solution-Finder to Problem-Finder

At the start of my career, I was heavily focused on solving problems—eliminating pain points and fixing broken experiences. After all, we’re often told that design is all about problem-solving.

But over time, I realized that finding the right problem to solve is even more important. This is where things get tricky: defining a problem isn’t easy because it often involves untangling causes from consequences.

Understanding the Root Cause

The root cause, or “first cause,” is the fundamental reason a problem exists. When we confuse causes with consequences, we risk addressing symptoms rather than solving the real issue. This phenomenon is sometimes referred to as the “Stork Effect.”

For example, abandoning a shopping cart on a website is a consequence, not the root problem. The real issue might be frustration with the checkout process or unclear pricing.

Here’s another simple analogy: Imagine you’re running a 10km race. At the 7km mark, you stop and are disqualified. The consequence is clear: you didn’t finish the race. But the root cause? Fatigue.

Asking “Why?” to Find the First Cause

To get to the root cause, you need to analyze the situation step by step, asking “Why?” repeatedly.

Using the race example:

1. Why was I disqualified? Because I stopped at the 7th kilometer.
2. Why did I stop? Because I was too tired.
3. Why was I tired? Because I didn’t have enough stamina.
4. Why didn’t I have enough stamina? Because I didn’t train properly.
5. Why didn’t I train? Because I didn’t create a training plan in advance.

Here, the root cause isn’t just fatigue—it’s the lack of preparation. By identifying this, we can pinpoint a clear solution: better preparation.

The Power of Asking “Why?”

I often repeat how important it is to ask “Why?”—to the point that I might annoy those around me! But this question is the cornerstone of Design Thinking. As Simon Sinek explains in Start With Why, understanding the deeper reasons behind actions or decisions is essential for solving the right problems.

Asking “Why?” pushes us beyond surface-level answers and helps uncover the real needs and motivations behind user behavior.

Turning Problems into Solutions

Once you’ve identified the root cause, the next step is crafting a solution. While the problem may have only one true answer, the solution can take on various forms depending on constraints like time, resources, or technology.

For instance, in the race example, the solution is to improve training. But the form it takes could vary:

• Using a mobile app for workouts.
• Designing a printed training schedule.
• Hiring a personal trainer.

Design brings this solution to life in the most suitable way for the situation.

Conclusion

Defining the problem is a vital step in Design Thinking. It requires continually asking “Why?” to uncover the root cause and guide teams toward meaningful solutions.

A well-defined problem has only one true solution, but that solution can adapt to different circumstances. This adaptability ensures that responses remain practical, innovative, and aligned with user needs.

Always remember: great design starts with a clear problem. What’s your process for uncovering the real issues in your projects? Share your thoughts below!

Contact me, if you need me!

How Can I help?

I believe that we have to redefine our self-worth if we want to thrive in today’s world. Let me help you find it, so you can start your journey with peace of mind, feeling that you are where you belong.