Launchpad Start Day 2 - Google Design Sprints

On the second day of Launchpad Start we did a one day design sprint to help startups state and define their problems, which they then attempted to solve.

Transcript

1. Google Design Sprint Launchpad Day 2
2. GOOGLE DEVELOPER EXPERT Johann du Toit @JOHANN_DU_TOIT | JOHANNDUTOIT.NET
3. The Day • 09:30-10:00 - Talk • 10:00 - 17:30 - 1 Day Sprint • 13:30 (lunch)
4. We will • Why and What • Guide through the 5 Phases • Solve your problem :)
5. We will • Why and What • Guide through the 5 Phases • Solve your problem :)
6. “ If you build it, they will come “
7. “ If you build it, they will come “ Lots of folks …
15. BUILD 2 1 3 4 LEARN IDEA LAUNCH
16. BUILD 2 1 3 4 LEARN IDEA LAUNCH
18. “ The shortcut to learning what your users actually want “
19. • Efficient Failure=Learn and move on • Flawed Success=RUN MORE SPRINTS • Epic Win=Move to Production The sprint ends with 3 results
20. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
21. < 2 DAYS Sprint
23. “NANO-sprints” goo.gl/ZSe7k9
24. PROBLEM SOLVING Cape Town is in trouble, we need to save as much water as possible. Build a service/app/web app that would allow: • People to monitor their usage • View the current dam levels and how many days are left
25. PROBLEM SOLVING Cape Town currently has 127 days left of water left, with the dam sitting at 25%. Residents are currently advised to save as much water as possible, and we have 3B water restrictions in place since 1 February 2017 until further notice. This means various rules are currently in place:
 
 https://goo.gl/Ue1YMC
