Speed Without Judgment

Somewhere along the way, the industry decided that speed is the ultimate signal of talent.

Open any design community and you'll find the same archetype being celebrated: the new grad who redesigned an app in a weekend, the junior who ships a feature every sprint, the self-taught designer who built a design system in three months. “Cracked,” people call them. Fast. Prolific.

Raw speed is impressive. It shows energy, ambition, and real capability with the tools. But I've watched what happens when speed runs ahead of judgment. And the people who pay for it are rarely the ones moving fast.

What speed looks like without experience

A fast designer without judgment doesn't make fewer decisions. They make more decisions, faster, with less information. And each one compounds.

They pick a layout pattern because it looks good, not because it maps to how users scan the page. They design a flow that works for the happy path and falls apart at the first edge case. They build a component that's beautiful in isolation and impossible to maintain at scale.

I've inherited work like this. Screens that looked polished until you asked basic questions: what happens when this field is empty? What if there are two hundred items instead of five? What does this look like in German? The designs didn't have answers because nobody slowed down long enough to ask.

The output looks productive. The velocity is real. But velocity without direction is just movement.

The judgment gap isn't about intelligence

The gap between a fast junior and a seasoned designer isn't talent. It's pattern recognition built from years of watching things go wrong.

When I design a complex component, I'm not thinking about how it looks with sample data. I'm thinking about the column with three characters in one row and forty in the next. About sort states, filter interactions, overflow, selection, bulk actions, loading, errors, and what happens when someone resizes their browser to half width.

That's not because I'm smarter. It's because I've shipped work that broke in every one of those scenarios and I remember the cleanup.

Judgment is internalized consequences. You can't speed-run it.

The industry's role in this

We've built an ecosystem that rewards speed over judgment and acts surprised when things break.

Design challenges in interviews are timed. “Redesign this app in 45 minutes.” That tests your ability to generate layouts under pressure. It doesn't test whether the layout would survive real users, real data, and real constraints.

Job postings ask for portfolios with ten case studies. How do you get ten case studies early in your career? By moving fast and treating everything as a portfolio piece, not by going deep on fewer problems.

Then companies hire someone optimized for speed, put them on a complex product, and wonder why design debt is piling up.

What seniors actually do differently

Experienced designers aren't slow. The difference is where they spend their time.

A junior spends 90% of their time in the tool and 10% thinking. A senior might spend 40% understanding the problem, 10% exploring, and 50% in execution. The Figma time is shorter, but the output is more considered because decisions were made before the first frame.

Seniors are also faster at saying no. No, this doesn't need a modal. No, we don't need a custom component — the existing one works. No, this edge case affects 0.3% of users. Every “no” is a decision that a less experienced designer would have turned into a week of work.

Speed isn't just how fast you produce. It's how much unnecessary work you avoid.

The mentorship failure

When a fast junior ships bad work, it's not entirely their fault.

Someone hired them. Someone gave them a complex problem without support. Someone reviewed their work and rubber-stamped it. Someone prioritized output speed over growth.

If you're a senior watching a junior move fast without depth and you're not intervening, you're not being supportive. You're being negligent. The best thing you can do for a talented junior is slow them down strategically — force them to present rationale before screens, document edge cases, sit in on user research and watch their assumptions fall apart.

That's not hazing. That's mentorship.

Speed with judgment is the actual goal

The goal isn't slowness. Slow, precious design is its own failure. The goal is speed with judgment — the ability to move quickly because you've internalized enough patterns to make good decisions without agonizing over each one.

A cracked new grad who moves fast, asks the right questions, and knows what they don't know? That's someone worth investing in.

But calling someone “cracked” purely because they're fast is like calling a driver skilled because they go 150 miles per hour. Speed is only impressive if you can also turn.