https://journal.highlandsolutions.com/getting-started-with-design-thinking-82df24a6f8a9
📌 ARTICLE proposant une rapide méthodologie pour bien débuter en Design Thinking.
La partie la plus intéressante portant sur le Design Sprint :
Day 1: Planning, Research, and Sourcing
- Define the journey’s point of view.
- Create an “inside-out” experience map of the customer journey.
- Create personas and target interview list.
- Identify and schedule interviews with seven to ten participants. Local, face to face interviews or video interviews are preferred.
Days 2 and 3: Guided Storytelling Interviews
- Conduct 60–90 minute guided storytelling interviews.
- Transcribe interview notes into narratives.
- Collect existing data (survey results, for example) that are relevant for the map.
Day 4: Map!
- Create journey maps, including current touchpoints and potential opportunities for research, change, and transformation.
Day 5: Strategy and Insights
- Analyze and prioritize opportunities generated from the map.
- Rank opportunities for change based on impact and feasibility.
- Design actionable changes.
- Reflect on the process and consider next steps.
Journey maps often result in a digital asset that may look something like this one that we created for Make-A-Wish Illinois:
But the activity itself — aligning a team around the actual customer experience — is more important than the artifact, so don’t get too caught up in making something pretty after the fact.
3. Sprint: Design Thinking In a Box
A design sprint is a time-constrained, five-phase process that prescribes a set of design thinking exercises to help a team create or improve a product, service, or experience. This approach was created and popularized by Google Ventures and summarized in their intro to Design Sprints content.
Jake Knapp, a former member of the Google Ventures team, wrote a book called Sprint that details exactly how to do a design sprint. When a Highland team tried the process after it was published in 2016, we did it with the book open, simply following the steps each day. The description allows a team to focus on the work instead of creating a process, so you can jump right into problem-solving.
