Shipping fast without losing craft

Speed and quality are usually framed as opposites. I don’t think that’s right. The real tension is between speed and completeness — and completeness is often overrated.

What slows work down

Most slow work isn’t slow because of craftsmanship. It’s slow because of indecision, rework, and the endless buffering between “good enough to ship” and “what I wish it could be.”

Perfectionism is often anxiety with a productivity mask on. The feature isn’t shipping because you’re uncertain whether it’s right, not because you’re making it better.

The 80% rule

There’s a threshold in most projects where the last 20% of quality takes 80% of the time — and delivers maybe 10% of the value. The question isn’t whether to care about craft. It’s knowing where the curve bends.

For a design system component used across 40 screens, that last 20% is probably worth it. For a landing page variant you’ll test for two weeks and then replace, it almost certainly isn’t.

Making speed a design decision

The fastest way to ship good work is to make clear decisions early. Not fast decisions — clear ones. A decision you make confidently in day one takes five minutes. A decision you defer to day five takes five minutes plus four days of ambient uncertainty.

Constraints help. When you commit to a grid, a type scale, a colour palette — you eliminate a thousand downstream micro-decisions. The fewer choices you’re making per hour, the faster you move without losing coherence.

What craft actually means

Craft isn’t polish. It’s not the number of hours you spent or the number of states you accounted for. It’s the quality of the decisions — whether the thing does what it needs to do for the person who’ll use it, and whether the reasoning holds up under scrutiny.

You can ship fast and with craft. What you can’t do is ship incomplete thinking. That’s the real gap.