Curiosity gets talked about like a personality trait.
Curiosity gets talked about like a personality trait.
But in practice, it’s a discipline.
Not the “fun” kind of curiosity. The useful kind.
The kind that shows up when a plan looks clean on paper, but something feels off in the room.
In design and in organizations, most problems aren’t caused by a lack of ideas.
They’re caused by unexamined assumptions.
Curiosity is what interrupts those assumptions before they become expensive.
1) Curiosity starts where certainty gets comfortable
The fastest way to make a bad decision is to fall in love with the first explanation that feels reasonable.
Curiosity asks:
- What are we assuming is true?
- What would we notice if it wasn’t?
- What’s the simplest way to test it before we commit?
2) Curiosity is a tool for seeing what people won’t say out loud
In projects, the “real” problem is often quiet:
- a constraint nobody owns
- a handoff nobody mapped
- a risk everyone sees but no one wants to name
Curiosity creates permission to surface it early, when it’s still cheap to fix.
3) Curiosity improves design by improving questions
Great design rarely comes from a genius answer.
It comes from a better question.
Instead of “What do you want?” try:
- What frustrates you repeatedly?
- What do you avoid because it’s annoying?
- What do you do in workarounds that the plan doesn’t acknowledge?
That’s where the real requirements live.
4) Curiosity is how you reduce rework
The opposite of curiosity isn’t knowledge.
It’s rushing.
When teams skip the “why,” they pay for it later in:
- redesign
- change orders
- delayed decisions
- friction between trades
- and a final product that feels slightly wrong
Curiosity is not slow. It’s preventative.
Final
Note
I don’t think curiosity is about chasing novelty.
I think it’s about attention.
Attention to what’s working, what’s breaking, and what keeps repeating.
That’s the discipline, and it’s where better outcomes quietly begin.