Design systems at the wrong time are a trap

Why early-stage startups should focus on shipping, not systematizing

The past few months, I’ve helped a few early-stage startups get their product off the ground. 2 or 3 engineers, no designer yet, just a vague idea of what needs to exist.

Half the time, the teams come from big tech. Strong resumes. Strong pitch decks. Strong opinions. And one request always shows up: “Julie, where’s the design system?” Or worse: “I can’t work because Julie hasn’t finished the design system.” (Oh, poor baby.)

A design system feels smart. Scalable. Efficient. But when you don’t even have a product, it’s none of those things.

Design systems are great when you’re shipping variations of the same thing, over and over. Not when every screen is a question and every feature is a maybe.

Early on, you don’t need tokens or components. You need speed, conviction, and a willingness to throw stuff out.

And if I hand over tokens on day one, they’ll be irrelevant by Friday. (Don’t ask me how I know.)

Trying to systematize too early just slows you down. You end up designing constraints instead of answers. You also end up trying to maintain a system that doesn’t serve your product yet.

So no, I won't give you a design system or even tokens on day one. I build the product. I give you just enough structure to move.

First, ship. Then systematize.