Every experienced designer can tell you about that moment when something in a design feels off before they can say why. The hierarchy doesn't quite work. The flow has friction. A component feels misused. They can't always articulate it immediately, but they know to dig.

That's design intuition. And it's one of the most underrated things that separates designers who grow quickly from those who plateau.

What design intuition actually is

Intuition sounds mysterious. It isn't. It's pattern recognition built from a large enough set of experiences that your brain starts connecting dots faster than your conscious reasoning can catch up.

A doctor with 20 years of experience can walk into a room and sense something is wrong before they've run a single test. A chess player sees the weakness in a position before they've calculated every line. A senior designer looks at a screen and knows the primary action is going to get missed — before user testing confirms it.

This isn't magic. It's compressed experience.

The question is: how do you build that compression faster?

Study work with intent, not just admiration

Looking at good design is useful. Most designers do it. Fewer do it with the right questions.

When you look at an interface you admire — Figma, Linear, Stripe's dashboard, whatever it is — don't just notice that it feels good. Ask why it feels good.

What's the hierarchy doing? Where does your eye go first, and why? What's been removed that a less confident designer would have kept? Where has the designer made a strong choice rather than a safe one?

And do the same with design you think is bad. Why does it fail? Is it a hierarchy problem? A density problem? Mismatched visual weight? Unclear affordances?

The more precisely you can name what's working and what isn't, the faster your intuition builds. Vague appreciation doesn't compound. Specific analysis does.

Do more design reps — deliberately

Volume alone won't build intuition. A designer who spends five years shipping safe work in a predictable context doesn't accumulate nearly as much useful signal as one who spends two years solving genuinely varied, difficult problems with fast feedback loops.

The key is feedback. You need to know whether your design decisions were actually right — not just whether stakeholders approved them.

That means caring about outcomes after things ship. Watching session recordings. Reading support tickets for features you designed. Sitting in research sessions where users interact with your work. Getting into the habit of asking what changed as a result of a design decision, not just was the design finished.

Intuition is built on correct predictions. Correct predictions come from understanding which of your past decisions were actually right.

Build a vocabulary for what you're noticing

Intuition without language is hard to develop further. When you sense something is wrong but can't name it, you can't deliberately look for that pattern in other work, you can't discuss it with other designers, and you can't improve it systematically.

Build a working vocabulary for the things you're noticing.

Not the formal terminology from design school — though that has its place. Practical descriptions that you actually use when thinking through problems. "The hierarchy is fighting itself." "This is too polite — there's no clear primary action." "The empty state assumes context the user doesn't have." "This interaction is teaching me nothing about what just happened."

Writing crits of your own past work is a good way to develop this. Go back to something you shipped six months ago. What do you notice now that you didn't then? What would you change? What did you get right without fully understanding why?

Expose yourself to adjacent fields

Design intuition deepens when it's informed by how humans work, not just how interfaces are structured.

Behavioural economics. Cognitive psychology. The way writing works — specifically what makes a sentence clear versus vague, what creates forward momentum in prose, what makes people stop reading. Architecture, where decisions about space, light, and flow have been studied and iterated over centuries.

These fields give you mental models that transfer directly into product design. The best designers you'll meet have usually read widely outside design. That breadth shows up in their judgment.

The long game

Design intuition doesn't develop on a timetable. You can accelerate it, but you can't rush it.

What you can do is make sure that every project, every crit, every shipped feature, and every piece of design you study leaves you with slightly more signal than before. Over time, that compounds into something that looks like taste — and that taste is what makes the difference between designers who get trusted with increasingly complex, important problems and those who don't.

Judgment and intuition are exactly what the Senior Product Designer Playbook was built around. Not tool tutorials or process templates, but the thinking behind great design decisions — the patterns that take years to develop, condensed into something you can act on now.

How to Develop Design Intuition (And Why It Matters More Than Tools)