Frameworks
142 frameworks, techniques and concepts from the courses, each on a one-screen card: when to use it, the steps, an example, pitfalls and a template. Filter by word, course or area.
AI & design 11
- AI adoption ladder
- A four-rung scale for where a designer is with AI on one specific task, so you can coach the next step instead of pushing “AI adoption” in general. UX Lead · AI for UX: Guiding designers through AI adoption
- AI champions network
- A small, rotating group of designers (one per 3–5 colleagues) who try tools, write playbook entries and run office hours, so the whole team learns from a few people's experiments. UX Lead · AI for UX: Guiding designers through AI adoption, UX agents and skills: a guide for designers
- AI usage guidelines
- A one-page “how we use AI in UX” covering approved tools, data rules, review rules, transparency and where to ask, so designers can experiment safely without asking permission each time. UX Lead · AI for UX: AI governance and data protection, Guiding designers through AI adoption
- Context files
- Files that AI agents read automatically (CLAUDE.md, AGENTS.md, DESIGN.md) that hold your principles, design-system rules and conventions, so every session starts from your standards instead of generic defaults. UX Lead · AI for UX: AI for content design, AI-ready design systems, Build your first skill, Claude Design, Design specs for AI, Generating design with Claude Code, How a model learns: train one on your laptop, Prompt patterns for designers, UX agents and skills: a guide for designers, What AI is (and isn't)
- Design tokens
- Named design decisions (colour, spacing, type, radius) stored as data in one place, so design tools, code and AI agents all use the same values and you can check that they do. UX Lead · AI for UX: Claude Design, Figma AI · UX Foundations: Build a type scale, Colour and contrast, Layout, grids and spacing, Typography for interfaces, What a design system is
- Human-in-the-loop
- AI proposes, a named human decides and stays accountable. Use it to set clear review, approval and undo points, both in your team's AI work and in the AI features you design. UX Lead · AI for UX: AI design review process, AI governance and data protection, Agentic design
- MCP
- Model Context Protocol: an open standard for connecting AI agents to tools and data (design files, browsers, issue trackers), so you can decide which systems your team's agents may read or change. UX Lead · AI for UX: AI tools landscape for designers, AI-ready design systems, Conversational and generative UI, Figma AI, Generating design with Claude Code, UX agents and skills: a guide for designers, What AI is (and isn't)
- Spec-driven development
- A way of working where every feature starts from written specs (requirements, then design, then tasks) that humans review and agents implement, so UX can own the experience before any code is generated. UX Lead · AI for UX: Design specs for AI
- Synthetic users
- AI-simulated “users” or personas that answer research questions. Use them to brainstorm hypotheses and sharpen your research plan, never as a substitute for real users or as evidence. UX Lead · AI for UX: AI in UX research, AI tools landscape for designers, Synthetic users and digital twins, What AI is (and isn't)
- Trust calibration
- Designing AI features so users trust them exactly as much as they deserve: not blindly (automation bias) and not never (wasted value), and testing that they do. UX Lead · AI for UX: Agentic design, Designing for uncertainty, Ethics, bias and inclusion in AI design
- Vibe coding vs production code
- Fast AI-generated code is great for prototypes and risky as unreviewed production code. Use this to make the boundary explicit: where prototypes live, how they are labelled, and who decides what moves to production. UX Lead · AI for UX: Prototyping with AI
Design systems 15
- Atomic design
- Brad Frost's five stages (atoms, molecules, organisms, templates, pages) for thinking about an interface as parts and wholes, so you can see what to build once, what to combine, and where real content tests the system. Design Systems: From components to patterns
- Component accessibility checklist
- The WCAG 2.2 success criteria a single component can meet or fail, grouped by the four principles, so every component ships with a tested accessibility contract instead of waiting for a screen-by-screen audit. Design Systems: Accessible components
- Component API checklist
- Six questions to answer in plain words before you draw a component (its job, parts, what changes, what never changes, its states and what it is not), then three checks that turn each answer into a variant, a property, a slot or a token. Design Systems: Anatomy and API of a component, Variants, properties and slots
- Component doc template
- A component page in the order people ask: name and status, one sentence, a live example, when to use and when not, how it works, accessibility, content, research and changelog, with each fact kept in one place and linked from the others. Design Systems: Component docs people use, Write a component doc page
- Component state matrix
- A grid of every state a component must ship (interaction states the browser sets, component states the product sets, data states the content brings) against what each needs: a design, the right attribute, a measured contrast and an edge-case test. Design Systems: States and edge cases
- Contribution process
- A lightweight path from a domain need to a released pattern (check existing, propose, council review, build, document, announce) that lets many teams grow the design system without you reviewing everything. UX Lead · UX Foundations: What a design system is · Design Systems: Contribution models
- Deprecation lifecycle
- Five stages for taking a component, token or property out of a design system (decide, deprecate in a minor, help people move, remove in a major, support the old major for a while), so nothing disappears by surprise. Design Systems: Deprecation and breaking changes
- Design system adoption playbook
- Seven moves that get teams to adopt the design system without policing: involve early, make the right way easy, show the benefit, pilot, migrate incrementally, listen to rejection, escalate rarely. UX Lead · Design Systems: Bringing teams onto the system
- Design system governance models
- Four ways to own a design system (solitary, centralised, federated, hybrid) and how to pick the one that fits your organisation. Federated or hybrid usually fits distributed enterprise teams. UX Lead · UX Foundations: What a design system is · Design Systems: Contribution models, Funding and staffing a design system team
- Design system metrics
- Six signals that show whether the design system works (adoption and coverage, detach rate, delivery time, consistency defects, satisfaction, contribution health), so you can report on it like a product. UX Lead · UX Foundations: What a design system is · Design Systems: Measuring adoption, Showing the value of a design system
- Design system ROI estimate
- A sum a finance partner can check line by line: the hours product teams get back from the system, minus the time they spend on it, next to what the system team costs, so you can say whether the system pays for itself and from what volume. Design Systems: Funding and staffing a design system team, Showing the value of a design system
- Pattern tiers
- Four tiers for design-system patterns (core, recommended, domain-specific, experimental) that make it explicit where teams must be consistent and where they are free to differ. UX Lead · UX Foundations: Patterns and when to break them · Design Systems: From components to patterns
- Semantic versioning for design systems
- MAJOR.MINOR.PATCH applied to a design system, where the API includes names, defaults, layout and behaviour, so every release number tells product teams how carefully to update. Design Systems: Versioning and releases
- Three-tier token model
- Primitive tokens hold raw values, semantic tokens name what a value is for, component tokens name one slot in one component, and aliases link them in one direction, so a mode, a rebrand or a second brand moves one link instead of every component. Design Systems: Token tiers
- Token naming formula
- A fixed order for building token names from general to specific (category, concept, variant, state), with a list of allowed words for each part, so every name tells people when to use it and new names stay consistent. Design Systems: Naming tokens
DesignOps & capacity 10
- Allocation patterns
- Five ways to give a domain design support (dedicated, shared, pool/flex, enablement, tiger team), so you can match the pattern to each domain instead of spreading designers evenly. UX Lead
- Capacity map
- A monthly view of who works on what at what percentage, with a 15–20% buffer kept free, so stakeholders can see design supply and the trade-offs behind it. UX Lead
- DACI
- Four roles (Driver, Approver, Contributors, Informed) that you name before a cross-domain decision is discussed, so everyone knows who decides and who only gives input. UX Lead · UX Foundations: Who does what on a product team
- Decision rights matrix
- A table of who decides, who is consulted and who owns what between the central UX lead, the domains and the designers, so a hybrid team model doesn't turn into constant negotiation. UX Lead
- Definition of Done for design
- A short shared checklist (states, edge cases, accessibility, annotations, design-system usage) that says when design work is ready for handoff, agreed with developers and QA. UX Lead · AI for UX: AI design review process
- DesignOps three layers
- NN/g's way of grouping DesignOps into how we work together, how we get our work done, and how our work creates impact, so you can find the real gaps and fix them with minimum viable standards. UX Lead
- RICE scoring
- A scoring formula from Intercom (Reach × Impact × Confidence ÷ Effort) that lets you compare backlog items on one scale and explain why one goes first. UX Lead
- UX intake
- One shared entry point for UX requests that captures the problem, users, impact, deadline and size, so all demand is visible and can be prioritised fairly. UX Lead
- UX team models
- Three ways to organise designers (centralised pool, decentralised/embedded, or hybrid where designers report to UX and sit long-term in domains), so you can name your model and fix its weak spot. UX Lead
- Weighted scoring
- Criteria and weights agreed with stakeholders before any request is scored, which makes UX prioritisation transparent and less political. UX Lead · AI for UX: Building an AI agent roadmap for your UX team
Enterprise UX 2
- Contextual inquiry
- Observe and interview users while they do their real work, in their real place, so you see the workarounds (Excel sheets, sticky notes) that interviews and demos never show. UX Lead · AI for UX: Guiding designers through AI adoption · UX Foundations: Short user interviews, Users, tasks and context
- Expert-user efficiency
- Seven design patterns for internal tools used by experts doing repetitive work (efficiency features, density, consistency, progressive disclosure, error prevention, respect for muscle memory, strong data tables) that you can use to review and improve a screen. UX Lead · UX Foundations: How people think
Facilitation techniques 28
- 1-2-4-All
- Think alone → pairs → foursomes → whole group. The default structure for equal participation. UX Lead
- 15% Solutions
- "What can you do now, with your own discretion and resources?" A Liberating Structure that ends a session with small actions each person can start immediately. UX Lead
- 4Ls retro
- Liked / Learned / Lacked / Longed for: a learning-focused retrospective that helps a team reflect on what it learned and pick 1–2 experiments. UX Lead
- 5 Whys
- Ask "why?" repeatedly about a single problem to get from the symptom to a root cause you can act on. UX Lead
- Affinity mapping
- Write findings on sticky notes, cluster them silently, then name the clusters as insights, so a group can make sense of research together. UX Lead · AI for UX: AI-assisted synthesis, step by step · UX Foundations: Card sorting and tree testing, Short user interviews · UX Research: From notes to themes, affinity mapping
- Assumption mapping
- Plot assumptions on known↔unknown × important↔unimportant, then test the important unknowns first, so opinions become research questions. UX Lead · UX Foundations: Problem statements and "How might we"
- Brainwriting 6-3-5
- 6 people × 3 ideas × 5 rounds of passing sheets, building on each other's ideas without dominant voices. UX Lead
- Buy a Feature
- Give stakeholders a budget to 'buy' items, so trade-offs become tangible and negotiation happens in the open. UX Lead
- Consent decision
- "Is this good enough for now and safe enough to try? Any objections?" A way to decide on standards and process changes without endless consensus. UX Lead
- Cover Story
- "It's three years from now and a magazine praises UX in your organisation. What does the story say?" A way to co-create an ambitious, concrete vision. UX Lead
- Crazy 8s
- Fold a sheet into 8 panels and sketch 8 ideas in 8 minutes. It gets non-designers sketching too. UX Lead
- 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. UX Lead · UX Foundations: The design process, What UX design is (and isn't)
- Dot voting
- Each person gets 3–5 dots to vote silently, and everyone reveals together to avoid group-think. A fast way to narrow a long list. UX Lead
- Empathy map
- Says / Thinks / Does / Feels for a user role, to align stakeholders on who the user is, based on real research. UX Lead · UX Foundations: Personas and archetypes
- Fist to Five
- A quick consensus check: everyone shows 0–5 fingers for their level of support at the same time, and you discuss anything at 2 or below before you close the decision. UX Lead
- How Might We
- Reframe pain points as "How might we…?" questions: narrow enough to act on, broad enough to allow options. UX Lead · UX Foundations: Problem statements and "How might we"
- Impact-effort matrix
- A 2×2 of impact vs effort that shows quick wins, big bets, fill-ins and money pits. UX Lead
- Journey mapping and service blueprints
- Map stages, actions, pain points, systems and back-office processes, ideal for cross-domain operational flows. UX Lead · UX Foundations: Journey maps, Users, tasks and context
- Lean Coffee
- Participants propose topics, vote, then discuss in timeboxes. Good for UX guilds and community sessions. UX Lead
- MoSCoW
- Must / Should / Could / Won't. Scope a release or initiative and make the 'won'ts' explicit. UX Lead
- Remember the Future
- Imagine success has already happened, then describe what made it happen. It surfaces enablers and risks. UX Lead
- 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. UX Lead · UX Foundations: Design critique in practice
- Sailboat retro
- Wind (helps), anchors (holds back), rocks (risks), island (goal): a visual reflection for teams and programmes. UX Lead
- Start, Stop, Continue
- Three columns for a quick practice or team review: what to start, what to stop and what to continue, ending with one commitment per column. UX Lead
- TRIZ
- "What would guarantee the worst outcome?" List it, then find what you're already doing that resembles it, and stop. UX Lead
- Troika Consulting
- One person shares a challenge. Two others consult while the presenter turns away and listens. It's peer coaching between designers. UX Lead
- What, So What, Now What
- Facts → meaning → action: a debrief structure for research, pilots and retros. UX Lead
- Workshop canvas
- Why now, outcome, participants, decision method, pre-work, agenda, materials, risks, follow-up. No clear outcome means no workshop. UX Lead
Imagery 10
- Alt text decision tree
- The W3C's five questions, asked in order, that tell you what kind of image you have (text, functional, informative, complex or decorative) and so what its alt text should say, or whether it should be empty. Photography and Imagery: Alt text that helps, Alt text workshop
- Composition guides
- Four guides for reading and choosing a photo for a screen (thirds, leading lines, visual weight and negative space), used as reasons a photo works, not as rules it must pass. Photography and Imagery: Composition
- Generated image policy template
- A one-page policy with seven clauses (allowed, never, labelled, recorded, checked, tools, owner) that tells every designer where AI-generated images help, where they mislead, and how they are marked and tracked. Photography and Imagery: A team policy for generated images, Labels and provenance
- Image brief template
- A one-page brief of eight lines (job, subject, where it shows, light, copy space, people, avoid, deliver) plus a numbered shot list, so a photographer, a stock search or an image generator brings back the image the screen needs. Photography and Imagery: The image brief and the shot list, Write an image brief
- Image format chooser
- Which file format each kind of image gets (JPEG, PNG, WebP, AVIF or SVG), and how to set a quality bar by looking at your own photos instead of trusting rules of thumb. Photography and Imagery: Formats and compression
- Image licence checklist
- Six questions to ask of every image before it ships (where it comes from, which licence it carries, what that licence allows, and how to credit it), so the product only uses images it may use. Photography and Imagery: Licences without fear, Running an image library
- Image role check
- Four questions to ask of any image slot before you look for a picture: what job it does, which promise it makes (photo, illustration or nothing), how big the job is, and what the alt text says, so every image on a screen has a reason to be there. Photography and Imagery: Photo, illustration or nothing, What an image does in a product
- Representation audit
- A counting method for the people in your product's images: lay them all out, record who appears in which role, compare with who uses the product, and fix the brief, so stereotypes are found by evidence instead of by luck. Photography and Imagery: Bias in image generators, People in images
- Responsive image checklist
- Six things every product image needs before it ships (widths, sizes, crops, dimensions, loading priority and alt text), so each screen gets a sharp file that is no bigger than it needs and the page doesn't jump. Photography and Imagery: Images and page speed, Responsive images and art direction
- Text-over-image contrast check
- A five-step check for text on photos: find the spot most like the text, measure it, tune one scrim for the worst photo and every crop, and make it part of the component. Photography and Imagery: Audit a hero for legibility, Measuring contrast on a photo, Scrims, safe areas and focal points
Influence & change 11
- ADKAR
- Individual change runs through Awareness, Desire, Knowledge, Ability and Reinforcement; use it to diagnose where someone is stuck and pick the right fix. UX Lead · AI for UX: Guiding designers through AI adoption
- Articulating design decisions
- A four-step way to answer stakeholder feedback (listen, restate, respond, agree) that frames each design decision in the stakeholder's terms instead of yours. UX Lead
- BLUF executive summary
- Bottom Line Up Front: a one-page summary that opens with your recommendation, then gives why now, the plan, the impact, what you need and the risks, so a senior reader can decide fast. UX Lead
- Cialdini principles
- Six principles of persuasion (reciprocity, social proof, authority, consistency, liking and scarcity) that you can use ethically to help good ideas land with stakeholders. UX Lead
- Disagree and commit
- Raise disagreement early and clearly, make the risk explicit, and once the decision is made, support it fully and agree how you will learn whether it was right. UX Lead
- Influence currencies
- Influence works by exchange: find what the other person values (results, visibility, relationship, personal gain, purpose), offer it, and you can get help from people who don't report to you. UX Lead
- Kotter 8 steps
- John Kotter's eight steps for leading organisational change, from creating urgency to anchoring the change in culture, adapted to building a UX practice. UX Lead · AI for UX: Guiding designers through AI adoption
- Power-interest grid
- A 2×2 map of your stakeholders by power and interest that tells you how to engage each one: manage closely, keep satisfied, keep informed or monitor. UX Lead
- Pre-meeting
- Talk 1:1 with key people before an important meeting, use their input to improve your proposal, and walk in with no surprises and with allies. UX Lead
- Saying no formula
- Acknowledge the request, explain the constraint, offer options and let the requester choose the trade-off, so you never give a bare no or a yes you can't deliver. UX Lead
- Stakeholder interview
- A structured conversation, ideally in your first 30 days, to learn a stakeholder's goals, pains and expectations of UX, and to start a working relationship. UX Lead
Measurement 11
- GDPR-safe tracking plan
- A table that links every analytics event to the question it answers, with properties that contain no personal data, a retention limit and an owner, so you can measure the system and never individuals. UX Lead
- Goals-Signals-Metrics
- A three-step chain from a user goal to observable signals to trackable metrics, so you measure what matters instead of what is easy to count. UX Lead · UX Foundations: Defining success
- HEART framework
- Five UX metric categories (Happiness, Engagement, Adoption, Retention, Task success) that help you choose metrics per product; for mandatory internal tools, focus on Task success and Happiness. UX Lead · UX Foundations: Defining success
- Qual and quant balance
- Quant shows where and how much; qual explains why. Use quant to find and verify problems, and qual to understand and solve them. UX Lead
- SEQ
- The Single Ease Question: one 7-point question asked right after each task ("How difficult or easy was the task?"), so you can compare tasks cheaply in any test. UX Lead
- SUS
- The System Usability Scale: a standard 10-item questionnaire scored 0–100, where about 68 is average, so you can compare an app's perceived usability with its own past and with published data. UX Lead · UX Foundations: Defining success · UX Research: Measuring usability
- Task success and time on task
- The core performance metrics for internal tools: the percentage of users who complete a task, how long it takes (median), and how many errors they make. UX Lead · UX Foundations: Defining success, Usability testing with five people
- UMUX-Lite
- A 2-item usability questionnaire (usefulness and ease) that correlates with SUS and is light enough for frequent in-app surveys. UX Lead
- UX benchmarking
- Measuring the same top tasks with the same method over time, so you can show change, for example "success 70% → 92%". UX Lead
- UX maturity model
- Nielsen Norman Group's six stages (Absent, Limited, Emergent, Structured, Integrated, User-driven), assessed across four factors, so you can place your organisation and pick the next factor to improve. UX Lead
- UX ROI
- A conservative estimate of what better UX saves in productivity, errors, training, support and development, with every assumption stated, so leaders can weigh UX work like any other investment. UX Lead
Motion & interaction 10
- Animation performance checklist
- Six checks that keep motion smooth on a slow phone: animate transform and opacity, respect the frame budget, use will-change sparingly, keep the first frame of feedback immediate, count the weight of animation files and measure in the browser's developer tools. Motion and Interaction: Motion performance, Motion, performance and budgets
- Duration scale
- Four steps of duration, from about 100 ms for feedback to about 400 ms for full-screen moves, picked by size and then adjusted for frequency and for whether something arrives or leaves, so every animation in a product gets its length from one short list. Motion and Interaction: Duration: how long is right, Motion tokens
- Easing selection guide
- Pick the curve from what the motion does: things arriving decelerate, things leaving accelerate, things moving on screen ease in and out, and only motion tied to time or a value runs linear. Then write it as a value or a token, never as a word. Motion and Interaction: Easing curves
- Microinteraction model
- Dan Saffer's four parts of a microinteraction (trigger, rules, feedback, loops and modes), used as a checklist so a small moment gets designed, specced and tested instead of left to the animation. Motion and Interaction: Anatomy of a microinteraction, Prototype a microinteraction in Figma
- Motion purpose check
- Name the one job each animation does (feedback, state change, orientation, relationship or attention), check that it starts fast and only one thing moves at a time, and cut whatever has no job you can name in one word. Motion and Interaction: What motion does in an interface, When not to animate
- Motion spec sheet
- A one-table handoff for a piece of motion: for every layer that moves, the trigger, the property, the start and end values, the delay, duration and easing, the reduced-motion version and what happens if it's interrupted. Motion and Interaction: Documenting motion in a design system, Lottie, Rive and handing off motion
- Reduced-motion substitution table
- A table that lists every motion in a product with what it means and what replaces it when someone asks for reduced motion (keep, swap or remove), so the reduced version is designed once and keeps the meaning instead of switching everything off. Motion and Interaction: Audit a page for reduced motion, Designing a reduced-motion version
- Spring parameter guide
- How the three settings of a spring (stiffness, damping, mass) turn into speed and bounce, how the damping ratio tells you at a glance whether it overshoots, and how to pick values for gestures and for system moves. Motion and Interaction: Springs and physics
- Stagger and sequence rules
- Four rules for motion with more than one moving part (clear the old content, let one element lead, let its content follow in reading order, cap the stagger) and one sum that tells you how long people will wait. Motion and Interaction: Choreography and stagger
- Twelve principles of animation for UI
- Frank Thomas and Ollie Johnston's twelve principles of animation, sorted for interfaces: four that do almost all the work in a product, and eight that are spices, so you can review motion with a shared vocabulary instead of taste. Motion and Interaction: Motion principles for interfaces, Reviewing motion in critique
People leadership 14
- Career ladder
- A grid of levels × dimensions (craft, collaboration, impact, leadership) that makes expectations explicit, so growth and promotion conversations are fair and specific. UX Lead · AI for UX: Guiding designers through AI adoption
- Coaching Habit questions
- Seven short questions from Michael Bungay Stanier that keep you curious a little longer and slow your rush to give advice. UX Lead
- Crucial Conversations
- A toolkit for high-stakes, emotional conversations: start with heart, make it safe, then STATE your path so you can say the hard thing and still hear the other side. UX Lead
- Delegation levels
- A five-level scale for how much authority you hand over, from "look into it and report back" to "decide and act, no need to tell me", so you and the designer agree on it before the work starts. UX Lead
- Design critique
- A structured session where designers give feedback on work against goals and principles, kept separate from approval, so the work improves without anyone defending their taste. UX Lead · AI for UX: AI design review process, Design specs for AI · UX Foundations: Design critique in practice, The design process, Who does what on a product team
- GROW model
- A coaching conversation in four steps (Goal, Reality, Options, Will) that helps someone find their own next step instead of taking yours. UX Lead
- Individual development plan
- One page per designer with strengths, growth goals from the career ladder, actions, support and evidence of done, so growth becomes a plan you review together instead of a hope. UX Lead · AI for UX: Guiding designers through AI adoption
- One-on-one meetings
- A recurring meeting that belongs to the report, not to you. It builds trust, surfaces problems early and drives growth, and a shared running doc keeps it focused. UX Lead · AI for UX: Guiding designers through AI adoption
- Psychological safety
- A shared belief that the team is safe for interpersonal risk-taking. It lets you build a team where people raise problems, admit mistakes and question ideas early. UX Lead · AI for UX: Guiding designers through AI adoption
- Radical Candor
- Care personally and challenge directly. The failure mode for empathetic leads is ruinous empathy: being kind and unclear. UX Lead
- SBI feedback
- Feedback in three parts (Situation, Behaviour, Impact), then an invitation to share their view, so your feedback is specific, fair and easy to act on. UX Lead
- Situational leadership
- Adapt your style (direct, coach, support, delegate) to the person's competence and confidence on this specific task, instead of leading everyone the same way. UX Lead · AI for UX: Guiding designers through AI adoption
- Structured hiring interview
- Same questions for every candidate, scored on a rubric by more than one interviewer, starting from a written scorecard, so you hire on evidence instead of gut feeling. UX Lead
- 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, so you see team problems before they become crises. UX Lead
Presence & career 5
- 30-60-90 plan
- Listen (days 1–30), align (31–60), set direction (61–90): a plan for a new team, scope or role that makes you diagnose before you change anything. UX Lead
- Leadership log
- Five minutes every Friday to write 3 wins, one leadership moment, where you held back, next week's proposal and what you learned, so slow leadership impact becomes visible. UX Lead
- Propose, don't just report
- A four-part habit for raising problems: bring the evidence, why it matters, a proposed solution (even a rough one) and what you need, so you shape the decision instead of handing it to others. UX Lead
- STAR method
- Situation, Task, Action, Result (+ Learning): a structure for telling leadership stories clearly in promotion cases, performance reviews, stakeholder updates and hiring conversations. UX Lead
- Stretch ladder
- Seven graded exposures, from asking one question in a meeting to presenting a UX strategy to senior management, climbed one rung every 1–2 weeks to build presence through action. UX Lead
Research 9
- Insight statement
- A one- or two-sentence format for an insight: who does what, why, why it matters to a goal and where it points, plus the evidence, confidence and owner that make a team act on it. UX Research: Writing insights that change decisions
- Interview guide
- A one-page plan for a semi-structured interview: intro, warm-up, three to five open core questions tagged to research questions, and a wrap-up, used flexibly so a free conversation still covers what the study needs. UX Research: Asking good questions, The interview guide
- Margin of error and sample size
- One formula that tells you how far a survey percentage is likely to be from the truth, and, turned around, how many responses and invitations you need for the precision a decision asks for. UX Research: Sample size and margin of error
- Research method chooser
- Three plain questions (say or do, why or how many, real use or a set-up) that narrow dozens of research methods down to two or three, plus a second method from another corner to cover the first one's blind spot. UX Research: Choosing a research method
- Research plan one-pager
- A one-page agreement, written before any work starts, on what the study will learn, from whom, by when and for which decision, so nobody is surprised by what it delivers. UX Research: Writing a research plan
- Research questions to decisions
- A five-step ladder from a vague business worry down to the decision, the research questions, the method and the evidence that would decide, so a study answers something the team will act on. UX Research: Research questions that lead to decisions
- Screener questionnaire
- A short questionnaire that decides who joins a study: criteria from the research questions, past-behaviour questions that can't be gamed, and quotas so six people aren't six copies of one. UX Research: Recruiting participants, Screeners and sampling
- Six phases of thematic analysis
- Braun and Clarke's six phases for turning interview data into themes: read everything, code everything, then build, check, name and write up patterns of shared meaning you can defend. UX Research: Thematic analysis
- Usability task scenarios
- How to write the tasks for a usability test: a short realistic situation with a goal and the details, no interface words, ordered from exploratory to directed, with a success criterion written before the first session. UX Research: Planning a usability test, Tasks and scenarios
Strategy & vision 6
- Design principles
- A few opinionated rules that help a team choose between two good options. Use the opposite test to check that each one actually says something. UX Lead
- Now-Next-Later roadmap
- A roadmap organised by problems or themes and three time horizons instead of features and dates, so you can show direction and confidence without promising what you can't deliver. UX Lead · AI for UX: Building an AI agent roadmap for your UX team
- OKRs
- Objectives and Key Results: one qualitative objective with 2–4 measurable key results per quarter or year, so a UX team can say what outcome it wants and how it will know it got there. UX Lead
- Strategy kernel
- Richard Rumelt's three-part core of a good strategy (a diagnosis of the critical challenge, a guiding policy, and coherent actions that reinforce each other) that you can use to build a UX strategy instead of a list of goals. UX Lead
- UX value model
- A simple calculation that expresses internal-tool UX in operational terms (time saved × users × frequency, plus errors, training and support load), so stakeholders see what a design change is worth. UX Lead
- UX vision statement
- A short, repeatable statement of where UX is going and why, made concrete with 2–3 future-state scenarios and co-created with the people who must believe it. UX Lead