Within 5 days, the document describes how to: 1. Apply the Design Sprint methodology to quickly test ideas and identify which to pursue, 2. Use storyboarding and paper prototyping to make ideas more concrete, 3. Obtain feedback from real users on a digital prototype to determine if the initial idea is good and worth developing further. The process enables identifying the right solution to a problem with limited resources in a short timeframe.

1. Methodology
Design Sprint
How Google Ventures solve big problems and test new ideas in just 5 days!
to solve big problems and test new ideas in just 5 days
Try Design Sprint

2. Methodology
Design Sprint: read it!
• Jake Knapp accompanied hundreds of companies developing their business
• He adapted the Design Thinking double diamond to its specific needs
• Now all other Google departments are using it
Key points: this book is really easy to read. It proposes you a complete agenda for the 5 days with all the tools & tips you need. But you can
also use it just as a toolkit. And you can also do as I did: adapt it to your context! But understand and keep the philosophy: keep it simple,
timeboxed and based on key people capacity to work together.

3. Why & How?
• most projects fails due to a Wrong product
• how develop a Good one? First, be sure to chose the Good ideas!
• But how to do it with limited means & just in one week?
9/10 products fail because we build the WRONG product (Ash Maurya, Running Lean)
Most learning happens when you make the Real Customer test your product
To know if your ideas are good, find ways to make your Customer test
As much as possible
As soon as possible

4. Why & How?
• Find THE good idea means generate MANY ideas
• Test the ones we are thinking are good. See if they are as good as we thought
• but more important, ABANDON the bad ones!
Key points: finally the important point here is the SPEED! Do it QUICKLY! Design Sprint proposes to squeeze Build and Launch phases.

5. Methodology
Design Sprint: an adaptation of Design Thinking double Diamond
• Design Sprint applies the Design Sprint Double Diamond principle
• In a really timeboxed time frame: one week!

6. Methodology
Design Sprint: an adaptation of Design Thinking double Diamond
Key points: Key points: within the group of 5 to 10 people, ensure you will have the Decider (Sponsor, CEO, …) at least at the key moments
(e.g. Wednesday)
• First make the group define the Key Question they need to answer
• Find below the week agenda, day by day
• Don’t forget to conclude: what is the group’s answer?

7. Methodology
From a Vision for the Customer Value Proposition to a Product: 3 Phases, 3 methodologies
My context:
• I’m working on a more classical environment on project development
• I found really efficient to use Design Sprint to Quickly test your ideas to decide which product to develop
Key points: previously you might have used Design Thinking to re-invent the Vision & Business Value Proposition

8. Methodology
Design Sprint: my Return of EXperience
How you can adapt Jake Knapp’s principle of Design Sprint to your context
• Example of a real case where the file is passing through many steps, many departments, many hands
• The consequence is today, nobody knows where it is in the operational process …
“At anytime we want to know where the file is, who we can call to
proactively communicate in case of any delays”
User promise
Your mission : given the User promise, you have 5 days to
o propose a first step toward the User promise (a MVP v0)
o check if your idea is a good one … or not & pivot
Your means: almost nothing!
o A few hours with key process stakeholders
o No IT budget or really limited one
Do you accept the mission …

9. Methodology
Design Sprint: my Return of EXperience
Make the group propose a content for the MVP V0 in less than 2 weeks
• we did the job!
• with only 2 * 4 hours, 1 day to move the paper sketch to a balsamic sketch & 1 week of test
Make the group
o propose a first step toward the User promise (a MVP v0)
o check if the first ideas are good … or not & pivot
MVP V0 : a first step towards the user promise
1 Build a backlog of
User Stories
3 Challenge your Story Board:
Is the process sustainable?
2 Build your User Journey
With a Story Board4 Challenge your Story Board:
Is the User Interface user friendly?
6
5 Test with real users:
Is your Story a Good Story?
“At anytime we want to know where the file is, who we can call to proactively
communicate in case of any delays”
User promise

10. Methodology
Design Sprint: my Return of EXperience
Build your User Journey with a Story Board. In 3 steps, prioritize your backlog into MVP V0, MVP V1 & general backlog
• Duration: 2h
• Material: paper board, post-it and a comfortable room
Key points: to keep the timing and keep the group focused on the objective, pay attention to have a good facilitator. If you don’t master
yourself the meeting facilitation techniques, my advise is to look for one. And remember, your best friend remains the post-it!

11. Methodology
Design Sprint: my Return of EXperience
Is your journey sustainable? drafting & running the process, make the ideas more concrete for the group
• Each role is listing the data he wants to monitor
• The group has to tell when & who will input those data
• Duration: 1h Material: post-it
Create Process step 1 Event 1
Input
✓ Data A
✓ Data B
✓ Data C
✓ Data D
Input
role 1
Key events
role 2
Key
roles
Input
Consult
Consult Consult
ConsultConsult
✓ Data 1
✓ Data 2
✓ Data 2
Input
✓ Data 1
✓ Data 2
✓ Data 3
Questions:
Now the process is more concrete, is it sustainable? For each role?
…

12. Methodology
Design Sprint: my Return of EXperience
Is the User Interface friendly? drafting & running the GUI, make the ideas more concrete for the group
• Each role is drafting the “look & feel” of the required screens
• If you can, ask a UX designer to give you a hand (what we did)
• Duration: 1h Material: paperboard
In session, the UX designer sketches in live on paper
Question:
Now it is even more concrete, are you still comfortable with your User Journey proposal?
Key points: warning! Doing this paper sketching, the group will certainly express other User Stories. Pay attention to point them out and to
ask the group to properly prioritize them (v0? v1? backlog?).

13. Methodology
Design Sprint: my Return of EXperience
Is your Story a GOOD story? Make real users test your prototype
• Based on the real test, run 5 interviews to get the users feedback
• More than 5 is not required as the others should confirm the previous feedbacks
• Duration: one week Material: Balsamiq Mockup, outlook
Key points: of course, if you can take advantage of a more ‘clickable’ version, feel free to do it but it has to be ‘light’. Finally, we concluded
and based on the Sponsor’s feedback the group pivoted a little. But the conclusion was the original idea was a good one and had a GO
to develop it and improve it!
Run your test with real users & get their feedbacks:
• Scope: limited scope but relevant
• Duration: from 1 day to 2 weeks
Move your paper sketch to a “Balsamiq Mockup”
Question:
Now it is even more concrete, are you still comfortable with your User Journey proposal?