Stanford Design Thinking vs. Other Design Thinking Models

Design thinking is a potent tool for solving problems with ingenuity. While various models exist, each brings unique attributes to the table.

Let’s delve into how Stanford’s d.school model stands against other prominent frameworks.

Stanford’s d.school Model

Stanford’s d.school design thinking model encompasses five pivotal stages:

1. Empathize: Delve into understanding the end-users.
2. Define: Articulate the core problem succinctly.
3. Ideate: Engage in brainstorming a plethora of ideas.
4. Prototype: Construct basic, functional models.
5. Test: Validate solutions through user interaction.

This approach prioritizes empathy and rapid prototyping, ensuring a user-centered design process.

IDEO’s Design Thinking Model

IDEO, a trailblazer in design thinking, employs a five-phase methodology:

1. Discovery: Conduct extensive research and grasp the problem space.
2. Interpretation: Transform research insights into actionable problem statements.
3. Ideation: Generate and expand on a multitude of ideas.
4. Experimentation: Develop and iterate prototypes.
5. Evolution: Refine and scale solutions based on feedback.

IDEO’s model emphasizes iterative learning and continuous evolution, fostering a dynamic problem-solving environment.

IBM’s Design Thinking Model

This model, known as the Loop, emphasizes ongoing collaboration:

1. Observe: Gather insights through observation and listening.
2. Reflect: Synthesize findings and conceptualize ideas.
3. Make: Build and test prototypes iteratively.

IBM’s approach underscores the importance of teamwork and continuous feedback, promoting a collaborative design ethos.

Comparative Insights

• Stanford champions empathy and swift prototyping to deeply understand user needs.
• IDEO focuses on iterative refinement and learning, allowing for flexible adaptation.
• IBM promotes a collaborative cycle of observing, reflecting, and making, fostering a team-centric innovation culture.

Practical Example

Consider a scenario where you’re designing a new mobile app.

With Stanford’s model, you would begin by immersing yourself in the user experience.

IDEO’s framework would then have you iterating based on user feedback.

Meanwhile, IBM’s approach would involve close teamwork and regular feedback loops to refine the app continuously.

Real-Life Applications

Stanford’s Model in Action

At Stanford, students use this model to tackle real-world problems. For instance, they might work on projects to improve healthcare delivery in underserved areas.

They begin by empathizing with patients and healthcare providers, defining specific challenges, brainstorming potential solutions, building prototypes like new patient intake systems, and testing these solutions in actual clinics.

This hands-on, user-centered approach ensures the solutions are practical and effective.

IDEO’s Model in Practice

IDEO has used its model to innovate across various industries. One notable example is their work with a major airline to redesign the boarding process.

They started with in-depth research, observing and interviewing passengers and staff. From there, they identified key pain points, such as long wait times and confusion.

Through iterative ideation and prototyping, they developed new boarding procedures and tools, continuously refining them based on user feedback. The result was a smoother, more efficient boarding experience.

IBM’s Loop in Use

IBM employs the Loop model in its internal projects and client work. For example, when developing a new enterprise software solution, they start by observing how employees interact with existing tools.

They then reflect on this data, generating insights and ideas for improvement. Prototyping and testing happen in short, iterative cycles, allowing them to refine the software quickly. This collaborative, feedback-driven process ensures the final product meets user needs and business goals.

Conclusion

Each design thinking model offers distinct advantages. For profound user insights and rapid prototyping, Stanford’s d.school model excels. IDEO’s model is ideal for iterative development and adaptability.

IBM’s Loop model is perfect for fostering collaboration and ongoing improvement. Choose the model that best aligns with your organizational needs and project goals.

References:

1. Stanford d.school: Stanford d.school Design Thinking
2. IDEO: IDEO Design Thinking
3. IBM: IBM Design Thinking