What should I look for in a designer’s portfolio if I’m a non-design founder?
Non-design founders should look beyond polished screens in design portfolios. Focus on case studies, problem-solving, and communication skills. This guide highlights what truly matters and the red flags to watch for when evaluating designers.
·
Founder series
Most non-design founders don’t evaluate designer portfolios effectively. They look at the screens and ask: “Does this look good?”
That’s understandable. However, this is almost entirely the wrong question. Here’s what to look for instead.
Process over polish
A beautiful portfolio of finished screens shows that a designer can produce polished work. However, it offers little insight into whether they can help a founder with an unclear brief, a constrained timeline, and a product that does not yet exist.
What you actually want to understand is how a designer thinks. How do they move from a fuzzy problem to a clear solution? What questions do they ask before they start? How do they handle a direction that isn’t working?
This is why case studies are more valuable than screenshots. A portfolio that walks you through a problem, describing the challenge, the approaches tried, the lessons learned, and the final outcome, provides far more insight than a gallery of polished final screens with no context.
When you review a portfolio, focus on the designer’s thinking, not just the output.
Look for evidence of ambiguity
For early-stage work specifically, you want a designer who has operated under conditions similar to yours: unclear requirements, limited resources, tight timelines, shifting priorities.
Look for case studies that describe a messy starting point. A designer who explains, “We started without knowing exactly what we were building,” demonstrates the ability to navigate the unknown. In contrast, a designer who only describes executing a handed-down brief is showing they can follow instructions.
Ask directly: what’s the most ambiguous project you’ve worked on, and how did you approach it? The quality of that answer will tell you more than the portfolio itself.
The education instinct
One of the most underrated qualities in a designer, especially for founders who are new to working with design, is the ability to explain what they are doing and why.
Design involves constant trade-offs. For example, one approach might be faster but less scalable, or an interface might be cleaner but hide functionality. A flow could reduce friction for new users but confuse experienced ones. A good designer does not make these calls quietly. They bring the trade-offs to light, explain the options, and help you make informed decisions about your product.
This skill is a combination of craft and communication style. Look for it in how designers describe their past work. Do they explain their reasoning, or simply show the outcome? Do they discuss what they decided and why, or only what they made?
A designer who educates as they go can be a force multiplier for a non-design founder. If a designer does not provide this guidance, you may end up relying on work that you do not fully understand.
Red flags to watch for
Even in a visually impressive portfolio, watch for these warning signs:
No case studies, only screens. In this case, you are seeing only the output rather than the thinking behind it.
Vague process descriptions, such as “I conducted user research and iterated on designs,” are template language and do not provide real insight.
No mention of constraints. Real projects have budgets, timelines, and technical limits. If a portfolio does not acknowledge any of these, it likely was not created in a real-world environment.
No examples of collaboration. Design does not happen in isolation. A portfolio with no mention of engineers, stakeholders, or founders may be a red flag.
Everything looks perfect. Real product design involves dead ends, pivots, and compromises. A portfolio with no signs of struggle or change is probably curated to hide the actual process.
The conversation matters as much as the portfolio
Portfolio review is only the first step. The way a designer discusses their work in conversation is equally revealing.
Do they ask questions about your product before pitching their approach? Do they talk about your users and your business goals, or mainly about their process and tools? Can they explain a complex design decision in plain language, without jargon?
A designer who listens before proposing and explains their thinking clearly is especially valuable when requirements are unclear and the stakes are high.