The document discusses design sprints, which are a 5-day process to go from an idea to a tested prototype. It involves stages of understanding the problem, diverging on ideas, converging on a solution, prototyping, and user testing. The author discusses having conducted several successful design sprints across web and mobile products that significantly improved metrics like conversions, engagement, and growth. Key lessons are to properly prepare with data, stakeholders, and tools and to fully involve different teams to iterate quickly based on learnings.

1. Design Sprints

2. anthony broad-crawford
@broadcrawford

3. cto, @fooda

4. cto, ceo, cpo

5. the intersection of product,
user experience, and
engineering

6. Product Metabolism

7. first, what is metabolism?

8. it's the set of life-
sustaining chemical
transformations within the
cells of living organisms

9. what is product metabolism?

10. it's the set of life-
sustaning transformations of
hypothesis/observations into
key learnings through
released product changes

11. you want a high metabolism

12. this should be no more than
2 or 3 weeks

13. but this is really tough
given our current product
development methodologies

14. So What's Wrong With Our
Existing Methods?

15. waterfall

16. scrum

17. kanban

18. free for all

19. none of these make the
organization agile

20. enter design sprints

21. What's A Design Sprint?

22. 5 day process to go from an
idea, problem, or
opportunity, to a user
tested high fidelity
prototype

23. Understand > Diverge > Converge > Prototype > Test

24. Understand
1. Review the opportunity
2. Conduct lightning demo's
3. Layout existing user flows
4. Define success
5. Review existing research
6. Interview internal stakeholders
7. Review existing analytics

26. Diverge
1. Mind map
2. Crazy eights (sketching excercise)
3. Story board
4. Silent critique
5. 3 minute critiques
6. Super votes
7. Repeat

29. Converge
1. Search for conflict
2. Best shot or battle royale
3. Identify assumptions to test
4. Whiteboard your user story(ies)

30. Prototype
1. Make it minimally real
2. Write real copy
3. Divide and conquer
4. Lightning critiques
5. Review with an outsider

31. Test
1. Review your assumptions
2. Identify your key questions
3. Setup observation room
4. Test any A/V in advance
5. Conduct your tests
6. Assess your findings

32. So What Do We Think?

33. we've conducted several
design sprints

34. across our web products,
mobile products, and even a
visual rebrand

35. What Have We Learned?

36. love it, love it, love it

37. So, let's talk results

38. Results are what matter
1. Sales funnel conversion increased to 75% from 12%
2. Email open rates up to 26% from 10%
3. Email clickthrough rates up to 12 from 2%
4. Mobile MAU's (Monthly Active Users) up 1100%
5. Mobile purchases up 500%
6. Design Language modernized and resonating

39. Lessons learned

40. setup a product war room

43. don't walk in with a
solution

44. don't skimp on the prep :
data

45. don't skimp on the prep :
design brief

46. don't skimp on the prep :
stakeholder involvement

47. don't skimp on the prep :
sizing

48. don't skimp on the prep :
day 1 interviews

49. assign a sprint lead

50. assign someone to start
recruiting day 5 testers, on
day 1

51. invest in tools like
silverback & TestFairy

52. invest in codifying your
findings

53. prioritize your sprints
against your roadmap

54. allow sprints to beget
sprints

55. allow sprints to inform your
roadmap

56. involve engineering

57. involve the executives on
day 1

58. involve key stakeholders on
day 1

59. conduct retrospectives just
like engineering

60. Anthony Broad-Crawford
@broadcrawford
abc@anthonybroadcraword.com
650.691.5107 (c)