Sofia Marchetti
UX Director
Early-stage founders routinely underinvest in design and then overcorrect by hiring for aesthetics rather than for thinking. This piece explains what design actually is, why it matters most before the product is built rather than after, and what to look for when you are hiring your first designer.
What Founders Get Wrong About Product Design
Most early-stage founders approach design as a problem of aesthetics. They want their product to look good. What they actually need is for their product to work — for users to understand it immediately, accomplish their goals without friction, and feel confident enough in the experience to trust the product with their time, money, or data.
Looking good is, at best, a by-product of working well. At worst, it is a distraction from it.
The Clarity Problem
The most common UX failure in early-stage products is not ugliness — it is confusion. Products built by people who are very close to the problem they are solving often assume too much prior knowledge from users who are encountering the product for the first time. Every screen that requires explanation has failed at design before a single user arrives.
The test we use with founder clients is ruthlessly simple: can a person who has never heard of your product complete the core task within three minutes without any guidance? If the answer is no, the design work has not yet started.
Why Founders Resist This
Founders resist simplification for understandable reasons. They have built something complex and they are proud of its complexity. They want users to understand the depth of what they have created. They worry that simplifying the interface will communicate a simpler product.
The opposite is true. The hardest design problem — the one that requires the most sophistication — is reducing something complex to its essential expression. A product that communicates a complex capability through a simple interface is not hiding its intelligence. It is demonstrating it.
Design as Competitive Advantage
The companies that have built lasting advantages through design — not just visual design but the full experience of using the product — are the ones where design had a seat at the product decision table, not just at the aesthetic review. When design is only called in to make things look good after the product decisions have been made, you get products that look polished and feel confusing.
Design is most valuable as a thinking tool before it is a making tool. The question "how would a user understand this?" should be in the room when product decisions are being made, not applied to the outcomes after the fact.
What to Do Instead
Hire a designer who asks uncomfortable questions. Not the ones who show you beautiful screens in the first week, but the ones who want to spend the first week understanding your users before they open a design tool. The deliverable you need is not a polished mockup — it is clarity about what the product actually is and who it is actually for. Everything else follows from that.
The best design work we do with early-stage clients is the work that makes them feel like we have simplified their vision. We have not. We have found the clearest possible expression of what was already there.
