Your design team doesn’t need a hierarchy. It needs a referee.
We have watched a dozen founders hire two senior designers, then spend the next six months wondering why the product feels like it was built by two different companies.
We have watched a dozen founders hire two senior designers, then spend the next six months wondering why the product feels like it was built by two different companies. One designer obsesses over craft, the other over user outcomes. Both are right. Both are furious. And the founder’s instinct, almost every time, is to draw an org chart and declare one of them the boss. That is a mistake.
The problem is not too many cooks. The problem is that you hired two people who were trained to answer different questions, and nobody told them which question wins on a Tuesday afternoon. A Design Manager looks at a feature and asks, “Can our team ship this without burning out?” A Lead Designer looks at the same feature and asks, “Does this actually fix the user’s pain?” Those are not competing answers. They are two halves of one decision, and you need a process that forces both halves to talk before anyone opens Figma.
We run design audits for early stage startups, and every single audit surfaces the same pattern. The founder says, “We have a design problem.” Then we discover they have a decision problem. The team has opinions, but no agreed upon order of operations. So the manager blocks a release because the team is overloaded, the lead blocks it because the flow is confusing, and the founder ends up mediating a fight that should have been settled by a simple rule: user impact first, team capacity second, pixel perfection third. That ordering is not obvious to anyone, and it is your job to make it explicit.
The founders who solve this do not promote one person over the other. They build a lightweight ritual. Every feature gets a one page brief that answers three questions in order. What problem are we solving for the user? What is the smallest version we can ship this week? What will we cut if the team gets stretched? That brief becomes the referee. When the manager and the lead disagree, they do not argue with each other. They argue with the brief.
What this means for founders
Stop treating design leadership like a hiring problem. You do not need a chief design officer, a head of design, or any other title that sounds impressive in a pitch deck. You need a decision framework that works before the ego kicks in. Write the three questions on a whiteboard. Make every designer answer them in writing before a project starts. If they cannot agree on the first question, they are not ready to build anything.
Second, schedule a weekly fifteen minute check in where the only agenda is, “What are we deprioritizing this week?” That forces the manager and the lead to make tradeoffs out loud, in front of you, instead of quietly resenting each other in Slack. You will be shocked how fast the tension dissolves when both people realize they are allowed to say, “We are not doing that this week” without it being a failure.
Third, and this is the one nobody wants to hear, you need to get comfortable being the referee for the first few months. Do not delegate this to another designer. Do not hire a consultant. You, the founder, are the only person in the room who genuinely does not care whether the button is 4 pixels wider. That neutrality is your superpower. Use it until the team internalizes the order of operations, then step back.
Key takeaways
- Write a one page brief for every feature that answers three questions in order: user problem, smallest shippable version, what gets cut if capacity dips.
- Make the brief the referee, not the seniority chart. Disagreements get resolved against the document, not against each other.
- Run a weekly fifteen minute meeting where the only agenda is what the team is explicitly not doing this week.
- Do not hire a chief design officer until you have shipped at least two products with the brief process. Titles do not fix confusion, process does.
This post builds on research originally published by A List Apart on August 11, 2026. We adapt established industry research into practical, first person guidance for founders.