One of the biggest misconceptions about design is that it's primarily about solutions.

People often imagine designers creating interfaces, wireframes and prototypes.

But before any of those things happen, there's usually a much more important activity taking place:Asking questions.

Over the years, I've learned that the quality of a project is often determined by the quality of the questions asked at the beginning.

The first problem is rarely the real problem
‍
When a project starts, stakeholders usually arrive with a solution in mind.
‍
"We need a dashboard."
‍
"We need a new feature."
‍
"We need to redesign the homepage."

But these requests are often symptoms rather than root causes.

The real challenge is understanding why the request exists in the first place.

What problem are we actually trying to solve?

The answer is not always obvious.

Curiosity creates better outcomes
‍
One of the most valuable skills a designer can develop is curiosity.

Curiosity helps uncover assumptions.

It reveals constraints.
‍
It exposes gaps in understanding.

And it often leads to opportunities that weren't visible at the start of the project.

The goal isn't to challenge people for the sake of it.

The goal is to understand the situation deeply enough to make informed decisions.

Research begins with questions
‍
User interviews.

Workshops.

Surveys.

Usability testing.

All of these methods rely on one thing: Good questions.

A poorly designed question can reinforce assumptions.

A thoughtful question can reveal entirely new perspectives.

The difference can completely change the direction of a project.
‍
Questions reduce risk
‍
Every product decision involves uncertainty.

Questions help reduce that uncertainty.

Who are the users?

What are they trying to achieve?

What obstacles do they face?
‍
What does success look like?

The more clearly these questions are answered, the more confidently teams can move forward.

Solutions become easier
‍
Something interesting happens when teams spend enough time understanding the problem.

Solutions often become surprisingly clear.

Many design challenges feel difficult because the problem hasn't been properly defined.

Once everyone understands the real challenge, decision-making becomes faster and more aligned.

Great products are built on understanding
‍
The projects I've enjoyed most weren't successful because they had the most features.

They were successful because teams invested time in understanding users, goals and constraints before making decisions.

Good design is rarely about guessing correctly.

It's about learning systematically.

Looking back
‍
The longer I work in product design, the less interested I become in quick answers.

Instead, I find myself focusing on better questions.

Because behind every successful product is usually a team that took the time to understand the problem before trying to solve it.

And that's where good design begins.