Being the solo designer at a startup sounds glamorous for about a week. You own the whole product. Every screen is yours. Then Monday arrives with a pitch deck due, a broken onboarding flow, three feature requests, a landing page and a developer waiting on specs, all at once.
Nobody hands you a process. Nobody reviews your work except people who don't design. And the backlog is always longer than the week.
I've seen this role from inside fast teams, and I think it's one of the best ways to grow as a designer, if you treat it as a job with its own skills rather than "normal design, but more of it". Here's what those skills are.
What a solo designer at a startup actually does
The job description says "product designer". The real job is closer to five roles in a trench coat.
| Hat | What it looks like day to day | How much time to give it |
|---|---|---|
| Product designer | Flows, wireframes, UI for features | The core, protect most of your week for it |
| Researcher | Talking to users, reading reviews, quick tests | Small but regular, every week |
| Design system owner | Components, styles, keeping things consistent | A little, often |
| Brand and marketing | Landing pages, decks, social assets | Time-box it, or it eats everything |
| Facilitator | Running reviews, aligning founders and developers | Short, structured sessions |
You won't do all of these well at the same time. The skill is knowing which hat matters this week.
"Solo" rarely means alone. You'll work with founders, developers, maybe a product manager. What's missing is another designer to argue with, and that changes how you get feedback.
Prioritise ruthlessly (the real core skill)
When everything is urgent, the loudest request wins by default. That's how solo designers end up polishing a marketing banner while the sign-up flow leaks users.
A simple filter I'd use: for every request, ask two questions.
- Does this affect a core task for users, or a key business number?
- Is it blocking someone right now?
Yes to both goes first. Yes to the first only gets scheduled. Neither goes on a "later" list that you review every couple of weeks. Most of it quietly stops mattering.
Make this visible. A shared board where founders can see what you're working on, and what's waiting, ends a lot of "is my thing done yet?" messages. It also turns priority arguments into a conversation the team has, rather than a decision you make alone and get blamed for.
Build just enough process
Big companies have design ops, critique rituals and research teams. You have a Figma file and a Slack channel. You still need process, just much lighter.
A one-page brief for anything bigger than a tweak
Before you design, write down: the problem, who has it, what success looks like and any constraints. Ten minutes. It saves days of redesign when a founder's mental picture turns out to be different from yours.
A tiny design system
Start with colours, type, spacing and the five or six components you use everywhere: buttons, inputs, cards, list items, navigation, modals. Don't build a library for a product that will change shape next month. My post on design systems for small teams covers how small to start.
A predictable handoff
Developers shouldn't have to hunt for specs. Name frames clearly, mark what's ready, include states (empty, loading, error) and keep one source of truth. A developer handoff checklist is worth having even if you're the only one using it.
Tip
Keep a "decisions" page in your Figma file: one line per decision, the date and why. Three months later, when someone asks why the button moved, you'll have an answer instead of a shrug.
Keep research alive without a research team
The biggest risk for a solo designer isn't bad UI. It's designing from assumptions because there's no time to check them.
Small, steady research beats a big study you never get round to:
- Read app store reviews and support messages every week.
- Sit in on sales or support calls when you can.
- Run a quick test with three to five people before a big feature ships.
- Ask founders for access to user communities, chats or groups.
From my work
On Pukaar.ai, much of the early insight came from a WhatsApp community of parents asking real 2 a.m. questions, along with more than 70 user interviews. A community channel like that is cheap, always on, and tells you what people actually worry about.
You don't need a lab. You need a habit.
Work with founders, not for them
Founders at early startups usually have strong product opinions, and often they're right. They've spent more time with customers than anyone. Your job isn't to win arguments. It's to make sure decisions are based on users, not just taste, including your own.
A few habits help:
- Show options early and rough. A sketch invites honest input; a polished screen invites nitpicking.
- Tie every design choice to a problem. "This reduces steps for first-time users" lands better than "this looks cleaner".
- Disagree with evidence, then commit. If you lose a call, ship it well and measure it.
How you present work matters a lot here, so I wrote a separate guide on presenting design to stakeholders.
Watch out
Saying yes to everything feels helpful but makes you the bottleneck and the scapegoat. A clear "yes, after X" is kinder to everyone than a silent pile-up.
Grow and stay sane
With no design manager, your growth is your responsibility. And with no one else sharing the load, burnout comes faster than you'd expect.
- Set two or three skills you want to improve this year and pick projects that stretch them
- Find designers outside the company for feedback: a community, a mentor, old classmates
- Document your work as you go, so case studies are easy later
- Block focus time in your calendar and defend it
- Take real breaks between big launches, not just after them
Using AI tools for first drafts of copy, research summaries and quick prototypes can also free up hours, as long as they don't replace the actual thinking.
FAQ
What does a solo designer at a startup do?
They own the whole design function: product UI, user research, the design system, often brand and marketing work, and the relationship with founders and developers. The real skill is choosing which of these matters most each week. Doing all of them at full depth at once isn't realistic.
Is being the only designer at a startup good for a junior designer?
It can be, if there's some support. You'll learn fast and own real outcomes, but without senior feedback you may build bad habits. If you take a role like this early on, find mentors outside the company and ask for honest reviews often.
How do I prioritise design requests at a startup?
Ask whether a request affects a core user task or business number, and whether it's blocking someone right now. Do the ones that hit both first, schedule the rest, and keep a visible board so the team sees the trade-offs. That turns priority into a team decision.
Key takeaways
- The solo designer role is several jobs at once; pick which hat matters each week.
- Prioritise by user and business impact, and make the queue visible to the team.
- Use light process: one-page briefs, a tiny design system and predictable handoffs.
- Keep research small and steady, through reviews, communities and quick tests.
- Own your growth and protect your energy, because nobody else will.
What to do next
If you're starting as a startup's first designer, begin with a list of every request on your plate and run it through the two-question filter. The quiet clarity that follows is worth a lot. If you're a founder looking for design help on a fast-moving product, tell me about your project and let's see if I can help.