Most of a company's design is decided in its first eighteen months, by people who would not describe themselves as designers, in conversations that nobody records.
I have been the founder making those decisions three times and the executive arriving afterwards four times, which is an unusual pair of vantage points and mostly a source of retrospective embarrassment. The thing I did not understand as a founder, and could not stop noticing as an executive, is that by the time a company hires someone to own design, the decisions that determine what the product feels like have already been taken and are load-bearing.
What founders actually decide
Not the visual language, which is the part everyone thinks of as design and the part most easily changed later. The decisions that stick are structural, and founders make all of them.
Who the customer is, when there are two plausible answers. At Honor we assumed our customer was the adult child arranging care for an aging parent, and when we went to market roughly half the people signing up each day were arranging care for themselves or for a spouse. Different person, different hardware, completely different emotional posture (we had built the entire onboarding for the wrong one). That is a design decision and it was made long before it was examined.
What the product refuses to require. We committed to Honor working as well over a landline as over a smartphone, which sounds like an accessibility footnote and is in fact the most constraining decision in the company's history. You cannot assume a screen, so the model of what is happening has to survive being spoken aloud, and that forces a clarity a user interface will happily let you avoid. Every downstream choice inherits it.
What the first ten customers are allowed to ask for. A founder saying yes to a specific enterprise buyer in month six writes a roadmap constraint that will still be visible in the product in year five.
None of these show up in a design review. All of them are design.
The first designer does not fix this
The standard move is to hire a designer to own design, with relief, at around fifteen or twenty people. It rarely works the way founders expect and the reason is not the designer.
Taste has already been encoded. It is in the onboarding flow the founder built in a weekend, in the pricing page they argued about, in the shape of the object model, in what the company thinks is embarrassing and what it thinks is fine. A new person can change the surface. They cannot change the encoded judgment without an argument with the founder, and that argument is exactly the one the hire was supposed to make unnecessary.
So the first designer is either given real authority over those structural decisions, which means the founder is now in a working relationship they thought they were buying their way out of, or they are handed the surface and slowly become a production function. The second outcome is far more common, and I think it is usually misdiagnosed as a hiring mistake.
The founder is going to do the design either way. The only open question is whether they do it deliberately.
What I look for now
I sit on the other side of this these days, running a small fund and a studio out of Amsterdam, and the founder-design question has become one of the more reliable things I can assess in a first meeting.
I am not looking for a founder with taste, exactly. Taste is pleasant and it is not predictive on its own, and plenty of tasteful founders build nothing. What I am looking for is whether the team can put something in front of a person this month.
When we founded Human, everybody on the founding team wrote code or pushed pixels, and I now think that was the clearest thing about us to the angels who wrote the first checks. Not because building it yourself is romantic, but because your story will change, your market will change, and your product will certainly change, and what an early investor is underwriting is how fast you can survive those changes.
The tell in a meeting is small. Ask what they shipped in the last two weeks (two weeks, not a quarter, because a quarter lets them answer with a plan). Founders who do this work themselves answer in specifics and often show you something on a phone. Founders who have outsourced their own product judgment answer with a plan.
The failure on the other side
I should be even-handed, because founder-led design has a characteristic failure and it is severe.
Founder taste never gets audited. The company grows, the founder's instinct keeps winning arguments on the strength of having been right in year one, and nobody can distinguish between the decisions that were correct and the decisions that were merely early. Everybody in the room learns to predict the founder rather than the customer, which is a much easier problem and produces a company that is excellent at pleasing one person.
The signature of it: a product with unusual coherence and a strange blind spot, always in the same place, always somewhere the founder does not personally go. This is where a design leader earns the job, and advocacy is the wrong tool for it. What works is a mechanism that lets an instinct be checked against something other than seniority: research the founder actually attends, and a habit of writing decisions down with the reasoning attached so a wrong one can be found later.
What I would tell a founder
Name the decisions that are design decisions and keep them: who the customer is when there are two plausible answers, what the product refuses to require, what it will never do, and what the first run of the thing feels like to someone who has no idea what they are looking at. That list is short, it is yours, and delegating it early is how companies end up with products nobody can describe.
Delegate everything else as fast as you can, and treat the first design hire as a partner in the short list rather than an owner of it. Be explicit that this is the arrangement, because the alternative is a competent person spending eight months discovering it by collision.
And write down why. Not for posterity. For the version of your company that is forty people, where somebody reasonable is going to ask why the landline decision exists, and the honest answer needs to be better than because the founder wanted it.
I've founded three companies, was part of the founding executive team at Honor leading product and brand from seed to Series C, and led design or product at Lyft, Grammarly and Pitch. Today I run Noord, an early-stage fund and studio in Amsterdam. The counter-argument: a good number of very large companies were built by founders with no design instinct at all and acquired the capability later at considerable expense, which suggests this is a strong advantage rather than a requirement. I think that is right, and I would still rather back the founder who can put the thing in front of someone this week.
© 2026 Renato Valdés-Olmos