http://gdgbari.github.io/zeppelin/ - http://www.gv.com/sprint/ - The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at Google Ventures, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more.

1. I’m Nick
Nicola Policoro
+zerodoIt
+nicolapolicoro

2. Nicola Policoro
+zerodoIt
+nicolapolicoro
Design SprintAndroid Wear

3. Google Ventures developed an intensive 5-day
product design sprint for startups

4. LEARN
BUILD

5. LEARN
BUILD

6. LEARN
BUILD

7. Learn
Build

14. DAYS 1-3
DAY 4
DAY 5

15. ● Before the sprint: Prepare
Get the people and things you need.
● Day 1: Understand
Dig into the design problem through research, competitive review,
and strategy exercises.
● Day 2: Diverge
Rapidly develop as many solutions as possible.
● Day 3: Decide
Choose the best ideas and hammer out a user story.
● Day 4: Prototype
Build something quick and dirty that can be shown to users.
● Day 5: Validate
Show the prototype to real humans.

17. 5 DAYS DESIGN SPTINT
At scale?

23. from teams of 4 … to team of 175

25. when you participate to a sprint you
either win or you learn.

26. -…and instead of 5 days, we’re going to do it in
about an hour and a half

30. 1. Challenge
2. User
3. Philosophy

31. Design Challenge
Build your service to come alive on the
wearable.

32. 1. Challenge
2. User
3. Philosophy

38. Jean needs
& wants
because
____________
____________
____________

39. 1. Challenge
2. User
3. Philosophy

40. Google’s been spending some some time looking at technology usage,
and thinking deeply about ways of staying connected to the people
around you, and those not currently with you.

43. Now that you have a basic
understanding of
1. The challenge
2. Your user
3. and this new form factor

44. It’s time to Diverge!

46. YES,
AND!

47. Design Challenge
Build your service to come alive on the
wearable.

49. #dfba14

50. Technical Complexity
UserValue
#dfba14

51. Technical Complexity
UserValue
Hackathon
#dfba14

52. Technical Complexity
UserValue
Hackathon Startup
#dfba14

53. Technical Complexity
UserValue
#dfba14

54. #dfba14

55. #dfba14

56. #dfba14

57. #dfba14

58. 8 key moments

59. - You now have 5 minutes to sketch or describe 8 different key moments that help
define the solution for this user experience;
- It is not a story board.
- Think of them as different possible experiences and interactions the user has
with the software. A moment can be…
- a screen: what does the service look like?
- an interaction: how does the persona interact with the service?
- a use case: when & where does the persona use the service? When does
the service intervene with a persona's life?

60. 8 key moments
feedback

61. 8 key moments
feedback
one key moment, expanded

66. What’s next?
Design Sprints
http://www.gv.com/sprint/

67. now you can conquer the world. Fast.
thx!