You'll learn:
All the activities required for realistic design sprints
How to modify your agenda and activities for different timelines
How to incorporate quantitative and qualitative data into design sprints
17. Our Design Sprint Approach
UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST
1º
2º
✓
X
1º
2º
3º
C. TODD LOMBARDO — @IAMCTODD
18. A DESIGN SPRINT IS A FLEXIBLE TIME-BOXED
PROBLEM SOLVING FRAMEWORK THAT
INCREASES THE CHANCES OF MAKING
SOMETHING PEOPLE WANT
What Is A Design Sprint?
23. ANYTIME CUSTOMER VALIDATION IS NEEDED
WHEN YOU DON’T HAVE DATA
WHEN THERE ARE ASSUMPTIONS
WHEN YOU ENTER NEW MARKETS
WHEN YOU DESIGN SOMETHING NEW
When Is A Design Sprint Used
25. UNDERSTAND
GET THE BACKGROUND
Rules of the Design Sprint
Parking Lot
Hopes & Fears
Assumptions
KNOW THE USER
Who / Do
Personas
User Journey Map
DEFINE THE PROBLEM
Problem Statement
Problem Reframe
WRAP-UP
Daily Retrospective
36. Problem Statement
A problem statement is a challenge that
has business value for a persona
INSPIRED BY: JEFF LASH
37. Problem Statement
A problem statement is a challenge that
has business value for a persona
INSPIRED BY: JEFF LASH
38. Problem Statement
A problem statement is a challenge that
has business value for a persona
INSPIRED BY: JEFF LASH
39. Problem Statement
A problem statement is a challenge that
has business value for a persona
INSPIRED BY: JEFF LASH
40. Problem Statement
A problem statement is a challenge that
has business value for a persona
WHATWHY WHO
INSPIRED BY: JEFF LASH
41. Example
Human resources lacks
recruiting software
Human resource struggles to
hire top talent to maintain a
competitive advantageBAD
GOOD
INSPIRED BY: JEFF LASH
42. Problem Statement
Human Resources struggle to hire top
talent to maintain a competitive advantage
WHAT WHYWHO
INSPIRED BY: JEFF LASH
50. Title (H1)
PROBLEM SOLUTION
Water on the floor Mop
WHY? Leaky pipe Fix pipe
WHY? Too much pressure Lower pressure
INSPIRED BY: WOLF BRUENING
51. Title (H1)
PROBLEM SOLUTION
Water on the floor Mop
WHY? Leaky pipe Fix pipe
WHY? Too much pressure Lower pressure
WHY? Pressure regulator Replace regulator
INSPIRED BY: WOLF BRUENING
52. Title (H1)
PROBLEM SOLUTION
Water on the floor Mop
WHY? Leaky pipe Fix pipe
WHY? Too much pressure Lower pressure
WHY? Pressure regulator Replace regulator
WHY? Maintenance schedule More frequent inspection
INSPIRED BY: WOLF BRUENING
75. CONVERGE
GET STARTED
Review Agenda and Rules
Diverge Recap
DECISION CRITERIA
$100 Test
Assumptions Table
SKETCHING
Sketching - I
Ritual Dissent
Team Sketching – II
WRAP-UP
Workshop Retrospective
102. Interview Structure
1. Pre Roll: Establish background questions
(“how do you currently…”)
2. Test: Determine which tasks to test prototype
(“using this ____, try to…”)
103. Interview Structure
1. Pre Roll: Establish background questions
(“how do you currently…”)
2. Test: Determine which tasks to test prototype
(“using this ____, try to…”)
3. Post-Roll: Wrap-up questions
(“How does this compare to how you do it today…?”)
128. Agenda: Shorter day - 10a to 4p
Monday 10a to 4p
UNDERSTAND
Intro to Design Sprint
Intro to Understand
Problem Statement
Existing research
Facts & Assumptions
Reframe
Personas
Challenge Maps
Daily Retro
Tuesday 10a to 4p
DIVERGE
Intro to Diverge
Recap Day 1
Job Stories
Diverge Cycle
Mind Map
SixUps
Storyboard
Critique
Daily Retro
Wednesday 10a to 4p
CONVERGE
Intro to Converge
Recap Phase 2
Assumptions Table /
$100 Test
Identify Alternatives
Team Sketch I
Ritual Dissent
Team Sketch II
Daily Retro
Thursday
PROTOTYPE
Build prototype
Define Test Plan
Confirm Interviews
Friday
TEST
Interview #1
Interview #2
Interview #3
Interview #4
Interview #5
Friday
RETRO & DEBRIEF
Sprint Retro
129. Agenda: Invitee Hack
Core Team Exec Participation
Monday 10a to 4p
UNDERSTAND
Intro to Design Sprint
Intro to Understand
Problem Statement
Existing research
Facts & Assumptions
Reframe
Personas
Challenge Maps
Daily Retro
Tuesday 10a to 4p
DIVERGE
Intro to Diverge
Recap Day 1
Job Stories
Diverge Cycle
Mind Map
SixUps
Storyboard
Critique
Daily Retro
Wednesday 10a to 4p
CONVERGE
Intro to Converge
Recap Phase 2
Assumptions Table /
$100 Test
Identify Alternatives
Team Sketch I
Ritual Dissent
Team Sketch II
Daily Retro
Thursday
PROTOTYPE
Build prototype
Define Test Plan
Confirm Interviews
Friday
TEST
Interview #1
Interview #2
Interview #3
Interview #4
Interview #5
Friday
RETRO & DEBRIEF
Sprint Retro
Designer/Maker/Engineer
130. Day 1
UNDERSTAND
Intro to Design Sprint
Intro to Understand
Problem Statement
Existing research
Facts & Assumptions
Reframe
Personas
Challenge Maps
Daily Retro
Day 2
DIVERGE & CONVERGE
Intro to Diverge
Recap Day 1
Job Stories
Diverge Cycle
Assumptions Table / $100 Test
Identify Alternatives
Team Sketch I
Ritual Dissent
Day 3
PROTOTYPE
Build prototype
Define Test Plan
Confirm Interviews
Day 4
TEST
Interview #1
Interview #2
Interview #3
Interview #4
Interview #5
Day 4 or Day 5
RETRO & DEBRIEF
Sprint Retro
Agenda: Four Day Hack
133. Preparation / Research
IDEA BRIEF USER INTERVIEWS INTERNAL INTERVIEWS PLAN PREP
MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY
Design Sprint
UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST
Iteration 1
ASSUMPTIONS DIVERGE/CONVERGE PROTOTYPE TEST DEBRIEF
Final Iteration
ASSUMPTIONS FINAL PROTOTYPE TEST FINAL DEBRIEF GO / NO-GO
Agenda: Four Week Hack Alternate
136. Design Sprint
○ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule
ains
137. Design Sprint
○ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule
○ “Let’s focus on this textbox.” — More ambiguous = better
ains
138. Design Sprint
○ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule
○ “Let’s focus on this textbox.” — More ambiguous = better
○ “We’ll use our normal conference room” — Book it in advance (offsite
preferable)
ains
139. Design Sprint
○ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule
○ “Let’s focus on this textbox.” — More ambiguous = better
○ “We’ll use our normal conference room” — Book it in advance (offsite
preferable)
○ “I can only be there for half of day 2” — Clear schedules
ains
140. Design Sprint
○ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule
○ “Let’s focus on this textbox.” — More ambiguous = better
○ “We’ll use our normal conference room” — Book it in advance (offsite
preferable)
○ “I can only be there for half of day 2” — Clear schedules
○ “Can we do it in one day?” — No. Just….NO!
ains