The deck used to structure one of the Design Sprints at The Economist

1. Design Sprint
January 2015
P R O J E C T A U R O R A

2. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Introduction
• Your Name
• What you do

3. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Rules
• No device policy
• Timer
• Decider
• Parking lot

4. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Design Sprint
What is it?
• A 5-day process based on design thinking for answering critical business questions through
design, prototyping, and testing ideas with customers invented by Google Ventures.
Why do it?
• Efficiency. Quick way of building and testing a product (huge ROI if the solution works, time
and money saved if it doesn’t)
• Team alignment. Co-creation process unites the team around the same goal and expedite
decision making process
• Customer-Centric. We’ll test solution with real users
• Innovation. Time constraint boosts creativity and prototyping frees us to test risky ideas

5. P R O J E C T A U R O R A . D E S I G N S P R I N T.
The Design Process
“Design Thinking combines empathy, creativity and rationality to
solve human-centered problems.

6. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Day 2: Ideate
• Objective:
Generate ideas for potential solution(s)
• Deliverable:
• Prototype Storyboard
Objectives
Day 1: Shared Understanding
• Objective:
have a shared understanding of the problem
we’re solving
• Deliverables:
• User flow
• Tasks to ideate on

7. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Agenda
Day 1: Shared Understanding
10:00 Introduction
10:10 Design Sprint Goals
10:20 Opportunity Presentation
10:30 Research Presentation
11:30 Break
11:40 Affinity Mapping Activity
1:00 Lunch
2:00 User flow Activity (individual)
3:00 Break
3:10 User flow Activity (group)

8. P R O J E C T A U R O R A . D E S I G N S P R I N T.
How Might We…
HMW
bring users back?
As we go through the next
presentations, you’ll identify
problems/gaps we could
potentially work on.
Write each one on a post-it note
in this format to allow for open-
ended design exploration

9. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Mapping Customer
Experience

10. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Map Customer Experience
Activity
TIMING
DELIVERABLE
KEY OBJECTIVE(S)
Maps of customer journey for first time and returning
experiences
45 min
45 min
1. Map first time experience on board
2. Map returning experience on board
Visualize customer journeys for first time and returning
experience

11. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Choose the problems
Activity
TIMING
DELIVERABLE
KEY OBJECTIVE(S)
4 tasks for ideation on Day 2
15 min
15 min
1. Align HMW notes to customer journey map
2. Choose top 4 tasks to ideate on
Identify the problems (tasks) to ideate on

12. P R O J E C T A U R O R A . D I S C O V E R Y W O R K S H O P S
Day 2

13. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Sketching

14. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Activity: Crazy 8
EXERCISE
TIMING
DELIVERABLE
KEY OBJECTIVE(S)
Sketches of high level ideas
5 min
20 min
1. Individually: create 6 - 8 ideas for first time
user flow
2. In groups: Present and critique.
Generate many high level ideas for a feature in short period of
time

15. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Storyboard

16. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Activity: Storyboard
EXERCISE
TIMING
DELIVERABLE
KEY OBJECTIVE(S)
Storyboards of screens/UI elements for a feature
10 min
5 min
10 min
15 min
1. Individually: Choose one of idea from the
previous exercise, then create a storyboard (of
screens or UI elements). Add annotations to
help describe your ideasDot voting
2. Within group: Dot voting
3. Within group: Present and critique
4. As a group: Create final storyboard
Elaborate on idea in the form of storyboard

17. P R O J E C T A U R O R A . D E S I G N S P R I N T.
Activity: Creating one
EXERCISE
TIMING
DELIVERABLE
KEY OBJECTIVE(S)
Screens for prototype
60 min
60 min
1. Both groups: present & critique each other’s
work
2. Combine storyboards into one flow (to
identify screens for prototype)
Define final flow that we’ll turn into prototype for testing