UX Foundations
Frameworks
20 frameworks and techniques this course's lessons use, by area.
Each card opens the full framework: when to use it, the steps, an example, pitfalls and a template. The frameworks of every course are in one list, with a filter.
AI & design
- 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. In Build a type scale, Colour and contrast, Layout, grids and spacing, Typography for interfaces, What a design system is
Design systems
- 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. In What a design system is
- 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. In What a design system is
- 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. In What a design system is
- 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. In Patterns and when to break them
DesignOps & capacity
- 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. In Who does what on a product team
Enterprise UX
- 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. In 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. In How people think
Facilitation techniques
- 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. In Card sorting and tree testing, Short user interviews
- Assumption mapping
- Plot assumptions on known↔unknown × important↔unimportant, then test the important unknowns first, so opinions become research questions. In Problem statements and "How might we"
- 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. In The design process, What UX design is (and isn't)
- Empathy map
- Says / Thinks / Does / Feels for a user role, to align stakeholders on who the user is, based on real research. In Personas and archetypes
- How Might We
- Reframe pain points as "How might we…?" questions: narrow enough to act on, broad enough to allow options. In Problem statements and "How might we"
- Journey mapping and service blueprints
- Map stages, actions, pain points, systems and back-office processes, ideal for cross-domain operational flows. In Journey maps, Users, tasks and context
- 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. In Design critique in practice
Measurement
- 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. In 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. In Defining success
- 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. In Defining success
- 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. In Defining success, Usability testing with five people
People leadership
- 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. In Design critique in practice, The design process, Who does what on a product team
Saved only on this device.