First designer to Head of Design: owning product, brand and the team end to end
I’ve been the first designer more than once, and I’ve grown a design team from a handful of people into a team that ran product, brand and marketing for a company going from Series B to unicorn. The two jobs look different on an org chart. In practice they’re the same job at different zoom levels: setting the defaults everyone else inherits, then deciding where your own hands still need to be.
Today I’m Head of Design at Cognichip, where I joined at seed as the first designer and own product, brand and the design system from zero to one. Cognichip is building Artificial Chip Intelligence (ACI®), a physics-informed foundation model for chip design, and announced a $60M Series A led by Seligman Ventures, with Intel CEO Lip-Bu Tan joining the board. Before that I spent eight years at Plume (2016–2024), leading brand and then design, and was Head of Design from 2021 to 2024. Earlier still, I worked on 0→1 products at a software and product agency.
Day one: the decisions nobody else will make
The first designer at a startup inherits a strange kind of authority. Nobody tells you what to do, because nobody else is thinking about it. That means the most important early decisions are the ones that will happen by default if you don’t make them:
- Identity. The logo, voice and visual language will exist either way. If no one designs them, they’ll be whatever the first pitch deck happened to look like.
- The system. The first ten screens set the component patterns for the next thousand. Choosing early to build atomic parts, and to share them across product and marketing, saves a rebuild later.
- Research cadence. If talking to users isn’t scheduled in the first month, it quietly becomes something you’ll do "after launch."
- How decisions get recorded. A lightweight habit of writing down what was decided and why pays off the first time someone new asks.
At Cognichip, the first public deliverables were the logo and website for launch, followed by the product itself: chat and agentic interfaces for chip design work, built from scratch. Identity and product came out of one design engine from the start, which is far easier than merging them later.
0→1 patterns that keep repeating
Before Plume, I spent a few years designing new products at an agency, where each project was a small company in itself. A few of them show the patterns well:
- Handle was a product for turning email into tasks. I owned product design across web and mobile, and the team placed second at TechCrunch Disrupt. The lesson: a sharp product posture (collapse the inbox into the next action) matters more than feature count.
- Meow let diners skip a restaurant waitlist by bidding. Logo, identity, UX and research all came from the same small team. The pun did half the onboarding. Taste is a product decision.
- Boxbee was on-demand storage by the box. The bright yellow box was both the brand and the interface. When the physical thing and the digital thing share an identity, explanation gets easier.
- Sparrow Dock, an origami-inspired MacBook workstation, was released for crowdfunding with identity, product story and launch creative designed as one voice, on a deadline that didn’t move.
The common thread is end-to-end ownership. In 0→1 work, the seams between brand, product and marketing are where young companies lose coherence, and a first designer is often the only person positioned to see all of them.
Player-coach: designing beside the team
At Plume, the shape of the team changed several times. Early on the product team was five or six people. For years before we scaled, two or three internal designers, with agencies as needed, designed all of product, brand and marketing. In the later years I led about nine designers, with freelancers and agencies alongside, spanning the consumer app, the service-provider dashboards, email and brand.
Through all of it, I stayed a player-coach. In the small-team years that meant designing a large share of the work myself. In the larger-team years it meant fewer pixels and more defaults: reviewing, setting the bar, and sitting down to help wherever the work was stuck. I don’t think a Head of Design at a growth-stage startup should ever fully stop making things. You lose your sense of where the work is hard.
Scaling from Series B: process, and when it slows you down
Growth adds people, and people add coordination cost. The temptation is to add process everywhere. My rule: add process where mistakes are expensive and recurring, and nowhere else.
Good early candidates:
- A shared design system with clear ownership.
- A review rhythm that looks at early drafts, not just finished work.
- A written brief for anything that touches more than one team.
Things I’d delay as long as possible: heavy intake forms, approval chains for small changes, and status rituals that report on work instead of unblocking it. I wrote about what I’d do differently through that growth phase in What I’d Build Earlier.
Partnering with Product and Engineering as an equal
A first designer who waits for requirements becomes a production resource. The job is to shape the problem with Product and Engineering, not to decorate the answer.
In practice that means bringing evidence (research, support signal, prototypes) to planning, being fluent in technical constraints, and treating engineering constraints as design material. It also means being willing to let your idea become Plan B when someone else’s is better. Equal partnership is earned by being useful in the room, not by title.
What I’d tell a founder hiring a first designer
- Hire for range and judgment, not a portfolio of one style. Your first designer will touch brand, product, marketing and probably the pitch deck.
- Give them the seams. Make it explicit that brand and product consistency is their problem.
- Expect them to build. Today a strong first designer prototypes in real code and uses AI tools daily. Ask to see something that shipped.
- Decide early when to hire the second designer. Usually it’s when the first one stops having time to talk to users.
- Let them stay hands-on as they grow. The best Heads of Design I know still make things.
The first designer’s real output isn’t screens. It’s the defaults everyone builds on for years. Make them deliberately.
Related Product discovery with AI: synthesis that keeps the quote attachedThe Spreadsheet That Tells You What to Test NextPapercuts, Tech Debt and Stalled Features: How Design Teams Ratchet Quality Forward