There's a moment in most early-stage startups when the founder makes a decision that feels completely logical and turns out to be exactly wrong.
Hiring a designer too early, at the wrong level, is one of them.
I don't mean you shouldn't have a designer. I mean the designer you hire — the mid-level product designer with three to five years of experience who can take a brief and deliver polished screens — is often the wrong hire for the moment.
Here's why.
What you think you're buying
When a founder hires their first designer, they're usually solving a specific problem: there's too much design work and not enough capacity. The backlog is growing. Features are shipping with rough UI. The product looks like it was built by engineers.
The hire is supposed to fix this. And it does — for a while. Screens get designed. The backlog clears. Things look better.
Then the harder problem surfaces.
What you're actually buying
A mid-level designer can execute a clear direction. What they can't do is establish one.
They can design the navigation once you've decided how it should work. They can't tell you that the navigation model you've been using for eighteen months is why users can't find anything.
They can produce a polished onboarding flow from a brief. They can't tell you that the brief is wrong and the onboarding problem is actually a product positioning problem.
Those are judgment calls. Judgment comes from experience — from having seen what happens when you make the same mistake ten times on ten different products.
A designer with three years of experience, working at their second or third company, hasn't made those mistakes yet. So they execute what they're given. And if what they're given is wrong, they execute wrong things very polished.
The management tax
There's a second problem, which is that someone has to set the design direction. In the absence of a senior designer who can do it themselves, that person is usually you.
This is the failure mode founders don't see coming. They hire a designer expecting to be free of design decisions. Instead, they find themselves in weekly design reviews, explaining what they were trying to achieve, pushing back on work that missed the brief, writing longer briefs to compensate for the misses.
The design work is getting done. But you're doing half of it.
What senior capacity first actually looks like
The right sequence, for most early-stage companies, is this: bring in someone senior enough to own design independently before you hire someone junior enough to execute it.
Senior doesn't mean expensive. It means experienced enough to diagnose the problem before designing the solution. To push back on the brief. To flag the engineering implication before the engineer does. To look at the product and tell you what's wrong with it, not just what you asked them to fix.
Once that person has established what good looks like — the component system, the design language, the decision-making framework — you can hire junior designers to maintain and extend it. The senior judgment is now embedded in the system, not dependent on the individual.
When the mid-level hire does make sense
This isn't a universal rule. If you have a strong CPO or a founding designer who already provides the senior judgment layer, a mid-level hire can work well. You have the direction; you need the execution.
The mistake is hiring execution capacity when what you need is direction capacity — and spending six months wondering why you're still involved in every design decision.
The question to ask yourself
Before your next design hire, ask: do I know clearly what good design looks like for this product, and can I communicate that without much explanation?
If yes, hire execution.
If no — hire judgment first.
---
*Illustration idea: Two org charts. Left: "What you think you're buying" — designer slot is filled, founder is free. Right: "What actually happens" — designer needs direction, founder is still in the loop on every decision.*
Daniel Tkačenko
Founder NotTooMuch