Google Design Sprints

What they are, why and a few activities cherry picked to give everyone an idea of the power of a design sprint

Transcript

2. GOOGLE DEVELOPER EXPERT Johann du Toit @JOHANN_DU_TOIT | JOHANNDUTOIT.NET
3. We will • Firstly build up some teams • What a Design Sprint is, and why Google created it • We will run a very quick sprint ourselves while being guided through the phases
4. We will • Firstly build up some teams • What a Design Sprint is, and why Google created it • We will run a very quick sprint ourselves while being guided through the phases
5. TEAM TIME™ 5 in a team
7. TIME LIMIT 3 minutes
8. We will • Firstly build up some teams • What a Design Sprint is, and why Google created it • We will run a very quick sprint ourselves while being guided through the phases
9. “ If you build it, they will come Lots of people …”
17. BUILD 2 1 3 4 LEARN IDEA LAUNCH
18. BUILD 2 1 3 4 LEARN IDEA LAUNCH
20. • Efficient Failure=Learn and move on • Flawed Success=RUN MORE SPRINTS • Epic Win=Move to Production The sprint ends with 3 results
21. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
22. < 2 DAYS Sprint
24. We will • Firstly build up some teams • What a Design Sprint is, and why Google created it • We will run a very quick sprint ourselves while being guided through the phases
26. 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
27. 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. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
29. Day 1: Part One • User Interviews • Lightning Talks • Building user profiles • How Might We's • Affinity Mapping
30. 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.
32. Day 1: Part Two Brainstorming
33. 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?
34. TIME LIMIT 3 minutes
35. 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.
36. TIME LIMIT 3 minutes
37. 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
38. TIME LIMIT 30 secondes
39. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
40. 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
42. TIME LIMIT 3 minutes
43. Voting
44. TIME LIMIT 3 minutes
46. 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.
47. TIME LIMIT 3 minutes
48. WOOHOO Congratulations!
49. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
50. Day 3 • Review existing solutions • Voting on solution sketches • Story boarding the solutions
51. Vote Vote Give each person 3 votes to place on the elements within the design they find most compelling. This will highlight parts of an idea
52. TIME LIMIT 3 minutes
53. DIRECTION Storyboarding
54. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
55. Day 4 • PROTOTYPES
56. 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.
59. 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.
60. MONDAY Map TUESDAY Sketch WEDNESDAY Decide THURSDAY Prototype FRIDAY Test SPRINT
61. Day 5 • Validate with users under recorded session • Stream session to team to watch reactions
62. GET SOME Feedback
63. ESSENTIAL Remember 1. Manufacture time pressure 2. Prototype as fast as possible 3. Quick research by talking to users first
64. CHECK IT OUT Resources • www.gv.com/ • www.gv.com/sprint/ • io.co.za • johanndutoit.net
65. info@io.co.za