UX Lead · 11 min read
Frameworks index
All 103 frameworks, techniques and concepts in the course on one page, grouped by area, with a one-line summary each.
All 103 concepts, frameworks and techniques in the course, grouped by area. Each one is a one-screen card: what it is, how to use it, and links to the module section that teaches it, related concepts and further reading. To combine them into your own practice model, see Design your UX practice.
People leadership
- SBI feedback: Feedback in three parts: Situation, Behaviour, Impact. Then invite the other person's view.
- Radical Candor: Care personally and challenge directly. The failure mode for empathetic leads is ruinous empathy: being kind and unclear.
- GROW model: A coaching conversation in four steps: Goal, Reality, Options, Will.
- Coaching Habit questions: Seven questions that keep you curious a little longer and slow your rush to give advice.
- Situational leadership: Adapt your style (direct, coach, support, delegate) to the person's competence and confidence on this specific task.
- Delegation levels: Say how much authority you're handing over, from "look into it and report back" to "decide and act, no need to tell me".
- One-on-one meetings: A recurring meeting that belongs to the report, not to you. It builds trust, surfaces problems early and drives growth.
- Individual development plan: One page per designer: strengths, growth goals from the ladder, actions, support and evidence of done.
- Career ladder: Levels × dimensions (craft, collaboration, impact, leadership) that make expectations explicit and growth conversations fair.
- Psychological safety: A shared belief that the team is safe for interpersonal risk-taking. Google's Project Aristotle found it the strongest predictor of team effectiveness.
- Team health check: A quarterly anonymous 1–5 survey on clarity, safety, feedback, growth, workload and cross-domain connection, followed by a discussion of the lowest scores.
- Crucial Conversations: A toolkit for high-stakes, emotional conversations: start with heart, make it safe, STATE your path.
- Design critique: Structured feedback on work against goals and principles, kept separate from approval.
- Structured hiring interview: Same questions for every candidate, scored on a rubric by more than one interviewer, starting from a written scorecard.
Strategy & vision
- Strategy kernel: Good strategy = diagnosis of the critical challenge + guiding policy + coherent actions that reinforce each other.
- UX vision statement: A short, repeatable statement of where UX is going and why, made concrete with future-state scenarios.
- Design principles: Opinionated rules that help choose between two good options. Test: could a reasonable team adopt the opposite?
- Now-Next-Later roadmap: A roadmap organised by problems or themes and time horizons, not by features and dates.
- OKRs: Objectives (qualitative direction) with 2–4 measurable Key Results per quarter or year.
- UX value model: Express internal-tool UX in operational terms: time saved × users × frequency, plus errors, training and support load.
DesignOps & capacity
- UX team models: Centralised (pool), decentralised (embedded) or hybrid (designers report to UX, embedded long-term in domains).
- Decision rights matrix: A table of who decides, who is consulted and who owns what between the central UX lead, domains and designers.
- DesignOps three layers: DesignOps covers how we work together, how we get work done, and how our work creates impact.
- UX intake: One shared entry point for UX requests, capturing the problem, users, impact, deadline and size.
- Capacity map: A monthly view of who works on what at what percentage, keeping a 15–20% buffer for urgent work and practice.
- RICE scoring: Priority = Reach × Impact × Confidence ÷ Effort.
- Weighted scoring: Criteria and weights agreed with stakeholders before scoring requests, which makes prioritisation transparent and less political.
- Allocation patterns: Dedicated, shared (max 2 domains), pool/flex, enablement (DS + office hours) or tiger team.
- DACI: Driver, Approver (only one!), Contributors, Informed, named before a cross-domain decision is discussed.
- Definition of Done for design: A shared checklist for when design work is ready for handoff: states, edge cases, accessibility, annotations, DS usage.
Design systems
- Design system governance models: Solitary, centralised, federated or hybrid ownership of the design system. Federated or hybrid usually fits distributed enterprise teams.
- Contribution process: A lightweight path from domain need → check existing → proposal → council review → build, document, announce.
- Pattern tiers: Core (must use), recommended (use unless documented reason), domain-specific, experimental. It makes consistency vs autonomy explicit.
- Design system adoption playbook: Drive adoption without policing: involve early, make the right way easy, pilot, migrate incrementally, and treat resistance as information.
- Design system metrics: Adoption/coverage, detach rate, delivery time, consistency defects, satisfaction and contribution health.
Influence & change
- Power-interest grid: Map stakeholders by power and interest: manage closely, keep satisfied, keep informed, monitor.
- Stakeholder interview: A structured conversation to learn a stakeholder's goals, pains and expectations of UX, and to build the relationship.
- Influence currencies: Influence works by exchange. Find what the other person values (results, visibility, relationship, time saved, purpose) and offer it.
- Cialdini principles: Reciprocity, social proof, authority, consistency, liking (and scarcity). Use them ethically to make good ideas land.
- Pre-meeting: Decisions are rarely made in the meeting. Talk 1:1 with key people beforehand, incorporate their input, and arrive with no surprises.
- Articulating design decisions: Listen → restate → respond with goal, decision, reasoning and evidence → agree next steps. Frame decisions in the stakeholder's terms.
- Saying no formula: Acknowledge → explain the constraint → offer options → let them choose the trade-off. Never a bare no, never a yes you can't deliver.
- Disagree and commit: Raise disagreement early and clearly. Once a decision is made, support it fully and agree how you'll learn whether it was right.
- BLUF executive summary: Bottom Line Up Front: recommendation, why now, what we'll do, impact, what we need, risks. One page, one ask.
- Kotter 8 steps: Urgency → coalition → vision → communicate → remove obstacles → short-term wins → sustain → anchor in culture.
- ADKAR: Individual change runs through Awareness → Desire → Knowledge → Ability → Reinforcement. Diagnose where someone is stuck.
Measurement
- UX maturity model: Six stages (Absent, Limited, Emergent, Structured, Integrated, User-driven) assessed across four factors: strategy, culture, process, outcomes.
- Goals-Signals-Metrics: Start from a goal, identify behavioural signals, then pick metrics. It prevents measuring what's easy instead of what matters.
- HEART framework: Happiness, Engagement, Adoption, Retention, Task success. For mandatory internal tools, focus on task success and happiness.
- SUS: System Usability Scale: a 10-item questionnaire scored 0–100. Around 68 is average. Widely benchmarked.
- UMUX-Lite: A 2-item usability questionnaire that correlates with SUS. Light enough for in-app surveys.
- SEQ: Single Ease Question: "How easy was this task?" on a 1–7 scale, asked right after a task.
- Task success and time on task: The core performance metrics for internal tools: % who complete a task, and how long it takes (median).
- UX benchmarking: Measure the top tasks repeatedly over time so you can show change, e.g. "success 70% → 92%".
- GDPR-safe tracking plan: Event → question it answers → properties without personal data → retention → owner. Measure the system, never individuals.
- UX ROI: Productivity, error reduction, training, support and development savings, estimated conservatively with stated assumptions.
- Qual and quant balance: Quant shows where and how much; qual explains why. Use quant to find and verify problems, qual to understand and solve them.
Enterprise UX
- Contextual inquiry: Observe and interview users in their real work context. It's gold for expert operators of internal tools and surfaces the Excel and sticky-note workarounds.
- Expert-user efficiency: Internal tools serve experts doing repetitive work: density, keyboard, bulk actions, defaults, error prevention, and respect for muscle memory.
Presence & career
- Propose, don't just report: Every time you raise a problem, bring the evidence, why it matters, a proposed solution, and what you need.
- Stretch ladder: Seven graded exposures, from asking one question in a meeting to presenting strategy to management. One rung every 1–2 weeks.
- Leadership log: Five minutes every Friday: 3 wins, one leadership moment, where you held back, next week's proposal, and what you learned.
- STAR method: Situation, Task, Action, Result (+ Learning). A structure for telling leadership stories clearly: in promotion cases, performance reviews, stakeholder updates and hiring conversations.
- 30-60-90 plan: Listen (1–30) → align (31–60) → set direction (61–90). Diagnose before you change anything.
Facilitation techniques
- Diverge and converge: Every session alternates between opening up (generate, no judgement) and narrowing down (cluster, prioritise, decide). The messy middle is the groan zone.
- Workshop canvas: Why now, outcome, participants, decision method, pre-work, agenda, materials, risks, follow-up. No clear outcome means no workshop.
- Affinity mapping: Write findings on sticky notes, cluster them silently, then name the clusters.
- Empathy map: Says / Thinks / Does / Feels for a user role, to align stakeholders on who the user is.
- Journey mapping and service blueprints: Map stages, actions, pain points, systems and back-office processes, ideal for cross-domain operational flows.
- Assumption mapping: Plot assumptions on known↔unknown × important↔unimportant, then test the important unknowns first.
- 5 Whys: Ask "why?" repeatedly about a single problem to get from symptom to root cause.
- How Might We: Reframe pain points as "How might we…?" questions: narrow enough to act on, broad enough to allow options.
- Crazy 8s: Fold a sheet into 8 panels and sketch 8 ideas in 8 minutes. It gets non-designers sketching too.
- Brainwriting 6-3-5: 6 people × 3 ideas × 5 rounds, passing sheets and building on each other's ideas without dominant voices.
- Dot voting: Each person gets 3–5 dots to vote silently. Reveal together to avoid group-think.
- Impact-effort matrix: A 2×2 of impact vs effort that shows quick wins, big bets, fill-ins and money pits.
- MoSCoW: Must / Should / Could / Won't. Scope a release or initiative and make the 'won'ts' explicit.
- Buy a Feature: Give stakeholders a budget to 'buy' items, so trade-offs become tangible and negotiation happens in the open.
- Fist to Five: A quick consensus check: show 0–5 fingers for your level of support, then discuss anything ≤ 2.
- Consent decision: "Is this good enough for now and safe enough to try? Any objections?" It avoids endless consensus on standards and process.
- Cover Story: "It's 2028 and a magazine praises UX in your organisation. What does the story say?" A way to co-create an ambitious, concrete vision.
- Remember the Future: Imagine success has already happened, then describe what made it happen. It surfaces enablers and risks.
- Rose, Thorn, Bud: What's working (rose), what's painful (thorn), what's promising (bud). Ideal for a new lead's first-30-days listening.
- Start, Stop, Continue: Three columns for a quick practice or team review.
- Sailboat retro: Wind (helps), anchors (holds back), rocks (risks), island (goal): a visual reflection for teams and programmes.
- 4Ls retro: Liked / Learned / Lacked / Longed for: a learning-focused retrospective.
- Lean Coffee: Participants propose topics, vote, then discuss in timeboxes. Good for UX guilds and community sessions.
- 1-2-4-All: Think alone → pairs → foursomes → whole group. The default structure for equal participation.
- TRIZ: "What would guarantee the worst outcome?" List it, then find what you're already doing that resembles it, and stop.
- 15% Solutions: "What can you do now, with your own discretion and resources?" Ends sessions with immediate action.
- Troika Consulting: One person shares a challenge. Two others consult while the presenter turns away and listens. It's peer coaching between designers.
- What, So What, Now What: Facts → meaning → action: a debrief structure for research, pilots and retros.
AI & design
- Human-in-the-loop: AI proposes, a named human decides and stays accountable, with clear review, approval and undo points.
- Trust calibration: Users should trust AI exactly as much as it deserves: not blindly (automation bias), not never (wasted value).
- AI adoption ladder: Explore → Assist → Co-create → Orchestrate: where a designer is with AI for a given task.
- AI champions network: One champion per 3–5 designers tries tools, writes playbook entries and runs office hours. Rotate the role.
- AI usage guidelines: A one-page 'how we use AI in UX': approved tools, data rules, review rules, transparency and where to ask.
- Design tokens: Named design decisions (colour, spacing, type, radius) stored as data, so tools, code and AI agents use the same values.
- Spec-driven development: Work starts from written specs (requirements → design → tasks) that humans review and agents implement.
- Context files: Files that agents read automatically (CLAUDE.md, AGENTS.md, DESIGN.md) holding principles, DS rules and conventions.
- MCP: Model Context Protocol: an open standard for connecting AI agents to tools and data, e.g. Figma, browsers, issue trackers.
- Synthetic users: AI-simulated 'users' answering research questions. Useful for brainstorming hypotheses, never a substitute for real users.
- Vibe coding vs production code: Fast AI-generated code is great for prototypes and terrible as unreviewed production code. Make the boundary explicit.
AI area notes
AI design review process · AI governance and data protection · AI in UX research · AI tools landscape for designers · Agentic design · Claude Design · Design specs for AI · Figma AI · Generating design with Claude Code · Guiding designers through AI adoption · Prompt patterns for designers
Books
Org Design for Design Orgs · The Making of a Manager · Radical Candor · The Coaching Habit · Resilient Management · The Manager's Path · Crucial Conversations · Thanks for the Feedback · Good Strategy Bad Strategy · Articulating Design Decisions · Influence Without Authority · Leading Change · Never Split the Difference · Measuring the User Experience · Quantifying the User Experience · Design Systems · Atomic Design · Expressive Design Systems · Design That Scales · Team Topologies · An Elegant Puzzle · DesignOps Handbook · Quiet · The Introverted Leader · The Culture Map · The First 90 Days · The User Experience Team of One · Mapping Experiences · Lean UX · Thinking in Systems · Gamestorming · Facilitator's Guide to Participatory Decision-Making · Sprint · Sentient Design · Designing Assistant Technology · Co-Intelligence