Triple Diamond + Design Thinking Framework

Part
01
of one
Part
01

Triple Diamond + Design Thinking Framework

The research team has curated a list of key deliverables associated with each phase of the Triple Diamond + Design Thinking diagram. Considering the intended use of this custom framework, the associated selection of work products was sourced from only the most credible institutions, including design thought leaders (e.g., Interaction Design Foundation), scientific journals (e.g., PoliPapers) and business case studies. Moreover, each physical deliverable was identified based on its recommended use specifically in support of the Triple Diamond, Design Thinking and/or Lean Startup methodologies. In cases where relevant deliverables were applicable only to digital or web products (e.g., sitemap creation during Stage 2), these work outputs were excluded. Additionally, in cases where a large variety of work outputs were available to support a step, the most widely cited were selected (with other options also listed below). These validated, hand-picked work outputs have been added to the one-page diagram that was drafted during the first hour of research (available at this link) as well as cataloged below for additional reference purposes, as helpful.

Stage 1a

  • User Personas: User personas are clearly defined profiles that are created for each of the different "users whose problems a team wants to solve." User personas generally include information about a typical user's goals, motivations, frustrations, education level and other relevant demographic/psychographic characteristics. These user personals help designers empathize with a specific audience.
  • Empathy Maps: Consisting of four quadrants (as depicted below), empathy maps capture and organize the "four key traits" that users demonstrate surrounding the problem in question.
  • Storyboard: Perhaps one of the most widely recommended deliverables across the Triple Diamond, Design Thinking and Lean Startup methodologies, storyboards can also be leveraged throughout multiple stages of the design process, including Stage 1a, Stage 1d and Stage 2. Storyboards in simple terms are a "comic strip" that outlines a user's actions and circumstances, thereby codifying both a potential customer's behavior as well as how the environment may motivate user behavior.
  • Customer Journey Map: Also referred to as an Experience Map, a customer journey map is a diagram that outlines a user's steps along a timeline, enabling a design team to understand the evolution of a user's motivations/problems/needs and associated context.


Stage 1b

  • Problem Statement: Specifically in the context of product design, it is recommended that problem statements take the form of a Point Of View (POV) statement. These statements define the challenge that a team has chosen to address, and present this selected mission in an actionable manner. Three elements are necessary to create an effective problem statement: user, need and insight, or "[User (descriptive)] needs [need (verb)] because [insight (compelling)]."
  • Is/Is Not Matrix: This deliverable helps a design team isolate the "who, what, when, and where about a problem." By doing so, critical factors are identified and extraneous considerations are eliminated.

  • How Might We Questions: These questions help facilitate the transition from the problem statement to solution discovery. The questions begin with "how might we" or "in what ways might we," and refer to specific aspects of the identified problem. If executed correctly, they can help "spark" the next stage of ideation.
  • Why-How Ladder: Another crossover deliverable, the why-how ladder guides a design team from broadly defining the problem (the why) to more specifically identifying actionable components (the how).

Stage 1c


Stage 1d

  • User Flow Diagram (or Solution Sketch): This flow chart outlines the steps a user will take with a design team's proposed product or service. Unlike a customer journey map, this diagram includes only what happens with a user and the design team's proposed product. Notably, user flow diagrams facilitate concept validation by quickly highlighting the efficiency of a proposed solution.
  • SMART Goals: This deliverable clearly articulates the goals, requirements and criteria that will be used in evaluating a proposed solution as it enters the subsequent design and development stage. All proposed goals must be Specific, Measurable, Achievable, Relevant and Time-bound.


Stage 2


Stage 3

  • Usability Report: Usability reports are the outcome of evaluations of a prototype, ranging from more qualitative evaluations (e.g., focus group with a prototype) to robust assessments (e.g., user test, as described below). A complete usability report includes the following components: background summary, methodology, test results and findings/recommendations.
  • User Test: This deliverable involves introducing users to the developed prototype in a context/scenario that matches the intended environment where it will be used. Observations and feedback are captured, documented and reported.


Stage 4

  • Business Case: This action plan for a selected solution considers how it will be launched, implemented, assessed and modified (if necessary) after commercial introduction. Key components include "tasks, dates, people in charge, participants, budget (resources and costs), and training plan."
  • Analytics Report: After a product's release, data is captured and analyzed to produce recommendations for how the design can be improved. This reporting must go beyond synthesizing data to delivery explanations and recommendations associated with the findings.

Research proposal:

Only the project owner can select the next research path.
Need related research? Let's launch your next project!
Sources
Sources