"The best designers aren't the ones who rigidly follow a set process. They are the ones who adapt and apply the right methods for the specific problem at hand."
When you first start learning product design, you’ll come across a "standard" design process that looks something like this:
- Empathize: Understand the users, their needs, and the problem space through research and observation
- Define: Clearly articulate the problem you’re trying to solve and your design goals, based on your insights from the empathize stage
- Ideate: Brainstorm and generate a wide range of possible solutions to the defined problem
- Prototype: Turn your ideas into tangible designs or models that can be interacted with and tested
- Test: Gather feedback from real users to evaluate your solution, learn what works (and what doesn’t), and refine the design
These steps come from the Design Thinking framework, which is widely used in UX and product design.
It provides structure and helps designers approach problems methodically. However, real-world projects often demand flexibility and adaptation rather than a strict adherence to these steps.
The Reality: Design Processes Vary
As you gain experience, you’ll realize that every project and every company operates differently.
The design process should be more of a flexible framework than a rigid checklist.
Real-world variations:
- Some teams have dedicated researchers; others rely on analytics and past insights
- Some projects start from scratch; others involve redesigning existing products with years of operational data
- Some companies prioritize rapid iteration; others require extensive validation before moving forward
- Some teams work in agile sprints; others follow waterfall methodologies
Case study from past projects