Design Process
The design process is the structured series of steps designers follow from an initial idea through research, design, prototyping, and validation to a finished solution.
The design process is the framework designers use to move from understanding a problem to delivering a solution. It is not a rigid formula. It is a flexible structure that organizes creative work, grounds decisions in evidence, and helps teams collaborate.
How it works
The design process is a sequence of phases that feed into each other, though in practice the work is rarely linear. Research and discovery comes first: understanding the problem, the users, and the context through interviews, surveys, competitive analysis, market research, and stakeholder alignment. The outputs are user personas, problem statements, journey maps, and a clear picture of the opportunity. Define and frame follows , synthesising the raw research into a focused problem definition and design direction. The team creates personas and scenarios, frames design challenges as "how might we" statements, and sets goals and success criteria. Ideate and explore is the divergent phase: brainstorming, sketching, and running design workshops to generate many possible solutions before converging on the best one. Prototyping turns ideas into something tangible , wireframes, interactive prototypes, and visual designs that can be tested. Test and validate puts the design in front of users through usability testing, interviews, A/B tests, and feedback analysis, then iterates based on what is found. Refine and handoff finalises the design, prepares specs and assets, and collaborates with developers on the build. Launch and learn closes the loop: monitoring performance, gathering real-world feedback, and feeding that learning back into the next round of work.
When to use it
Use a design process whenever creative work needs structure , almost always. A process is most valuable when the problem is genuinely uncertain, the stakes are high, or multiple people need to collaborate on the same outcome. It is worth applying a lightweight process to small, familiar features and a deeper one to large, complex, or risky projects. The process is not worth rigidly following when the team already knows the answer, when the context is simple enough that informal methods work fine, or when the process itself becomes the point , producing deliverables instead of solving the problem. The right process is the one that actually gets used and produces good outcomes, not the one that looks best on paper.
Common mistakes
Skipping research is the most common and costly mistake , jumping straight to solutions without understanding the problem or the users. Skipping testing has the same effect in reverse: designing without ever putting the work in front of real people, so problems surface only at launch. Being too rigid is the opposite failure , following a process so strictly that it cannot adapt to the project, slowing things down without adding value. Being too loose is equally bad: no process at all leads to chaotic, reactive work driven by the loudest voice rather than evidence. Deliverables over outcomes is a subtle trap , producing the "right" artefacts instead of solving the problem and delivering value. Not collaborating means design happens in isolation, without input from research, product, engineering, or stakeholders. One-and-done treats the process as a single pass with no feedback loops. Perfectionism spends too long on any one phase, delaying progress without proportional benefit. Big design up front does all the design before any development, without the testing and iteration that would catch problems earlier.
Key takeaways
- The design process is the structured series of steps from problem understanding to solution delivery.
- Common phases: research, define, ideate, prototype, test, refine, and launch.
- A good process reduces risk, grounds decisions in evidence, supports collaboration, and improves quality.
- Well-known models include Design Thinking, Double Diamond, Lean UX, and Agile Design , each with a different emphasis.
- In practice the process is rarely linear: it involves iteration, parallel work, and adaptation to the project.
No lessons cover this yet
This term is defined ahead of the curriculum — the definition above stands on its own, and lessons will link here once they exist.
Browse what is publishedCommon questions
- What is the difference between the design process and design thinking?
- Design thinking is one specific model of the design process , the human-centered approach popularised by IDEO and Stanford's d.school, with its five stages of empathise, define, ideate, prototype, and test. The design process is the broader concept: any structured series of steps that takes a product from idea to solution. Design thinking is one way to run a design process; it is not the only one.
- How does the design process differ from product discovery?
- Product discovery is the learning activity , figuring out what to build and why before building it. The design process is the structured path from that understanding through to a finished solution. Discovery informs the design process by clarifying the problem and opportunities. The design process then takes that clarity and turns it into something testable, refinable, and ultimately buildable. They overlap and feed each other, but discovery is about learning what, and the design process is about working through how.
- Do all design teams need a formal process?
- No , but all teams benefit from some structure. A small, experienced team working on a familiar feature may do fine with a light, informal approach. A large team on a complex, risky project needs more rigour. The point is not to force every project through the same machine; it is to apply the right level of structure for the situation. What matters is that the team understands the problem, tests before committing, and learns from real feedback , however informally that happens.