Justin Bartak · Strategy · September 12, 2025 · 3 min read ·
Startups Need Taste, Not Design Systems
TL;DR
Design systems create order. But order without soul is sterile. In the earliest days of a startup, the goal is not efficiency. It is identity.
Design systems create order. But order without soul is sterile. In the earliest days of a startup, the goal is not efficiency. It is identity. It is creating something that feels inevitable, almost obvious, in how right it is. Too many teams systemize too soon, mistaking consistency for quality. But a lifeless design system only scales lifelessness.
A system is a multiplier. Taste is the source.
What matters first
Before tokens and components, you need a point of view.
You need decisions that cut through noise and refuse compromise. You need a small set of crafted patterns that feel impossibly right, not because they are standardized, but because they are true.
Early stage priorities are simple:
- A point of view that creates coherence
- Uncompromising decisions that show conviction
- A handful of patterns that feel calm, obvious, and intentional
When those are present, consistency becomes natural. When they are missing, consistency becomes a costume.
Taste is strategy
Taste is not decoration. Taste is direction.
It is the invisible hand that decides what should exist and what must never exist. It sets the emotional tone. It defines the cadence of interactions. It shapes restraint. It determines when to be quiet and when to be bold.
A design system cannot answer the most important question:
Does this move someone
Only taste can.
Because users do not fall in love with consistency. They fall in love with clarity, confidence, and feeling understood.
Don't systemize chaos
If your product is confusing, a system will only make that confusion consistent. If your product lacks a heartbeat, a system will preserve that lifelessness.
Systems are not a cure. They are an amplifier.
First, make something worth amplifying.
That means:
- Find the core job and remove everything else
- Craft one primary flow until it feels inevitable
- Establish a visual and interaction language that carries emotion, not just rules
- Raise the bar on details until the experience feels trustworthy
Then and only then do you standardize.
Taste before systems
The best companies did not begin with guidelines. They began with obsession.
Obsession for feel. For proportion. For the way a corner curves. For how a button responds. For the way a product breathes when you hold it.
Only later did they codify those decisions.
The system was not the spark. It was the amplifier.
Final thought
Startups do not need a design system on day one.
They need a soul. They need a point of view. They need taste.
Build something undeniably right first. Then scale it.
Related reading: The Rise of Claude Code. The Death of Figma and Design Systems., Zero-to-One Is a Taste Game, and I Design Belief, Not Just Products.
