In industry discussions, I often ask professionals about their perspectives on various design frameworks. However, I have observed a gap in theoretical understanding, even among experienced designers. Some find the question itself unclear, while others conflate process, approach, and framework.
This article seeks to clarify these concepts, as they are fundamental to a designer’s expertise. A strong grasp of these ideas is essential for navigating senior and leadership roles effectively.
Design Approaches
Before diving deeper, let’s define Design Approach, as it’s the simplest to understand. A design approach refers to a specific way of tackling a design challenge, often influenced by the chosen framework. It defines the philosophy and mindset behind how a team or individual addresses a problem, shaped by principles, context, and constraints.
One of the most important things to understand about design approaches is that they are not something a designer simply selects and applies. Instead, they represent fundamental ways of thinking that are necessary to achieve the best possible outcome. To fully grasp design approaches, one must first understand design principles (which will be covered in a separate article). Design approaches are built on and support these principles.
At a high level, a user-centric mindset underpins all design work. Every other approach either operates under this umbrella or exists in parallel to it. However, user-centered design does not, by itself, define the entire user or customer experience—it is just one essential component of a broader, more complex system.
The User-Centered Design (UCD) approach prioritizes user needs, behaviors, and feedback throughout the design process. This is the foundation of modern design practices, and every other approach serves to reinforce it.
In addition to UCD, designers must be familiar with various complementary approaches that inform design decisions, including:
- Data-Driven Design – Leveraging analytics, A/B testing, and user behavior insights to guide decisions.
- Mobile-First Design – Designing for mobile devices first, then scaling up to larger screens.
- Accessibility-First Design – Ensuring inclusivity by prioritizing users with disabilities from the start.
- Conversational Design – Structuring interactions as conversations, commonly used in chatbots, voice UIs, and AI-driven interfaces.
- Emotion-Driven Design – Crafting experiences that evoke specific emotional responses.
- Ethical and Sustainable Design – Creating products with social responsibility, sustainability, and ethical impact in mind.
- Minimalist Design – Focusing on simplicity, clarity, and essential functionality.
- Speculative Design – Exploring “what if?” scenarios to anticipate future needs and innovations.
- Neuro Design – Applying neuroscience principles to enhance engagement and retention.
- Generative Design – Using AI and algorithms to generate optimized design solutions.
As these approaches illustrate, they serve as strategic directions for applying User-Centered Design effectively. Every designer, regardless of seniority, should be well-versed in these methodologies.
Understanding design approaches is critical at both execution and leadership levels. Designers must apply these approaches in their day-to-day work while also shaping strategic direction at an organizational level.
With the foundation of Design Approaches established, the next step is to explore the Design Process, a structured, step-by-step workflow that ensures design work is executed systematically and efficiently.
Design Processes
This section does not aim to provide an exhaustive breakdown of design processes. Instead, it highlights the fundamental differences between various approaches, outlines their advantages and disadvantages, and offers recommendations on when and where they are best applied. For execution-level insights, a deeper dive into specific processes is recommended. Where relevant, I will include links for those who wish to explore the theoretical aspects further.
Just as with design approaches, I often find that many professionals have only a surface-level understanding of design processes. While deep expertise in every process is not necessary at the execution level—most companies typically adopt one or two primary design processes—leadership roles require a broader awareness. Understanding the full spectrum of available methodologies is critical, a topic that will be further explored in the design framework section.
Key Design Processes
Design processes provide a structured, step-by-step framework for solving problems and developing products. Below are some of the most commonly used methodologies in UX and product design:
1. Double Diamond
A structured process emphasizing problem discovery before solution development. One of the most recognized methodologies, the Double Diamond is often introduced early in a designer’s career as it effectively illustrates the iterative nature of design. It is particularly useful for mobile and web applications, post-launch projects, service design, and enterprise product design. This approach works well for complex design challenges because it focuses on deep research, which provides valuable user insights. The structured process helps solve problems effectively. However, the research can take a lot of time, and although it is meant to be iterative, it’s often used in a linear way, making it hard to adjust quickly in fast-changing situations.
2. Design Thinking Process
Although often referred to as a process, Design Thinking is closer to an approach. However, some companies adopt it as a core methodology.
Design Thinking Process is a non-linear approach centered around empathy, ideation, and iteration. This approach is best for companies without dedicated designers or where generalists take care of design tasks, as well as teams where designers are part of product teams rather than working in a separate design team. However, it’s not ideal for environments with gaps in the development cycle, as it needs clear problem statements to work well. It can also be too broad, leading to too many iterations and slowing down progress.
3. Lean UX
A fast, feedback-driven process designed for agile environments. This approach is great for pre-launch projects, startups, and quick feature development, as well as teams using Scrum or Kanban workflows. It offers a good balance between traditional UX processes and fast, flexible execution.
4. Agile UX
Agile methodology is widely known, but its application in UX follows principles similar to rapid iteration found in other processes. This approach is ideal for fast-paced environments where close collaboration between design and development is crucial. However, it only works well with strong teamwork across functions and requires careful attention to avoid design inconsistencies due to rapid iteration cycles.
5. Google Ventures (GV) Design Sprint
A 5-day structured process for rapidly solving design challenges and validating ideas. This approach is best for early-stage startups launching new products and large enterprises testing radical innovations. It helps reduce uncertainty and encourages cross-functional collaboration. However, it’s not sustainable as a long-term design process because it’s intensive. It also requires full team commitment, which makes it unsuitable for teams constantly under tight deadlines. If a team faces frequent pressure, the delivery process should be adjusted rather than forcing continuous sprint cycles.
6. Jobs to Be Done (JTBD)
This methodology helps understand why users “hire” a product to solve a problem. Although user-centered, it’s more of a customer-centered process. It’s ideal for product teams focused on outcome-driven strategies instead of traditional persona-based approaches. It effectively uncovers user motivation but places less focus on the emotional aspects of user behavior, making it less suitable for design teams. It’s mainly used in product strategy rather than in design execution.
7. Double Diamond 2.0
This is an evolved version of the traditional Double Diamond, combining business strategy, agility, and ethical considerations. It’s ideal for UX leaders who need to align design with business goals while ensuring iterative validation, and for fostering a culture of experimentation and collaboration. It improves traditional design thinking by integrating cross-functional collaboration and strategic foresight.
+1. Atomic Design Process
This is not a dedicated design process but a methodology that combines approach and execution. While primarily a design approach, its structured nature makes it function like a process. It’s best for complex design systems or projects that span multiple platforms. It’s especially valuable for designers working on scalable design systems.
Frameworks
We have covered fundamental design approaches and processes, but the key question remains: As a Design Lead, how do we decide which one to use?
This brings us to design frameworks.
What is a Design Framework?
A design framework is a high-level structure or mental model that guides design thinking. While an organization’s structure may impose constraints on which frameworks can be used, these limitations are not absolute. As a Design Lead, when defining approaches or processes, we must understand why and how we are implementing them. In simple terms, a framework defines a high-level design process and approach planning, based on strategy, business needs, and user needs.
There is often an overlap between approaches and processes—some processes also function as approaches. Since a framework is a mental model, certain processes align closely with them, which is why we may encounter Lean UX as both a process and a framework.
A framework differs from a process in that it incorporates strategic thinking and decision-making in a holistic manner. The best example of this distinction is the difference between User-Centered Design (UCD) and Human-Centered Design (HCD). While User-Centered Design is an approach, Human-Centered Design is a framework.
When selecting a framework, the first step is to analyze the product lifecycle within the company.
Key Frameworks
1. Human-Centered Design (HCD)
HCD is a creative and iterative approach that prioritizes user needs, behaviors, and emotions throughout the design process. It ensures that products solve real problems in a meaningful and sustainable way.
Execution Steps: Inspiration → Ideation → Implementation
Thinking Model: Human-Centered Thinking
Feasible Design Processes: User-Centered Design, JTBD, Participatory Design, Service Design, Agile UX, Lean UX, Service-Centered Blueprint
2. Technology-Centered User Interface Design (TCUID)
TCUID is a lifecycle-driven framework that integrates sustainability, user impact, and product evolution into the design process. Unlike traditional models that focus primarily on usability, TCUID ensures that products are designed, used, and phased out responsibly.
Execution Steps: Thinking → Creating → Using → Improving → Discarding
Thinking Model: Product Lifecycle Thinking
Feasible Design Processes: System-Centered Design, Engineering-Driven Design, Function-First UI Design, Waterfall Design Process
3. Design-Centered Approach as a Framework
The Design-Centered Approach (DCA) prioritizes design as the primary driver of innovation, rather than being led solely by business, engineering, or user needs.
Execution Steps: Defining (the Why) → Understanding (the Ecosystem) → Shaping (the Design Direction) → Iterative Making → Bringing Design to Life → Improvement
Thinking Model: Form and Function-Focused Thinking
Feasible Design Processes: Double Diamond, Design Thinking, Atomic Design, Lean UX
4. Behavior-Centered Design
A psychological framework for designing habit-forming products. While primarily a product strategy approach, it can significantly impact the design framework selection.
Execution Steps: Trigger → Action → Variable Reward → Investment
Thinking Model: Behavior-Focused Thinking
Feasible Design Processes: BJ Fogg Behavioral Design Process, Gamification UX Process, Nudge Design Process, Habit-Centered Design (Hooked), Emotional Journey Mapping
5. Business-Centered Design
Prioritizes business goals, market viability, and revenue models as the primary drivers (e.g., Growth-Driven Design, KPI-Driven UX). This framework is not user-focused and is not covered in detail in this article.
How to choose framework?
A feasible design process is included within each framework, as not all organizations have the capability or expertise to define a dedicated Design Framework within a Product Framework. However, when the opportunity exists, defining a Design Framework is beneficial—especially for design-driven products.
The core principle in selecting a framework is choosing the right mental model that aligns with the product lifecycle.
Key Questions When Selecting a Framework:
- What Thinking Model/Mental Model best aligns with the product, process, and strategy?
- What is the current product lifecycle and how does the framework support it?
- What is the status of the team (size, expertise, maturity)?
- How does the framework align with business and user needs?
Summary
Design Approach
- Specific philosophy or perspective you take within that framework.
Design Process
- It is the actual execution—how you move from problem to solution.
- It is a step-by-step workflow that helps execute design work systematically.
- Practical way to execute the Design Framework thinking
- Use it when executing design work, running workshops, or delivering a product.
Design Framework
- It is the overarching structure that guides your work.
- It is a high-level structure or mental model that guides design thinking.
- It is a structured way of thinking for the Design Process execution
- Use it when shaping strategy, guiding team alignment, or defining principles.
By understanding and selecting the right design framework, Design Leads can align their teams, processes, and strategies with both business needs and user expectations, ensuring a structured and effective approach to product development.
