2. CHALLENGE
MAK3itwants to build a solution which helps
product teams and productcoachesto pick the
right experimentsfor the testing of theirown
ideas.
Further, we want to test whetherGoogle Design
Sprint is a good sprint method
3.
4. RESULTS
• Enormous outputin just 5 days
• Feedback:the “great“ idea was rejected by the potential customers
• However,ideasfor new solutionsfor a following sprinthave been
generated
• Huge amountof validated learningsespecially with regard to the problem
• Good facilitation isthe key for a successful sprint
• The rigth team composition and concentrating 100%on the sprint is
extremely important
5. MONDAY: FORM THE BASIS
• Get together& roles
• Long-term goal
• Critical questions
• Draw a process card
• Talk to experts
• „How mightwe?“-
questionsQ&A
• Choose target customers
Kick-off, knowhowsessions, challenge & goal
6. THUESDAY: GENERATE SOLUTIONS
• Flashlightdemosand napkin
sketches of existing solutions
as means of inspiration
• Division oftasks
• 4-step sketch process & idea
generation
• Appointmin.5 customer
interviews
Inspiration, challenging, meetings with potential customers for Friday
7. WEDNESDAY: DECIDE
• Do the „solution gallery“
round tour
• Set focus points
• Quick feedback& decision
round
• Choose a fake name
• Division oftasks
• Design the story board
Present solutions, assess & choose, design the story board
8. THURSDAY: PREPARE THE TEST
• Choose the right tool
• Task division
• Conducta test-rehearsal
• Finalise the test
preparations
• Create the interview script
Embrace “Fake it“-philosphy, desgin a realistic front-end
9. FRIDAY: CONDUCT THE TEST
• Prepare the test room(s)
• Conduct5 tests and
documentthe results
immediately
• Look for patterns
• Decide on next steps
Interview customers, record reacrions, decision & next steps
11. INNOVATE LIKE GOOGLE
• In the last couple of yearsGoogle Ventureshelped
hundredsof startups and established
organisations(e.g Airbnb & Slack) to identify
problems and test solutionsby conducting the so-
called „Google Design Sprints“
• In 2016 Google published a bookabout their5-day
sprint process
• MAK3itis one of the first team in Europe to
implementthe Google Sprint process
12. DESIGN SPRINT DETAILS
• The goalof the sprint is to identifyandunderstandcustomer needsand problemsandto
continuouslytest newsolutionswithin 5-daycycles
• The intensiveworkis conductedin 4 - 6-headedteams alongwith an experiencedMAK3it
facilitator
• Option: Dependingon yourdemand(e.g. forIT-specialists, designers, marketing, etc.)MAK3it
experts couldadditionallycontributeto the projectas fulltime team members
• 5 days, fulltime, dailyfrom 10am to 5pm
14. CHALLENGE
MAK3itwants to build a solution which helps
product teams and productcoachesto pick the
right experimentsfor the testing of theirown
ideas.
Further, we want to test whetherGoogle Design
Sprint is a good sprint method
15.
16. RESULTS
• Enormous outputin just 5 days
• Feedback:the “great“ idea was rejected by the potential customers
• However,ideasfor new solutionsfor a following sprinthave been
generated
• Huge amountof validated learningsespecially with regard to the problem
• Good facilitation isthe key for a successful sprint
• The rigth team composition and concentrating 100%on the sprint is
extremely important
17. MONDAY: FORM THE BASIS
• Get together& roles
• Long-term goal
• Critical questions
• Draw a process card
• Talk to experts
• „How mightwe?“-
questionsQ&A
• Choose target customers
Kick-off, knowhowsessions, challenge & goal
18. THUESDAY: GENERATE SOLUTIONS
• Flashlightdemosand napkin
sketches of existing solutions
as means of inspiration
• Division oftasks
• 4-step sketch process & idea
generation
• Appointmin.5 customer
interviews
Inspiration, challenging, meetings with potential customers for Friday
19. WEDNESDAY: DECIDE
• Do the „solution gallery“
round tour
• Set focus points
• Quick feedback& decision
round
• Choose a fake name
• Division oftasks
• Design the story board
Present solutions, assess & choose, design the story board
20. THURSDAY: PREPARE THE TEST
• Choose the right tool
• Task division
• Conducta test-rehearsal
• Finalise the test
preparations
• Create the interview script
Embrace “Fake it“-philosphy, desgin a realistic front-end
21. FRIDAY: CONDUCT THE TEST
• Prepare the test room(s)
• Conduct5 tests and
documentthe results
immediately
• Look for patterns
• Decide on next steps
Interview customers, record reacrions, decision & next steps