You are an early-stage founder. You have a brilliant product, but your user interface looks like it was designed by a sleep-deprived engineer at 3 AM. You know you need a designer. But you have no idea how to hire one. You are terrified of being sold a bill of goods by some “creative” who speaks in abstract terms and wears expensive sneakers.
So, what do you do? Most founders do one of two things: they either panic and hire an expensive agency, or they freeze and wait for a magical “design leader” to appear and make all their aesthetic dreams come true.
Both of these choices are a surrender. You are outsourcing your judgment because you think you don’t have any.
Here is the twist: your lack of design expertise isn’t a weakness. It is the exact tool you need to make a better hire than someone who has spent twenty years developing a subjective, elitist taste for typography.
When you can’t judge art, you are forced to judge engineering. And engineering is what actually builds products. I recently read an account from a startup team that started with absolutely zero design expertise. Over two years, they didn’t rely on a design guru. They built a system, evaluated over 300 portfolios, and systematically hired their team.
They didn’t look for the prettiest Dribbble shots. They looked for process. They looked for problem-solving.
A designer who clearly explains their bad decisions is infinitely more valuable than a designer who stays silent about their beautiful pixels.
When you review a portfolio, stop asking, “Do I like this?” That question leads you astray. It makes you hire decorators instead of builders. Instead, ask: “What problem were they trying to solve? What constraints were they under? How did they measure success?”
Look at their case studies. Are they walking you through their thought process? Are they showing you the ugly wireframes that led to the final design? Or are they just dropping a polished hero shot and expecting you to be impressed?
If a designer can’t articulate the “why” behind their work, they aren’t a problem-solver. They are a pixel-pusher. And early-stage startups don’t survive on pixel-pushing.
Taste is a luxury you can’t quantify. Process is a weapon you can master.
So stop waiting for a design leader to hold your hand. Stop being intimidated by a discipline you don’t fully understand. Turn your ignorance into an objective framework. Review portfolios at scale. Demand logic over aesthetics. Hire the person who solves problems, and build the product your users actually need.
FAQ
Q: If I don't know good design, how do I avoid hiring a mediocre designer?
A: Stop evaluating the final visual output and start evaluating their case studies. A good designer will explain the constraints, the problem, and the logic behind their decisions. If they only show pretty pictures without context, pass.
Q: What's the practical implication of this approach?
A: You can scale your hiring process. Instead of relying on gut feeling or a rare design leader, you can review hundreds of portfolios quickly by filtering for problem-solving frameworks rather than aesthetic preferences.
Q: Isn't aesthetic taste important for a designer?
A: It matters eventually, but not at the early stage. Early on, you need someone who can translate complex user problems into functional interfaces. Polish is easy to add later; a broken product logic is fatal from day one.