Table of Contents
- Better questions. Bigger career.
- The right questions that change your UX career
- 1. Why am I doing design?
- 2. What's holding me back?
- 3. What are my non-negotiables?
- 4. What does success mean to me?
- 5. Who am I trying to please, and why?
- 6. When have I been the most fulfilled?
- 7. How meaningful is my current journey?
- Two frameworks for UX career growth
- Framework #1: Career How Might We's (asking the right questions)
- Traditional vs. Career HMW examples:
- How to apply Career HMWs:
- Framework #2: Hacking Career Growth (identify opportunities)
- The three pillars of compound career growth:
- 1. Skills that stack
- 2. Relationships that compound
- 3. Reputation that scales
- The uncomfortable truth about design career advice
- Growth isn't about getting ahead; it's about getting clear
Better questions. Bigger career.

- Asking better career questions (not "How do I get promoted?")
- Building compound growth (skills, relationships, and reputation that multiply over time)
The right questions that change your UX career

1. Why am I doing design?
- Is this a stepping stone to something else?
- Are you energized by making products more usable?
- Do you genuinely enjoy user research, iteration, and the messiness of the process?
- Did you get into UX because you love solving problems or because someone told you designers make good money?
2. What's holding me back?
- Do you struggle to sell your ideas to non-designers?
- Are you avoiding tough conversations with stakeholders?
- Are you waiting for permission instead of taking initiative?
- Do you second-guess yourself instead of trusting your expertise?
3. What are my non-negotiables?
- Remote work vs. in-person collaboration?
- Work-life balance vs. high-growth startup intensity?
- Creative autonomy vs. clear direction and structure?
4. What does success mean to me?
- Running your own consultancy?
- Is it building products millions use daily?
- Working 30 hours a week and traveling often?
5. Who am I trying to please, and why?
- Are you designing for users or for design awards?
- Are you optimizing for peer approval or business impact?
- Are you choosing projects for learning or for your resume?
6. When have I been the most fulfilled?
- Do you thrive when building new things or optimizing existing ones?
- Are you energized by solo deep work or collaborative brainstorming?
- Do you prefer ambiguous, open-ended challenges or structured, clear problems?
7. How meaningful is my current journey?
- Are you proud of the problems you’re solving?
- Do you believe in the product you’re building?
- Are you learning skills that will matter in five years?
Two frameworks for UX career growth
Framework #1: Career How Might We's (asking the right questions)

Traditional vs. Career HMW examples:
- Moves you from reactive to proactive positioning
- Focus shifts from seeking attention to creating impact
- Changes the dynamic from begging for recognition to earning it
- Identifies actual skill gaps rather than trendy tools
- Focuses on unique value creation vs. checkbox learning
- Makes you think strategically about differentiation
- Flips the script from taking value to creating value
- Makes you focus on what you bring to relationships
- Shifts from transactional to transformational networking
- Shows initiative rather than entitlement
- Builds the skills needed for the next level
- Demonstrates leadership potential through action
- Connects design work to business impact
- Focuses on outcomes rather than just process
- Helps you think beyond aesthetics to strategy
How to apply Career HMWs:
- Step 1: Write down a limiting career question you're asking
- Step 2: Identify what assumption is built into that question
- Step 3: Reframe it as "How might I..." focusing on what you can control
- Step 4: Brainstorm multiple approaches to that reframed question
- Step 5: Pick one approach to experiment with this week
Framework #2: Hacking Career Growth (identify opportunities)

The three pillars of compound career growth:
1. Skills that stack
- Design + Data analysis = Product intuition that's backed by evidence
- You can validate design decisions with user behavior data
- You speak the language of product managers and executives
- Your recommendations carry more weight because they're measurable
- UX + Business strategy = Designs that move company metrics
- You can translate user needs into business opportunities
- You understand how design decisions impact revenue and growth
- You can prioritize features based on business impact, not just user feedback
- Design + Writing = The ability to sell your ideas through documentation
- Your ideas spread because they're well-articulated
- You can create compelling design rationales that get buy-in
- You can communicate complex concepts to non-designers clearly
- UX + Psychology = Deep understanding of user motivation and behavior
- You become the user advocate that executives trust
- You can predict user behavior patterns before testing
- Your research insights go deeper than surface-level feedback
2. Relationships that compound
- Cross-functional partnerships:
- Teach engineers about design system thinking
- Help your PM understand user research methodologies
- Show data analysts how to make insights more actionable
- Mentorship (both directions):
- Document and share your mentorship learnings
- Mentor junior designers to build your teaching skills
- Find mentors in adjacent disciplines (product, engineering, business)
- Knowledge sharing:
- Share failure stories and lessons learned
- Run internal workshops on design topics
- Create documentation that makes others' jobs easier
- Long-term relationship building:
- The startup colleague you support becomes a hiring manager at a unicorn
- The junior developer you mentor becomes a senior engineer who champions design
- The designer who helps their PM today becomes an advocate when that PM becomes a Director
3. Reputation that scales
- The clarity creator:
- Known for asking the right questions that others miss
- Creates frameworks that help teams think more clearly
- Simplifies complex technical concepts for stakeholders
- The velocity driver:
- Balances speed with quality consistently
- Eliminates unnecessary process and friction
- Ships products faster than anyone thought possible
- The bridge builder:
- Creates alignment between design, product, and engineering
- Translates business requirements into user-centered solutions
- Makes complex technical concepts understandable to executives
- The system architect:
- Creates processes that improve team efficiency long-term
- Establishes design standards that maintain quality at scale
- Thinks in systems and frameworks, not just individual features
The uncomfortable truth about design career advice

Growth isn't about getting ahead; it's about getting clear