28. “ … “ Parkinson's law
29. “ work expands to fill the time “ Parkinson's law
31. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
32. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
34. We will • Why and What • Guide through the 5 Phases • Solve your problem :)
35. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
36. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
37. Day 1: Part One • Lightning Talks • User Interviews
38. Users are the ultimate judges of whether a product is good or not and it can be useful to start a sprint by finding and interviewing users.
40. Day 1: Part Two • Persona’s • Key User Journey • How Might We's • Affinity Mapping
43. Voting
44. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
45. Day 2 • Reviewing existing solutions • Rough Sketching using Crazy 8’s • Voting on the parts of the sketches that work • Creating prototype designs that could be built
47. Voting
50. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
51. Day 3 • Review existing solutions • Voting on solution sketches • Story boarding the solutions
52. Vote
53. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
54. Day 4 • PROTOTYPE(S)
55. Prototype Your Sprint is an attempt to identify the solution to a problem. Your prototype is a chance to see how good the ideas from your Decide phase are. To do this you have to make it real enough that you can get a realistic response from a potential user when you’re in the Validate phase.
58. Paper is fine too prototypes give you more feedback, but for short 2 . Paper is just fine, just talking to someone. Ensure that the design is quite clear. Paper is fine too Interactive prototypes give you more feedback, but for short 2 days sprint. Paper is just fine, just talking to someone. Ensure that the design is quite clear.
59. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
60. Day 5 • Validate with users under recorded session • Stream session to team to watch reactions
64. • Efficient Failure=Learn and move on • Flawed Success=RUN MORE SPRINTS • Epic Win=Move to Production The sprint ends with 3 results
65. ESSENTIAL Remember 1. Users are the ultimate judges of whether a product is good or not 2. Prototype as fast as possible, to get it in front of users 3. Quick research by talking to users first
66. CHECK IT OUT Resources • www.gv.com/ • www.gv.com/sprint/ • johanndutoit.net
67. We will • Why and What • Guide through the 5 Phases • Solve your problem :)
70. The rest of the day … • 10:00-13:00 - Ideation • 13:30 (lunch) • 14:00 - 17:30 - Prototyping
71. BUT FIRST !
74. Mentors
75. The Day • 10:00-13:00 - Ideation • 13:30 (lunch) • 13:30 - 17:30 - Prototyping
76. Problem Statement What problem do we want to solve / brainstorm on ?
77. Problem Statement 3 W’s: • What • Whom • Why
78. We will design [what] to improve the experience [whom] because they value [why]
79. We will design storage and sharing service to improve the experience of graphic designers because they value being able to access/share all their designs revisions without worrying about storage space and hosting
80. We will design [what] to improve the experience [whom] because they value [why] 10 minutes
81. User Persona’s Who are we trying to solve the problem for ?
82. A good persona will contain • Name • User characteristics • User need • Insight
83. [name] is a [user characteristic] who needs (a way to) [user need] because she values [insight]
84. Jacques is a graphics designer who needs (a way to) to store PSD files online because he values he need to share revisions with clients and storing them requires more space than he has
85. [name] is a [user characteristic] who needs (a way to) [user need] because she values [insight] 15 minutes
86. Voting • Each team member gets 3 dots. • It’s ok to vote on your own. • It’s ok to put more than one dot on the same note • We’ll pay more attention to notes that have multiple votes, so think strategically • We are not trying to get to one direction at this point in time 10 minutes
87. Key user journey Whats steps are involved in solving the problem
88. Search Click add to Cart Click Checkout Find Product View Cart Fill Out Details Discovery 15 minutes User from Google Search
89. Voting • Each team member gets 3 dots. • It’s ok to vote on your own. • It’s ok to put more than one dot on the same note • We’ll pay more attention to notes that have multiple votes, so think strategically • We are not trying to get to one direction at this point in time 10 minutes
90. How Might We’s Positive open ended ideas
91. HMW’S How Might We? Write with a thick dark sharpie. Be succinct. One idea per sticky note. Not too broad, and not too narrow. If you don’t write it down it can’t be voted on. Good Example: HMW Use location to show relevant results? 15 minutes
92. Affinity Mapping Highlight problem areas presented by the HMW’s
93. Affinity mapping Start grouping ideas into categories. Don’t worry if the categories aren’t immediately apparent. Look for overlaps or duplicates to get started. Revise or change the categories to create the most useful mapping. 15 minutes
94. Voting • Each team member gets 3 dots. • It’s ok to vote on your own. • It’s ok to put more than one dot on the same note • We’ll pay more attention to notes that have multiple votes, so think strategically • We are not trying to get to one direction at this point in time 10 minutes
95. Voting • Each team member gets 3 dots. • It’s ok to vote on your own. • It’s ok to put more than one dot on the same note • We’ll pay more attention to notes that have multiple votes, so think strategically • We are not trying to get to one direction at this point in time 10 minutes
96. Rough Solutions Present a few rough ideas that could solve the problem
99. Voting • Each team member gets 3 dots. • It’s ok to vote on your own. • It’s ok to put more than one dot on the same note • We’ll pay more attention to notes that have multiple votes, so think strategically • We are not trying to get to one direction at this point in time
100. LUNCH Time for everyone to catch up as well till 2PM
105. Solution Sketches Draw a solution to the problem that you could see working
106. Solution Sketch Select what you think is your best idea, and best execution of that idea. Sketch it out, you can do multiple frames as needed, use real words, use words and pictures to create a sketch that can communicate on its own. Add a memorable title.
107. Voting • Each team member gets 3 dots. • It’s ok to vote on your own. • It’s ok to put more than one dot on the same note • We’ll pay more attention to notes that have multiple votes, so think strategically • We are not trying to get to one direction at this point in time
108. Prototyping Draw a solution to the problem that you could see working
109. morangi@google.com + me@johanndutoit.net Subject: #LaunchpadStartJHB - [Startup Name] 60 minutes Problem statement + User persona + Final prototype
110. Show & Tell Show us what the solution you found
111. ESSENTIAL Remember 1. Users are the ultimate judges of whether a product is good or not 2. Prototype as fast as possible, to get it in front of users 3. Quick research by talking to users first
112. Tomorrow Dum dum duuuuuum
113. GIVE SOME Feedback • www.gv.com/ • www.gv.com/sprint/ • johanndutoit.net