Experience doesn’t make designers faster. It changes where attention goes.

Early in my career, I assumed experienced designers were simply faster.

They weren’t.

Some of the quickest at producing interfaces I’ve worked with were early in their careers: fluent in every shortcut, quick to try a new plugin, and comfortable throwing away work that wasn’t landing. Meanwhile, I’d watch experienced designers spend disproportionate time refining decisions most people wouldn’t even notice.

It looked inefficient. It wasn’t. They were investing attention in different places, but it took them the same amount of time. By attention, I don’t mean concentration. I mean the specific areas where a designer focuses their limited cognitive effort on any given problem.

What actually changes with experience

Early on, the real challenge isn’t drawing the interface. It’s deciding.

Should the navigation live here? Is this layout good enough? Have I explored enough directions? Early in a career, a meaningful share of attention isn’t spent designing at all; it’s spent reducing uncertainty about a direction that hasn’t yet earned trust.

As experience grows, that question changes shape. The same designer stops asking, 'Is this right?' and starts asking, 'Is this the best version of right?' Experience doesn’t reduce attention. It changes where attention gets invested: exploration gives way to recognition.

I once watched a junior product designer rework the same onboarding flow five times in two days. Every version was usable. None of them shipped, because each one raised a new doubt: was the empty state too sparse? Would the third screen confuse a first-time user? Should the skip option be more prominent? The flow wasn’t the problem. The uncertainty about whether any version was defensible was the problem, and that doubt consumed almost all of the available time before a single pixel was touched.

That’s often when the marginal gains start coming from refinement rather than generation. Not because experience makes anyone slower, plenty of experienced designers execute quickly, especially with deep system knowledge, but because attention shifts toward things a less trained eye wouldn’t register at all: accessibility gaps, a transition that feels half a beat off, and content hierarchy that technically works but doesn’t quite breathe. The work hasn’t grown. The standard you’re holding it to has changed.

A principal designer reviewing that same onboarding flow would likely settle on a direction within the first ten minutes and then spend the next two days somewhere else entirely: whether the empty state respects screen readers, whether the skip option quietly undermines a metric the team cares about three steps later, or whether the whole flow is even solving a problem the product has. Less time spent deciding. Far more time spent on questions a junior designer wouldn’t yet know to ask.

Why this matters more than it looks

This is also why evaluating everyone by the same definition of productivity quietly optimises the wrong behaviours.

What looks like indecision is often uncertainty. What looks like perfectionism is often judgement. A design leader who spends most of the week in meetings might be designing just as much; they may be holding alignment for ten other people at once. I’ve sat in reviews where a principal designer said almost nothing about the screens themselves and spent the entire hour making sure three teams agreed on what the screens were even meant to solve. From the outside, that looks like the least productive hour in the room. That hour usually isn’t wasted.

The same tool creates different leverage depending on where attention is being invested, which is also why a single AI feature never lands the same way twice across a team.

A limitation worth naming

This pattern tracks depth of experience in a domain, not seniority on paper. A principal designer walking into healthcare for the first time may spend more attention on uncertainty than a mid-career designer five years into that same domain. Expertise is domain-specific: the pattern resets, at least partially, every time the terrain changes.

What this is actually about

I don’t think this is a piece about speed at all.

It’s about where designers spend their cognitive capital: the scarce resource isn’t time, it’s attention. Early on, designers consume their attention by finding the right answer. Later, it’s consumed by improving the answer. Eventually, it’s consumed by deciding whether the problem deserves solving in the first place. And it’s also, ultimately, why experience compounds into leverage: judgement and alignment don’t just solve a designer’s own problems faster; they remove problems for everyone working alongside them.

Perhaps many organisations don’t have a productivity problem at all. They have a measurement problem. We keep asking designers to move faster when we should first ask a different question: where do they actually invest their attention?

Because experience doesn’t save time. It changes where time becomes valuable.