Module 2 of 12 · 7 min read
The Role Shift: From Doing the Work to Building the Conditions for Great Work
What actually changes when you move from senior designer to UX lead: your output, your time, your relationships, and the traps to avoid.
Why it matters
The single most important change for a new lead is this: stop measuring your impact only by the design you produce directly. This is the hardest part of the transition. It's an identity change more than a skill change. Most first-time leads struggle not because they lack skills, but because they keep defaulting to the work that made them successful. Design was where you felt competent, so under pressure you go back to it, and the team waits.
1. Know which job you're doing
"UX Lead" means different things in different companies. Your role sits somewhere on this map. Clarifying where, with your manager or before you accept a role, is one of the most useful questions you can ask: "Which of these matters most in this role, and how will success be judged?"
| Role | Primary focus | Direct reports? | Typical scope |
|---|---|---|---|
| Senior / Staff Designer | Craft, complex problems | No | One product/domain |
| Principal Designer | Craft at org scale, design direction | No | Multiple products, design system, vision |
| Design / UX Lead (functional) | Quality, standards, coordinating designers, mentoring | Sometimes (dotted line) | Several squads/domains |
| Design Manager | People: hiring, growth, performance, team health | Yes | 4–10 designers |
| Head of / Director of UX | Org design, strategy, budget, executive partnership | Managers + ICs | Whole UX function |
| DesignOps Lead | Process, tools, capacity, operations | Sometimes | Whole UX function |
Many real lead roles are hybrids: for example Design Lead + DesignOps + part Manager, covering standards, capacity transparency, designer development and a cross-team vision. If your role is a hybrid, be ready to work on all of its parts, and ask which one matters most right now.
Merholz & Skinner's model (Org Design for Design Orgs): design leadership splits into practice (quality, craft, methods), people (hiring, growth) and operations (process, tools, resources). Senior leaders have to cover all three, often by building a team that does.
2. What changes
2.1 Your output
| Before | After |
|---|---|
| Screens, flows, prototypes | Decisions, priorities, clarity, a healthy team |
| Visible in your design files | Visible in docs, meetings, other people's work |
| Feedback loop: days | Feedback loop: months |
That long feedback loop is why new leads often feel unproductive. Keep a Leadership log (template in the Learning plan) so the impact becomes visible to you.
2.2 Your time
A rough healthy split for a hands-on UX lead with 4–8 designers:
| Activity | % time |
|---|---|
| People (1:1s, coaching, feedback, hiring) | 25–30% |
| Practice (critique, quality, standards, design system) | 20–25% |
| Strategy & stakeholders (roadmaps, alignment, priorities) | 20–25% |
| Operations (capacity, process, tools) | 10–15% |
| Hands-on design | 10–20% |
Warning sign: if you're doing more than ~30% hands-on design, you're probably under-investing in the team, or you're a principal designer with a lead title.
2.3 Your relationships
- Former peers become your reports or dependents. Be explicit about the change, and don't pretend nothing changed.
- Your manager becomes a partner in shaping the organisation, not only a reviewer of your work.
- Product managers and engineering leads become your peers. You negotiate with them as equals about priorities and quality.
2.4 Your definition of a good day
Old: "I solved a hard design problem." New: "A designer solved a hard problem I couldn't have solved alone, and knew why it mattered."
3. The traps of the first-time lead
| Trap | What it looks like | Antidote |
|---|---|---|
| Super-IC | You redesign other people's work at night | Critique the problem framing, not the pixels. Ask: "What were you optimising for?" |
| Bottleneck | Every decision waits for you | Write decision principles; delegate decision rights explicitly (see RACI/DACI in module 07) |
| Friend, not lead | You avoid hard feedback to stay liked | Kindness = clarity. See Radical Candor in module 04 |
| Process zealot | Rolling out standards before understanding the teams | Listen for 30 days first (see 30-60-90 plan) |
| Invisible lead | Great work, nobody outside UX knows | Weekly/monthly written updates; demo days |
| Absorbing everything | Shielding the team from all pressure until you burn out | Filter, don't absorb; share context and trade-offs openly |
| Losing the craft | Six months in, you can't credibly critique | Keep 10–20% hands-on, e.g. a design-system initiative or a hard problem |
4. Leadership without the title (start now)
You don't need the title to start behaving like a lead. Practise these in your current role over the next 4–8 weeks:
- Run a cross-team design critique (bi-weekly, 45 min). Invite designers from other teams or products.
- Write a one-page "State of UX" memo for your area: what's working, what isn't, what you'd change. Share it with your manager.
- Mentor a less experienced designer formally: 30 min every two weeks, with a shared development doc.
- Own one cross-team decision end-to-end, e.g. a component standard or analytics event naming, including the stakeholder alignment.
- Speak first once per meeting in one recurring cross-team meeting. See module 03.
Each of these also gives you a fresh, concrete story (STAR method) to share when you talk about your leadership.
5. Practice
Evidence to collect
Keep proof in your Leadership log:
- Your time split today, and again in three months.
- Your leadership identity statement.
- The outcome of the two "leadership without the title" actions you started.
Read / watch
See Library → Role transition: Julie Zhuo's The Making of a Manager, Merholz & Skinner's Org Design for Design Orgs, Michael Watkins' The First 90 Days, Camille Fournier's The Manager's Path (engineering, but it maps closely to design).
Talking about it
- With your manager: use the role table in §1 to agree what your role is. Ask: "Which of practice, people and operations should I prioritise in the next six months?" Agree on your target time split, so you aren't judged on design output you've deliberately reduced.
- With your former peers: name the change openly. "My role has changed, and I'll be doing less design and more of X. I still want to hear from you directly when something isn't working."
- With stakeholders: explain your new value in their terms: faster decisions, consistent quality across teams, visible capacity. Not "I'll be in more meetings".
- In a promotion or hiring conversation: show you understand the shift. Describe how you measure your impact now (other people's work, decisions, team health) and give one example where you chose to coach rather than do the work yourself.
Check yourself
Answer out loud, then open the section to compare.
- How is a lead's output different from a senior designer's? → answer
- Which first-time-lead trap are you most at risk of? → answer
- What leadership can you start this month, without the title? → answer
Connections
← Module 1: Self-Assessment · Learning path · Module 3: Personal Leadership Presence →
Related
- Module 4: People Leadership: delegation is the antidote to the super-IC trap
- Module 7: DesignOps, Team Models & Capacity: DACI to stop being the bottleneck
- Module 3: Personal Leadership Presence: proactivity, leading without the title
- 12-Month Learning Plan: the leadership log makes impact visible
- Module 11: Workshop Techniques: a ready-to-run cross-team critique agenda
Hubs: Frameworks index