Solve the Right Problem First: Using Design Thinking to Create Better Business Solutions

🧭 Dojo Compass

Module: Decision-Making, Innovation and Lateral Thinking

Focus Area: Innovation and Execution

Key Article Point:

Many business problems persist not because organizations lack intelligence or effort, but because they solve the wrong problem. Design thinking provides a practical framework for uncovering the real challenge before investing time and resources in a solution. Instead of starting with assumptions, it starts with people.

This article presents a practical executive framework for using design thinking to improve products, services, customer experiences, and internal operations.

🎯 Key Challenge

Busy executives are expected to solve problems quickly.

The temptation is to jump immediately to solutions:

“Let’s add another feature.”
“Let’s reorganize the department.”
“Let’s buy new software.”
“Let’s lower prices.”

Unfortunately, many business problems are symptoms rather than root causes.

Organizations frequently spend significant resources solving the wrong problem, only to discover that the original challenge remains.

The competitive advantage is not simply solving problems faster—it is defining them more accurately.

🥋 Dojo Solution

Design thinking replaces assumption-driven decision-making with human-centered problem solving.

Rather than beginning with a preferred solution, it asks:

What is actually happening?

Why is it happening?

What are people truly trying to achieve?

Only after those questions are answered does solution development begin.

This dramatically increases the likelihood that the final solution creates meaningful value.

At its core, design thinking follows five stages:

Understand the people involved.
Define the real problem.
Generate multiple possible solutions.
Test ideas quickly.
Learn, refine, and scale.

Instead of searching for the perfect answer immediately, design thinking creates a disciplined process for discovering it.

🏗️ Putting It Into Practice

Step 1. Begin with Empathy

Every business challenge affects someone.

Those people may include:

customers
employees
suppliers
partners
investors

Instead of relying solely on reports and dashboards, spend time understanding how they experience the problem.

Useful questions include:

What frustrates them?
What slows them down?
What workarounds have they created?
What outcome are they really trying to achieve?

The objective is not to validate existing assumptions but to discover new ones.

Executive Action

Schedule five customer or employee interviews before approving a major improvement initiative.

Step 2. Define the Real Problem

After collecting information, organize recurring observations into common themes.

Look for repeated:

frustrations
delays
unmet expectations
emotional responses
operational bottlenecks

Then write a simple problem statement.

A useful format is:

The user…

needs…

because…

For example:

Busy sales managers need faster access to customer information because administrative work reduces the time available for selling.

Notice that this defines a need—not a solution.

The problem is not “we need better CRM software.”

The problem is lost selling time.

Step 3. Generate Multiple Solutions

Once the problem is clear, resist the temptation to pursue the first idea.

Instead, deliberately explore multiple approaches.

Ask questions beginning with:

“How might we…”

Examples include:

How might we eliminate unnecessary approvals?
How might we reduce waiting time?
How might we simplify the customer journey?
How might AI support rather than replace employees?
How might we solve the problem without increasing costs?

The objective is quantity before quality.

Unexpected ideas often emerge only after the obvious ones have been exhausted.

Step 4. Prototype Before You Commit

Large implementations create large risks.

Instead, test ideas on a small scale.

Prototypes may include:

pilot programs
mockups
process simulations
simple software demonstrations
role-playing customer interactions
limited geographic launches

A prototype is designed to answer one question:

Will this actually improve the user’s experience?

Testing early is almost always less expensive than correcting mistakes later.

Step 5. Measure, Learn, and Improve

Implementation is the beginning of learning—not the end.

Monitor:

customer satisfaction
employee feedback
adoption rates
productivity
cost savings
unexpected problems

Use this information to improve the solution continuously.

Great organizations rarely launch perfect products.

They launch good products—and then improve them relentlessly.

📌 Key Takeaways

Design thinking begins by understanding people rather than proposing solutions.
Many business problems persist because organizations solve symptoms instead of root causes.
Effective problem statements define user needs rather than preferred solutions.
Exploring multiple ideas before selecting one increases innovation.
Small-scale prototypes reduce implementation risk.
Continuous feedback transforms good solutions into exceptional ones.

🌿 Reflection

Many executives pride themselves on being decisive.

Yet one of the greatest leadership disciplines is resisting the urge to solve a problem before fully understanding it.

Design thinking reminds us that speed is valuable—but only when moving in the right direction.

The shortest route to a poor outcome is solving the wrong problem exceptionally well.

The best leaders invest time in understanding before acting.

Doing so often reveals opportunities that were invisible at the beginning.

⚔️ Dojo Mission

Choose one recurring business problem that has resisted previous solutions.

Over the next week:

Interview five people directly affected by the issue.
Write a one-sentence problem statement beginning with “The user needs…”
Brainstorm at least ten possible solutions before evaluating any of them.
Select one idea that can be tested within 30 days.
Measure what improves—and use those lessons before expanding further.

The objective is not to find the perfect solution immediately.

It is to build an organization that becomes better at solving the right problems.