The only designer at the company: real advice from real sessions
Based on 400+ anonymized mentorship sessions on ADPList.
Hundreds of solo designers (the first, only, or founding designer at their company) book ADPList sessions about it. We analyzed 400+ of those conversations, fully anonymized.
The most striking pattern: the mentors, mostly senior designers, don't coach purism. They coach survival tactics. The single most repeated advice is to stop selling the design process and start selling business outcomes.
What 400+ real sessions show
- The #1 advice pattern from mentors, by repetition: translate design into business outcomes. Don't advocate for “process.”
- In design-system sessions, mentors said start from an existing component library, almost never from scratch.
- ~1 in 6 sessions touches AI tools or AI career impact.
- Imposter syndrome, when raised, came almost exclusively from designers with no design peers.
- Around a third of sessions ended with a scheduled follow-up. Solo designers turn mentorship into an ongoing lifeline, not a one-off call.
- The “team of one” problem isn't design-specific: solo data engineers, QA engineers, and marketers bring the same challenges to sessions.
The questions people actually ask, and what mentors advise
How do I get buy-in for design when nobody at my company understands what I do?
The strongest consensus in these sessions: stop explaining UX and start speaking business. Tie every design argument to revenue, risk, or a metric leadership already tracks. Win small, visible battles before proposing process changes. Several mentors go further: practice UX without ever calling it UX.
How do I push back on a founder who dictates the design?
Build trust before you spend it. Understand what the founder is actually optimizing for, then present options with rationale instead of a single opinion. A recurring tactic: anticipate their feature ideas and bring next-version concepts proactively. It repositions design from obstacle to foresight. Pick battles deliberately; you won't win them all, and you shouldn't try.
How do I do user research with no budget and no access to users?
Do it scrappy and don't ask permission: analytics, support tickets, short surveys, hallway tests. Frame research as risk reduction, not ritual. If leadership gatekeeps user access, negotiate for partial access instead of fighting on principle.
Should I build a design system alone? Where do I start?
Mentors are near-unanimous: never from scratch. Start from an existing library and the components your engineers already use, wrap a minimal system around them, and add tokens and documentation incrementally. Align it with the engineering roadmap. A design system nobody adopts is a portfolio piece, not a system.
How do I manage the workload of being three roles at once?
Set boundaries that depend on your own actions, not on other people's goodwill. Triage requests by how much design they actually need, run a visible queue, batch interruptions into office hours, and ship the quick version now with the better version explicitly scheduled.
How do I keep growing with no design peers and no senior above me?
Get your feedback loop outside the building: external mentors, design communities, benchmarking against strong products, and self-critique against defined metrics. And mentors are honest about the ceiling: if growth stalls, the real answer may be moving to a company with a design team.
How do I convince my company to hire a second designer?
Don't argue that you're drowning; overwhelm is a personal complaint. Argue single point of failure: the company has a bus-factor problem, backed by weeks of workload and turnaround data. Mentors are blunt that “I'm overwhelmed” alone never wins headcount.
Is being a solo designer good or bad for my career?
The one question where mentors genuinely split. One camp: solo roles are compressed senior-level training, with ownership, ambiguity, and breadth you can't get on a big team. The other: without seniors around you accrue invisible skill debt and should get out. Both camps agree on the mechanics: set a decision timeline, document your wins, and don't drift.
How do I show impact in my portfolio when I was the only designer?
Story over screens: lead with the outcome, quantify what you can, and build case studies around constraints and decisions rather than a full process replay. Solo breadth is a selling point. Ownership and ambiguity tolerance are exactly what hiring managers screen for.
How do I work with engineers who resist my designs?
Involve them before the design is “done”; journey-mapping workshops are the recurring tool. Standardize specs and edge cases, prefer live feedback over async tickets, and learn enough of the stack to design within its constraints instead of against them.
Should I be worried about AI as a solo designer?
The advice is uniformly “adopt, don't fear”: use AI to accelerate briefs, research synthesis, and prototyping, and treat AI fluency as a differentiator in hiring. Your defensible ground is judgment, research, and domain expertise, the things a team of one exercises daily.
How do I estimate design timelines when every deadline is unrealistic?
Time-box by percentage allocation across projects, phase work into must-have and nice-to-have, communicate constraints before the deadline instead of at it, and treat every estimation miss as data for the next negotiation.
Talk it through with a mentor, free
Every insight on this page came from real mentorship conversations. Book your own free 1:1 session with a mentor who has been where you are. No fees, no premium tiers, no paywalls.
Find your mentor →About this data
This page is based on 400+ mentorship sessions held on ADPList between April 2025 and August 2026. Sessions were anonymized and analyzed in aggregate; everything above reflects patterns repeated across many independent mentors, and no individual session, person, or company is quoted or identifiable.