The Most Underrated Desing Skill: Saying No
As designers, we love ideas.
New features.
New flows.
New possibilities.
There’s always something more we could add.
But over time, I realized something uncomfortable:
The problem is rarely a lack of ideas.
The problem is too many of them.
The moment everything starts to break
Every product starts simple.
Clear idea.
Clear direction.
Clear purpose.
Then slowly…
One feature gets added
Then another
Then “just a small improvement”
And before you notice:
The product starts losing its clarity.
Not because the ideas are bad.
But because there are too many.
Saying no is not negative
At first, saying no feels wrong.
You don’t want to block ideas
You don’t want to slow the team
You don’t want to seem difficult
But here’s the shift:
Saying no is not rejection
It’s protection
You’re protecting:
The product
The experience
The vision
The two questions I keep asking
Over time, I reduced everything into two simple questions.
I ask them almost every day.
1. Why?
Why are we doing this?
Note:
Because someone asked
Because it “might be useful”
Because competitors have it
But:
What problem does this actually solve?
If the answer is unclear…
that’s already a signal.
2. Do we really need this?
This one is even harder.
Because most things can be useful.
But the real question is:
Is it necessary?
There’s a big difference between:
Useful
And essential
If we removed this feature:
Would the product break?
Or would it actually become clearer?
Most features are noise
This is something I started noticing:
many features don’t improve the product
they just make it heavier
They add:
More decisions
More complexity
More cognitive load
Clarity comes from removal
Good design is often associated with:
Creativity
Aesthetics
Innovation
But in reality, a big part of it is:
Editing
Removing things.
Simplifying.
Focusing.
Not asking:
“What else can we add?”
But asking:
“What can we remove?”
Final thoughts
The best products I’ve seen are not the ones that tried to do everything.
They’re the ones that knew:
What they are
and what they are not
So now, whenever I design something, I pause and ask:
Why?
Do we really need this?
Because sometimes the most impactful decision is not what you add…
But what you choose to leave out.
As designers, we love ideas.
New features.
New flows.
New possibilities.
There’s always something more we could add.
But over time, I realized something uncomfortable:
The problem is rarely a lack of ideas.
The problem is too many of them.
The moment everything starts to break
Every product starts simple.
Clear idea.
Clear direction.
Clear purpose.
Then slowly…
One feature gets added
Then another
Then “just a small improvement”
And before you notice:
The product starts losing its clarity.
Not because the ideas are bad.
But because there are too many.
Saying no is not negative
At first, saying no feels wrong.
You don’t want to block ideas
You don’t want to slow the team
You don’t want to seem difficult
But here’s the shift:
Saying no is not rejection
It’s protection
You’re protecting:
The product
The experience
The vision
The two questions I keep asking
Over time, I reduced everything into two simple questions.
I ask them almost every day.
1. Why?
Why are we doing this?
Note:
Because someone asked
Because it “might be useful”
Because competitors have it
But:
What problem does this actually solve?
If the answer is unclear…
that’s already a signal.
2. Do we really need this?
This one is even harder.
Because most things can be useful.
But the real question is:
Is it necessary?
There’s a big difference between:
Useful
And essential
If we removed this feature:
Would the product break?
Or would it actually become clearer?
Most features are noise
This is something I started noticing:
many features don’t improve the product
they just make it heavier
They add:
More decisions
More complexity
More cognitive load
Clarity comes from removal
Good design is often associated with:
Creativity
Aesthetics
Innovation
But in reality, a big part of it is:
Editing
Removing things.
Simplifying.
Focusing.
Not asking:
“What else can we add?”
But asking:
“What can we remove?”
Final thoughts
The best products I’ve seen are not the ones that tried to do everything.
They’re the ones that knew:
What they are
and what they are not
So now, whenever I design something, I pause and ask:
Why?
Do we really need this?
Because sometimes the most impactful decision is not what you add…
But what you choose to leave out.