Design Process Overview

A high-level look at the stages from research through delivery in design work.

stellae.design

Process

The Design Process Overview provides a framework for how design work progresses from problem identification to solution delivery. While many models exist (Design Thinking, Double Diamond, Lean UX), they share common phases: discovery (understanding the problem), definition (framing the opportunity), ideation (generating solutions), prototyping (making ideas tangible), validation (testing with users), and implementation (building and shipping). The key insight: the process is iterative, not linear — teams loop back based on what they learn. Good process provides structure while remaining flexible.

Why It Matters

The design process is the structured sequence of activities — research, ideation, prototyping, testing, and iteration — that transforms ambiguous problems into validated solutions. Having a shared understanding of this process across an organization prevents the two most expensive coordination failures: building the wrong thing because research was skipped, and endlessly iterating because there were no criteria for when a design is ready for development. The process is not a rigid waterfall but a flexible framework that teams adapt to their context while preserving the essential discipline of validating assumptions before committing resources.

Real-World Examples

Double Diamond process at the UK Design Council

The Double Diamond framework structures design into four phases: Discover the problem space, Define the specific problem to solve, Develop potential solutions, and Deliver the refined solution. The two diamonds represent two cycles of divergent then convergent thinking — first expanding and narrowing the problem definition, then expanding and narrowing the solution space. This model gives teams a shared language for where they are in the process and what type of thinking each phase requires.

IDEO's human-centered design process

IDEO's process moves through Inspiration, Ideation, and Implementation phases, with heavy emphasis on field research and rapid prototyping to validate ideas with real users before committing to development. The process explicitly requires teams to build and test rough prototypes early and often, making failure cheap and learning fast. This approach has been adopted across industries because it consistently produces solutions grounded in real human needs rather than stakeholder assumptions.

Counter-example

Skipping research to start building immediately

A team under deadline pressure skips user research and jumps directly from a stakeholder's feature request to high-fidelity design and development, assuming they already understand the user's need. After launch, analytics reveal that users ignore the feature entirely because it solves a problem they do not have, while the actual pain point — discovered in a post-launch survey — would have been identified in two days of user interviews. The team spends three months rebuilding a feature that proper process would have gotten right the first time.

Role-Specific Guidance

Common Mistakes

• The most common mistake is treating the design process as a linear sequence where each phase must be fully completed before the next begins, rather than as an iterative loop where insights from later phases feed back into earlier ones. Another frequent error is scaling the process uniformly regardless of project risk — applying a full research-ideate-test cycle to low-stakes decisions wastes time, while skipping it for high-stakes decisions wastes far more. Teams also confuse process compliance with quality, believing that following the steps guarantees good outcomes while neglecting the critical thinking, judgment, and craft that make each step actually effective.