Table of Contents
Imagine spending three months designing a feature. You make it pixel perfect, run the tests, and finally ship it. But when you launch? Nothing. The metrics are flat and nobody is clicking.
Has that happened to you? It hurts, but it is a really common story. It usually happens because we skip the planning and just start designing. We focus on what looks good instead of what solves the problem.
That’s exactly where UX frameworks work. Instead of guessing what users want, UX frameworks provide you with a repeatable process to validate your ideas before you invest months of work.
Today, we are going to break down the five core UX frameworks: design thinking, lean UX, the double diamond and jobs- to be tone. You’ll know what exactly each framework does, and when to use it.
What is a UX Framework?
A UX framework is a structured, repeatable process that guides how your team researches user problems, makes design decisions, and validates solutions before shipping. It is not a UI library or a style guide. It is the thinking system that decides what you do, in what order, and why.
Without this system, design becomes just a guessing game. The product manager demands a feature, the developer focuses on the code cost, and the designer polishes the pixels. But nobody stops to ask if the feature actually solves a real user problem.
Notice what is missing? The user. A framework forces that difficult question early, before you spend months building the wrong thing. It acts as a safety net that catches bad ideas before they become expensive code.
You might also hear about "UX design principles" from experts like Jakob Nielsen’s 10 Usability Heuristics or Don Norman’s work on affordances. These are the rules of good behavior, like "make it consistent" or "give feedback."
They answer the question, "Is this actually good for the user?" Every solid design decision you make traces back to these core ideas. But the framework is the path you walk to make sure you follow them.
The 5 Core UX Frameworks
Think of these frameworks like different tools in a toolbox. You wouldn't use a hammer to fix a watch, and you shouldn't use the same design process for every project. Each of these five frameworks solves a different problem.
1. Design Thinking
Design Thinking is a human-centered approach to solving problems you do not fully understand yet. It was popularized by IDEO and Stanford’s d.school, and it is built on one main idea: great products come from deeply understanding real people, not from making assumptions. You do not start by designing, you start by observing.
IBM adopted this framework across their entire enterprise, training over 100,000 employees. It helped them drastically reduce the time it took to get products to market.
The process follows five distinct phases: Empathize, Define, Ideate, Prototype, and Test.
- Empathize: You study real users to challenge your own assumptions. You interview them and watch them work. The goal is to understand their behavior, not just what they say they like.
- Define: You boil down all your research into one sharp problem statement. You do not say "users want better onboarding." You say, "Users quit on screen two because they do not understand the value."
- Ideate: This is about quantity over quality. You generate tons of ideas through sketching or brainstorming. You want to escape the obvious answers to find something new.
- Prototype: You build the simplest thing possible to test your idea. In Figma, this means rough wireframes, not polished UI. Speed matters more than beauty here.
- Test: You put your prototype in front of real users. You watch what they do, not just what they tell you. Then you use that feedback to loop back and fix it.
2. Lean UX
Lean UX is about working fast and learning even faster. Imagine you have a hunch about a feature. You could spend three months building it, only to find out nobody wants it.
Or, you could spend two days testing a rough sketch to see if you are on the right track. Lean UX chooses the two-day path. It is based on "The Lean Startup" method, but applied to design.
Instead of trying to build a perfect product, you focus on validating your ideas through a simple loop: Think, Make, Check.
- Think: Look at your list of assumptions and pick the riskiest one. This is the thing that, if you are wrong, breaks your whole product. Turn that into a specific statement you can prove wrong.
- Make: Build the smallest thing possible to test that belief. Use a pen, paper, or rough Figma frames. Resist the urge to polish. No fancy fonts or colors. Just the raw idea.
- Check: Put that rough prototype in front of a real user immediately. Watch what they do. The output here is not a design file. It is a lesson. You either proved yourself right, or you learned something new.
You can run this cycle right inside Figma. Instead of designing full flows, you design single experiments:
- List your assumptions on a FigJam board.
- Create one Figma frame for the most important assumption.
- If the test fails, duplicate the frame, move the button, and test again in hours
Spotify uses this method to great effect. Their design teams work in two-week sprints. They spend the first few days building ugly, low-fidelity experiments. By the middle of the sprint, they have already tested them with real users.
3. Double Diamond
The Double Diamond is about not rushing. The British Design Council created it to help teams slow down. They found that the best teams do two things. First, they find the right problem. Second, they find the right solution. They never mix the two up.
You can map the first diamond to research. Use FigJam for workshops and keep your notes on a page in your Figma file. The second diamond is for design work. Use branching to try different layouts. Then, use Dev Mode to hand off the final specs.
The UK government used this to fix their websites. They had to merge thousands of sites into one. By separating the problem from the solution, they built a system that actually works for millions of people [UK Design Council, 2023].
The framework uses two diamonds to show this. You must finish the first diamond completely before you start the second one.
- Discover: You open the first diamond to explore. You do research and look at competitors. You want to see the big picture before you have an opinion.
- Define: You close the first diamond. You take all that research and pick one clear problem. This is the most important part. Everyone must agree before you move on.
- Develop: You open the second diamond. Now you explore solutions. You sketch and prototype many ideas. You are not building the final product yet.
- Deliver: You close the second diamond. You take the best idea, test it, and refine it. At the end, you have a design ready for developers to build.
4. Jobs-to-Be-Done (JTBD)
Jobs-to-Be-Done is not a process like the others. It is a lens for understanding why people use your product. Popularized by Clayton Christensen, the core idea is simple. Users do not buy products. They "hire" them to do a job.
If you understand the job they are trying to get done, you can build the right thing. It focuses on three dimensions: the practical work they need to do (Functional), how they want to feel (Emotional), and how they want to look to others (Social).
This framework is amazing for strategy. It answers "what should we build?" instead of "how should it look?"
Real-World Example: A B2B invoicing client asked us to add more reporting features because their competitors had them. But we ran a JTBD analysis and found the real job was not "generate reports." It was "get paid faster."
We redesigned the payment reminder flow instead. The result? Collections time dropped from 47 days to 29 days. A boring reminder feature drove more revenue than any report dashboard could have.
5. The Five Elements of UX
Jesse James Garrett introduced this model in his famous book. It organizes design into five layers, stacked on top of each other like a pyramid. The rule is simple: you cannot build the top layer until the bottom one is solid.
You can organize your entire Figma file using these five planes. Create a page for "Strategy" to list your goals. Build a "Scope" frame to list your features. Use simple shapes to map your "Structure" and flows. Then, build "Skeleton" wireframes before you ever apply a color or font.
This method works in the real world, too. A team building a mobile banking app used this approach. They defined their strategy first, then locked in the scope and navigation structure. Only after all that did they start wireframing screens.
The result? Zero major redesigns after launch. Their previous app needed two navigation overhauls in six months because they skipped these steps.
Most designers start at the top with visuals. This framework says you must start at the bottom with strategy. If the strategy is weak, the visuals do not matter.
- Strategy: The foundation. You ask two questions: What do users need? What does the business need? You must answer both before you draw a single line.
- Scope: You turn strategy into a list of features. You decide exactly what the product will do - and what it will not do.
- Structure: You organize those features. This is where you define the navigation and how users move around the app.
- Skeleton: You create the layout. These are your wireframes. You decide where buttons go and how content is arranged.
- Surface: The final layer. This is the visual design. You add colors, fonts, and images to make the skeleton look good.
How to Choose the Right Framework
.avif)
There is no "best" framework. Asking which one is winning is the wrong question. You need to ask which one fits your team, your timeline, and the specific problem you are trying to solve. Think of these frameworks like tools. You would not use a hammer to paint a wall.
Here is a simple way to see how they differ.
Common Mistakes When Applying UX Frameworks
Most problems with frameworks come from three bad habits. Teams skip the necessary research, follow the steps like a rigid script, or pick a framework based on habit instead of the project's needs. If you avoid these traps, your design process will run much smoother and your products will be better.
Skipping the Research
Assuming you know your users is a huge mistake. When teams skip research to save time, they build the wrong thing. In Figma, you end up with beautiful screens that do not work. Finding a bug in an interview is free. Finding it after you ship costs weeks of rework. Always do the research first.
Treating the Framework Like a Rigid Script
Do not follow the framework like a robot. You do not need five workshops just because the framework has five phases. A small team does not need the same process as a big company. Adapt the framework to fit your project. Use it as a compass to guide your thinking, not a checklist that slows you down.
Picking Based on Habit
Choosing a framework just because your lead designer knows it is a trap. You might default to Design Thinking out of habit, but your project is actually a 2-week sprint. That framework takes too long for such a short timeline.
Match the framework to the project, not to the person. Look at your timeline and your goals. Pick the tool that fits the job you have to do today.
Ignoring Stakeholders
Do not pick a framework in a vacuum. You have to consider who you work with. If you need formal approval from stakeholders, use a structured process like Double Diamond. If they want fast results, use Lean UX. Think about your team's expectations and choose a framework that fits them.
The Bottom Line
Stop trying to find the one "perfect" framework. Design Thinking, Lean UX, Double Diamond, and the Five Elements are just tools to help you work smarter. One helps you find the problem, one helps you move fast, and one helps you organize complex apps.
The best teams do not stick to just one. They mix and match to fit the project. The version of your product that users actually love will be built on the framework that asks the right questions at the right time. Pick the tool that fits your timeline and get building.
Frequently Asked Questions
What are the 5 UX frameworks?
Five well-known UX frameworks are Design Thinking, Lean UX, Double Diamond, Five Elements of UX, and Jobs To Be Done. They give you a clear way to go from idea to design.
What is the difference between Design Thinking and Lean UX?
Design Thinking takes time to understand the problem first. Lean UX moves quickly by testing ideas early. One slows down to learn, the other speeds up to check.
Can you use multiple UX frameworks in one project?
Yes. You can mix them based on what you need. For example, figure out the problem with one approach and test ideas with another.
Which UX framework is best for startups and MVP design?
Lean UX works well for startups because it helps you move fast and learn quickly. If you’re not sure about the problem yet, spend some time on Design Thinking first.
How does the Double Diamond framework work?
It follows four steps: Discover, Define, Develop, and Deliver. First you figure out the problem, then you work on solutions and improve them.
What is the Five Elements of UX model and who created it?
It was created by Jesse James Garrett. It shows five layers of UX, starting from basic goals and ending with the final look of the product.
Do freelancers and solo designers need UX frameworks?
Yes. It helps you stay on track and not jump straight into design without thinking things through.
