Module 4 of 12 · 10 min read
People Leadership
The core methods for leading designers: 1:1s, feedback, coaching, delegation, career growth, psychological safety, hard conversations and hiring.
Why it matters
For many new leads, people leadership is the biggest gap on paper. You may have mentored informally, but never run regular 1:1s, given formal corrective feedback, or supported someone through a performance problem. It is also the area the people around you will test first: "How do you support a struggling designer? How do you give feedback? How do you avoid micromanaging?" You need concrete methods, not values alone.
It connects directly to Growth and learning, one pillar of the course's example practice model: a UX practice only grows as fast as its designers do.
Good news: people leadership is learnable and procedural. The tools below are used by managers everywhere.
Common pitfalls
- Turning 1:1s into status updates.
- Holding back corrective feedback to stay liked (ruinous empathy).
- Giving answers when a question would grow the person more.
- Delegating a task, then taking it back at the first wobble.
- Waiting too long on underperformance, until it becomes a crisis.
1. The 1:1: your most important ritual
Purpose: it's their meeting, not a status update. It builds trust, surfaces problems early and drives growth.
Cadence: weekly or bi-weekly, 30 min. Never cancel; reschedule if you must.
Structure (shared running doc per person):
## YYYY-MM-DD
**Their topics** (they fill first)
-
**My topics**
-
**Growth** (monthly): progress on development goals
**Feedback** (both directions)
**Actions**
- [ ] who / what / when
Good 1:1 questions
- What's on your mind this week?
- What's the most frustrating part of your work right now?
- Where are you stuck, and what would unblock you?
- What's something you're proud of from the last two weeks?
- Is there anything I could do differently to support you?
- What are you learning? What do you want to learn?
- On a scale of 1–10, how is your energy? What would make it +1?
Distributed teams (designers in different offices or countries): cameras on, written agendas, and timezone fairness. Rotate meeting slots if people are in different time zones.
2. Feedback
2.1 SBI — Situation, Behaviour, Impact (Center for Creative Leadership)
Situation: "In yesterday's review with the product manager…" Behaviour: "…you presented three options without a recommendation…" Impact: "…and the product manager chose the cheapest one, which drops the bulk-edit flow users need." + Invite: "What was your thinking? How could we approach the next one?"
Use it for praise too. Specific praise teaches more than "great job":
"In the critique (S), you asked the dev about edge cases before showing the design (B). It saved us a full iteration (I)."
2.2 Radical Candor (Kim Scott)
Two axes: Care personally × Challenge directly.
| Low challenge | High challenge | |
|---|---|---|
| High care | Ruinous empathy | Radical candor |
| Low care | Manipulative insincerity | Obnoxious aggression |
If you are empathetic and tend to avoid conflict (a very common profile among designers), you are most at risk of ruinous empathy: being so kind you don't say the hard thing. Remember: withholding feedback is a disservice to the person.
2.3 Feedback hygiene
- Praise in public, correct in private.
- Feedback close to the event (within days).
- Behaviour, not personality ("the deck had no recommendation", not "you're indecisive").
- Ratio: aim for more positive than corrective, but don't sandwich. Sandwiches hide the message.
- Ask for feedback on yourself first. It models the behaviour.
2.4 Design critique is feedback too
- Critique against goals and principles, not taste: "Does this help the operator find exceptions faster?"
- Separate critique (improve the work) from review/approval (decide).
- Roles: the presenter states the goal and what feedback they want; the facilitator keeps time; everyone else asks questions before suggesting.
- See NN/g's articles on design critiques in the Library.
3. Coaching — ask, don't tell
GROW model
| Step | Question |
|---|---|
| Goal | What do you want to achieve? What does good look like? |
| Reality | What's happening now? What have you tried? |
| Options | What could you do? What else? (ask "what else?" at least twice) |
| Will / Way forward | What will you do? By when? How will I know? |
The Coaching Habit: 7 questions (Michael Bungay Stanier)
- What's on your mind?
- And what else?
- What's the real challenge here for you?
- What do you want?
- How can I help?
- If you're saying yes to this, what are you saying no to?
- What was most useful for you?
Rule of thumb: junior designers need more telling/teaching; seniors need more coaching/asking. Match your style to the person's competence and confidence on this specific task (the Situational Leadership idea).
| Their state on this task | Your style |
|---|---|
| New & enthusiastic | Direct: clear instructions, examples |
| Some skill, low confidence | Coach: explain why, encourage, review together |
| Skilled, variable confidence | Support: ask, listen, back their decisions |
| Skilled & confident | Delegate: give the outcome, stay available |
4. Delegation without micromanagement
Delegate outcomes, not tasks
"Make the filter panel blue and move it left." "Operators miss exceptions in the order list. We need to reduce time-to-find. You own the solution; let's check in Thursday on direction."
Levels of delegation (pick one explicitly)
- Look into it and report back. I'll decide.
- Recommend options. I'll decide.
- Decide, but tell me before acting.
- Decide and act, then tell me.
- Decide and act. No need to tell me.
Saying the level out loud removes most micromanagement tension.
Check-in design
- Agree on checkpoints upfront ("direction review Thursday, pre-handoff review next Wednesday").
- At checkpoints, ask "what are you worried about?" before giving your opinion.
- Only intervene on the work if it threatens user outcome, deadline or standards, and say which one.
5. Career growth & development
Career ladders
Make expectations explicit with a career framework: levels (Junior → Mid → Senior → Staff/Principal / Lead) × dimensions (craft, collaboration, impact, leadership).
- If your organisation has one: learn it deeply and use it in every growth conversation.
- If not: building one is a high-value initiative for a growth and learning pillar. Start from public ladders (see Library → Career frameworks).
Individual development plan (IDP) per designer
Designer: ___ Level: ___ Next level target: ___
Strengths (with evidence):
Growth areas (from ladder):
1. Goal — Action — Support needed — Evidence of done — Date
2. …
Stretch opportunity this quarter:
Growth levers you control as a lead
- Stretch assignments. Give someone a cross-team problem.
- Visibility. Let them present to stakeholders, not you.
- Learning budget/time. Courses, conferences, reading time.
- Mentoring pairs. Senior-junior across teams (this connects teams too).
- Sponsorship. Mention their name in rooms they're not in.
6. Psychological safety & team health
Amy Edmondson's research (and Google's Project Aristotle) found psychological safety, people feeling safe to take interpersonal risks, to be the strongest predictor of team effectiveness.
How a lead builds it
- Frame work as learning problems, not execution problems.
- Admit your own fallibility: "I might be missing something, what do you see?"
- Respond productively to bad news. Thank the messenger.
- Make mistakes discussable through retros and "what we learned" posts.
- Ensure quiet voices get space: round-robin, written input before discussion.
Team health check (quarterly, anonymous, 1–5)
- I understand what's expected of me.
- I can raise problems and tough issues.
- I get useful feedback on my work.
- I'm learning and growing.
- My workload is sustainable.
- I feel connected to designers in other teams.
Question 6 matters most when your designers are spread across product teams and rarely work together, which is common in organisations with embedded designers.
7. Hard conversations
Underperformance — a humane process
- Clarify expectations. Were they ever explicit? (Often, no. That's on you.)
- Diagnose. Is it skill, will, context or something personal?
- Talk early with SBI and listen.
- Agree on a plan with clear goals and dates, plus support.
- Follow up regularly and document.
- Escalate with HR if no progress. Involve your manager early.
Crucial Conversations (Patterson et al.) toolkit
- Start with heart: what do I really want, for me, them and the relationship?
- Make it safe: restore mutual purpose and respect when emotions rise.
- STATE your path: Share facts → Tell your story → Ask for theirs → Talk tentatively → Encourage testing.
Conflict between designers / with a product manager
- Separate positions (what they ask) from interests (why).
- Bring it back to user evidence and principles.
- Decide who decides (DACI), then disagree and commit.
8. Hiring & onboarding (even if not in scope initially)
- Write a scorecard before reading CVs: outcomes for the role, competencies, culture contribution.
- Use a structured interview: same questions, rubric-scored, more than one interviewer.
- Portfolio review: ask about decisions and trade-offs, not only visuals.
- Onboarding plan for new designers: buddy, 30-60-90 goals, domain immersion, design-system training. Any training you already run (e.g. design-tool or design-system workshops) can become a ready-made onboarding module.
9. Practice
Do these in your current role, whether or not you have direct reports yet:
Evidence to collect
Keep proof in your Leadership log:
- A mentoring doc (anonymised) showing someone's growth.
- An example where you gave hard feedback and what changed.
- An example of delegation that worked, or one that didn't and what you learned.
Read / watch
Library → People leadership: Radical Candor, The Coaching Habit, Resilient Management (Lara Hogan), Crucial Conversations, The Making of a Manager, Amy Edmondson's The Fearless Organization and her TED talk.
Talking about it
People will ask how you lead people long before they see you do it. Answer with methods and examples, not values.
- With your manager: agree what "good" looks like for your people work. "I'll run bi-weekly 1:1s with each designer, an IDP per person by the end of the quarter, and a quarterly health check. Can we review the results together?" Bring them early into any performance concern.
- With your designers: explain how you'll work together: what 1:1s are for, how you give feedback, which delegation level they have on their current work. Clear rules of the game build trust faster than good intentions.
- In a promotion or hiring conversation: typical questions are "How would you support a struggling designer?", "How do you give feedback?" and "How do you avoid micromanaging?" For each, name the method (the humane underperformance process, SBI, delegation levels), then give one real example, even a small one from mentoring. "I use SBI. Last month I told a designer that…, and in the next review they…" beats any general statement.
Check yourself
Answer out loud, then open the section to compare.
- What are the three parts of SBI, and what comes after them? → answer
- How is coaching different from advising, and what is GROW? → answer
- How do you handle underperformance humanely? → answer
Connections
← Module 3: Personal Leadership Presence · Learning path · Module 5: Enterprise & Internal Applications →
Related
- Module 11: Workshop Techniques: a ready-to-run critique agenda, plus retro & team-health formats
- Module 7: DesignOps, Team Models & Capacity: where 1:1s fit in team rituals
- Module 3: Personal Leadership Presence: courage for corrective feedback
- 01 › B. People leadership: score yourself on people leadership