The word of the week : design thinking

The word of the week : design thinking

Design thinking is an iterative approach to problem solving that intentionally seeks out people with different perspectives, knowledge, skills and experience and has them work together to create a practical solution for a real-world problem.

Design thinking uses a process-based approach to solve problems and like any process, it involves a series of steps that are carried out in a particular order to achieve a goal. In this case, the goal is to identify a solution that is capable of succeeding, can be carried out in a timely manner and is likely to be accepted by all stakeholders.

The five steps in design thinking are empathize, define, ideate, prototype and test.

  • Empathize: This step involves interviewing stakeholders and asking open-ended questions. The goal is to learn more about the problem from multiple perspectives.

  • Define: This step involves synthesizing all the information that was gathered during the previous step and arriving at a group consensus that states what problem needs to be solved. The goal is to identify the scope and true nature of the problem.

  • Ideate: This step involves sharing ideas - however wild and impractical -- and using each other's ideas as triggers for continuing the ideation process. The goal is to brainstorm solutions to the problem.

  • Prototype: This step involves creating a mock-up that conveys the essence of a proposed solution. An important goal of this step is to help the design team weed out unworkable or impractical solutions and focus attention on ideas that are likely to be approved by stakeholders.

  • Test: This step involves presenting the prototype to stakeholders. The goal is to solicit feedback that will let the design team know if they have successfully solved the problem or whether they need to go back to the drawing board and repeat steps.

The concepts that form the foundation of design thinking are drawn from many branches of knowledge including engineering, computer science, the arts, social sciences and business. Depending upon the implementation, the steps may be called by different names, combined in different ways or carried out in different orders.

In many ways, design thinking reflects the management philosophy of Engineer Taiichi Ohno, who is credited with developing the Toyota Way to help with Japan's economic recovery after World War II. The Toyota Way has two components, Respect for People (also known as Respect for Stakeholders) and Continuous Improvement (also known as Kaizen). After the last recession in the United States, its guiding principles, which are customer-centric and designed to deal with changing constraints, were adopted by software developers and business managers under the new labels agile and lean. Since then, new terms like user story, specification by example and acceptance test have entered the lexicon and gone mainstream.

"The real value of design thinking is in bringing a cross-departmental team through the process." - Matt Schulz

From TechTarget

To continue your reading, see:

Developing Fiori apps requires design-centric thinking, UI5
Read the best practices and other advice from consultants and SAP on developing the Fiori apps that users demand, and learn what skill sets are required.

Shake up your mobile workflow with design thinking
Learn how design thinking can improve the mobile workflow by putting IT and developers in end users' shoes.

Software test management: Produce quality applications by fostering culture of respect
Are developers and testers treated equally? Agile expert Lisa Crispin talks to test managers about their experiences and what they want senior management to know.

Company-wide customer experience mapping
Lior Arussy explains how a customer experience manager can use mapping to determine customer satisfaction across all touch points in an organization.

Use elicitation techniques to discover software requirements
Discovering requirements for a software project can be challenging. Here are some techniques to use when defining business and software requirements

To view or add a comment, sign in

More articles by Jean-Albert Eude

Others also viewed

Explore content categories