Choosing Your Framework: A UX Designer's Guide

As a UX designer, you've probably encountered multiple design frameworks and wondered: "Why are there so many? Which one should I use?"

The truth is, the Product Development Life Cycle, Double Diamond, and Design Thinking aren't competing methodologies—they're different tools for different situations. Understanding when and how to apply each one can dramatically improve how you work with your team and stakeholders.

When you're building a digital product

The Product Development Lifecycle is for product team where the UX designers embedded at startups, tech companies, or any organization shipping digital products.

As a UX designer in this context, you're part of a larger machine. You'll collaborate closely with product managers who define scope, engineers who build functionality, and stakeholders who hold the budget.

The Product Development Life Cycle gives everyone a shared language.

Your role shifts across stages. During brainstorming, you might contribute user research insights by taking on the role of a UX researcher to help the team identify which problems are worth solving.

In the define stage, you're translating business requirements into design opportunities. The design stage is where you shine—creating wireframes, prototypes, and polished interfaces.

During testing, you're interpreting user feedback and iterating rapidly. At launch, you're already thinking about version 2.0.

Why this framework works here 

It acknowledges the reality of shipping products in business environments. There are timelines, budgets, legal requirements, and marketing considerations. You're not just designing in a vacuum—you're designing as part of a system.

When design is leading the way

The Double Diamond is well-suited for UX designers at agencies, consultancies, or leading specific design initiatives within larger projects.

The Double Diamond gives you permission to explore before committing. In the first diamond (Discover and Define), you're conducting user research, synthesizing findings, and reframing problems.

You might spend weeks just understanding the problem space before proposing any solutions. In the second diamond (Develop and Deliver), you're generating multiple design concepts, testing them, and refining the best ones.

This framework is particularly powerful when you need to justify your process to clients or stakeholders who want to jump straight to solutions. The visual metaphor of diverging and converging helps explain why you need time to explore before narrowing down.

Why this framework works here

It centers the design process itself. When design is the deliverable—whether that's a prototype, a design system, or a strategic recommendation—the Double Diamond keeps you focused on doing rigorous, thoughtful work rather than rushing to the first idea.

When you're facilitating innovation

Design Thinking can be used by UX designers when acting as facilitators, working with non-designers, or tackling ambiguous problems that extend beyond traditional UX work.

Design Thinking's strength is its accessibility. When you need to run a workshop with executives, help engineers understand user empathy, or collaborate with marketing teams on service design, Design Thinking provides a framework anyone can understand and participate in.

You might lead a Design Thinking sprint where you guide cross-functional team members through empathizing with users, defining the core problem, ideating solutions together, building quick prototypes, and gathering feedback. You're not just designing—you're teaching others to think like designers.

Why this framework works here

It democratizes design. When you need buy-in, cultural change, or collaboration across disciplines, Design Thinking's human-centered principles and flexible structure make design accessible to everyone.

Using frameworks together

These frameworks can be layered strategically based on your own context.

A UX designer at a fintech startup building a new budgeting feature will follow the Product Development Life Cycle which provides a roadmap, quarterly goals, and a clear launch date. That's the macro framework for the team.

But during the design stage of that lifecycle, the UX designer might use the Double Diamond approach for your design process. You diverge by exploring multiple interface concepts, then converge on the strongest direction based on user testing. Your PM doesn't need to know you're using the Double Diamond—they just see that you're being thorough.

When you hit a roadblock or are unsure if something is feasible, you might facilitate a Design Thinking workshop with your product manager, a data analyst, and a customer support rep. Together, you re-empathize with users, redefine the problem, and ideate fresh solutions.

Choosing your framework

When starting a new project, ask yourself:

What's the scope? If you're shipping a complete product with business constraints, the Product Development Life Cycle provides structure. If you're solving a specific design problem, the Double Diamond focuses your efforts. If you're tackling a fuzzy, organizational challenge, Design Thinking opens up possibilities.

Who's involved? If you're working with a mature product team, they probably already follow a Product Development Life Cycle—align with it. If you're working with people unfamiliar with design, Design Thinking helps bring them along. If you're working primarily with other designers, the Double Diamond speaks your language.

What's the culture? Some organizations are process-driven and need clear stages (Product Development Life Cycle). Others value innovation and experimentation (Design Thinking). Some give design teams autonomy to work deeply (Double Diamond).

What are you delivering? Shipping a product? Product Development Life Cycle. Creating a design solution? Double Diamond. Building design capability in the organization? Design Thinking.

The underlying power

All three frameworks point to the same fundamental insight: good design requires understanding problems deeply before solving them. They all involve research, iteration, and putting users at the center. They all recognize that design isn't linear—you'll loop back, reconsider, and refine.

As a UX designer, your job isn't to be dogmatic about frameworks. It's to recognize that these are tools, not rules.

TLDR

• Use the Product Development Life Cycle to stay aligned with your product team.

• Use the Double Diamond to structure your design process.
  

• Use Design Thinking to bring others into the design conversation.

  
  

The framework matters less than the principles. After all, the best framework is the one that helps you ship great experiences for users. Everything else is just vocabulary.