UX frameworks are useful when they help a team make better decisions. The point is not to follow a method perfectly. The point is to choose the right structure for the product risk in front of you.
For a broader explanation of framework types and when to use them, start with these design framework examples.
Four useful UX frameworks
| Framework | Use it when |
|---|
| Double Diamond | The team needs to separate problem discovery from solution development |
| Design thinking | The team needs research, ideation, prototyping, and testing around an unclear problem |
| Jobs to be done | The team needs to understand user progress and motivation |
| HEART metrics | The team needs to measure UX quality through happiness, engagement, adoption, retention, and task success |
Double Diamond
- Use it when
- The team needs to separate problem discovery from solution development
Design thinking
- Use it when
- The team needs research, ideation, prototyping, and testing around an unclear problem
Jobs to be done
- Use it when
- The team needs to understand user progress and motivation
HEART metrics
- Use it when
- The team needs to measure UX quality through happiness, engagement, adoption, retention, and task success
How to choose
Choose by risk. If the problem is unclear, use discovery. If motivation is unclear, use jobs to be done. If the product is already live, use measurement and journey review.
Common mistakes
Using a full framework for a tiny decision.
Treating framework artifacts as the goal.
Choosing a framework because it is familiar, not because it fits the risk.
Related reading
For the parent article, read what UX frameworks are. For building one, see how to design a UX framework.