Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Design Sprints: The methods, outcomes and pitfa...
Search
tomprior
March 22, 2018
Design
1
130
Design Sprints: The methods, outcomes and pitfalls.
1. A brief rundown of what a Design Sprint is.
2. When to Sprint.
3. Deciding what to do next.
tomprior
March 22, 2018
Tweet
Share
More Decks by tomprior
See All by tomprior
Tools for business confident designers
tomprior
0
260
The designer with business confidence
tomprior
1
360
The collaborative creator: Climate, mindset, and mastery.
tomprior
1
300
Mapping Competitive Advantage with The Kano Model
tomprior
0
260
The Project Pre-Mortem: Harnessing prospective hindsight for healthier projects.
tomprior
0
720
An Adaptive Approach
tomprior
0
130
From Responsive to Reactive: Harnessing Context on the Web
tomprior
4
500
Driven by experience (and cupholders)
tomprior
1
330
Other Decks in Design
See All in Design
エンジニアでも捗る デザイナー的思考入門
tinykitten
PRO
1
890
Crisp Code inc. ブランドガイドライン
so_kotani
1
180
The Golden Whitney
ohtristanart
PRO
0
150
新年あけおめWSの実施スキルをみんなで振り返りタイムのススメ
sugiyama_sukedachi
0
120
同人音声のための、 最高の視聴体験を求めて【サブカル×デザインMeetUP!】
vivion
0
610
BPStudy#213〜ビジネスアナリシスとDDD(ドメイン駆動設計)パネルディスカッション資料 / BPStudy213-panel
haru860
0
220
プロジェクト内でデザイナーができること 日経電子版アプリ機能開発「For You」#nikkei_tech_talk
nikkei_engineer_recruiting
8
3.6k
今日から意識できるアクセシビリティ
fumiko
0
230
今日からできる実践アクセシビリティSNSというかXでaltをつけよう
securecat
1
210
マンガで分かるサービスデザインガイドライン
senryakuka
1
860
AIで加速するアクセシビリティのこれから
magi1125
3
420
藤本佳子・ポートフォリオ・2025/5/29
yoshi_designer
1
5.4k
Featured
See All Featured
Reflections from 52 weeks, 52 projects
jeffersonlam
349
20k
Done Done
chrislema
184
16k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
What’s in a name? Adding method to the madness
productmarketing
PRO
22
3.5k
Mobile First: as difficult as doing things right
swwweet
223
9.6k
It's Worth the Effort
3n
184
28k
Adopting Sorbet at Scale
ufuk
76
9.4k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
12k
A Tale of Four Properties
chriscoyier
159
23k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
8
750
Documentation Writing (for coders)
carmenintech
71
4.8k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
31
1.2k
Transcript
DESIGN SPRINTS The methods, outcomes and pitfalls. Hayden Slaughter &
Tom Prior ProductTank Brighton 22 March 2018
OUR EXPERIENCE Facilitated and participated in Design Sprints Made some
mistakes Run a lot of Sprint style design phases Learned a lot
JAKE KNAPP
None
A MISNOMER When is a Sprint not a Sprint?
A DISCLAIMER
WHAT WE WILL COVER 1. A brief rundown of what
a Design Sprint is. 2. When to Sprint. 3. Deciding what to do next.
1. The GV Design Sprint
How to Solve Big Problems and Test New Ideas in
Just Five Days 1. The GV Sprint
1. The GV Sprint
Jump forward in time. 1. The GV Sprint
Structured days, proven formula 1. The GV Sprint
SET THE STAGE 1. The GV Sprint
Assemble the team 1. The GV Sprint
Find a Facilitator 1. The GV Sprint
Nominate a Decider 1. The GV Sprint
Get a room 1. The GV Sprint
None
MONDAY Map 1. The GV Sprint
None
None
TUESDAY Sketch 1. The GV Sprint
None
None
WEDNESDAY Decide 1. The GV Sprint
None
None
THURSDAY Prototype 1. The GV Sprint
None
None
FRIDAY Test 1. The GV Sprint
None
None
1. The GV Sprint Let’s go
WOAH THERE 1. The GV Sprint
2. When to Sprint
The Product Manager says.. “We should do a design Sprint
for every feature!” 2. When to Sprint
Don’t waste a Sprint on business as usual 2. When
to Sprint
The CEO says.. “That’s an exciting idea, but too risky”
2. When to Sprint
Sprint the big stuff 2. When to Sprint
The Developer says.. “We can start developing this straight after
the Sprint” 2. When to Sprint
Sprints are not reliable product design 2. When to Sprint
“We don’t know whether this idea is worth financial investment”
The CFO says.. 2. When to Sprint
Use a Sprint to unlock budget 2. When to Sprint
“The Sprint will validate what we think about our customers”
The Marketing Manager says.. 2. When to Sprint
Sprints don’t replace proper research work 2. When to Sprint
You avoided pitfalls and picked the right thing to Sprint
on. 2. When to Sprint
You went from idea to tested prototype in just five
days. 2. When to Sprint
You gathered valuable feedback and identified patterns. 2. When to
Sprint
Your team developed a shared vision. 2. When to Sprint
3. What next?
It depends! 3. What next?
There were some unexpected wins The outcome was… 3. What
next?
Get them into your backlog 3. What next?
It bombed The outcome was… 3. What next?
Bin it 3. What next?
It went well, but there were unanswered questions The outcome
was… 3. What next?
Sprint again 3. What next?
We discovered a bigger problem The outcome was… 3. What
next?
Go deep 3. What next?
The idea tested well The outcome was… 3. What next?
Start your design process 3. What next?
WHAT WE SHARED 1. A brief rundown of what a
Design Sprint is. 2. When to Sprint. 3. What to do after a Sprint.
THANKS FOR LISTENING! Hayden Slaughter www.haydenslaughter.com @haydenslaughter Tom Prior www.thomasprior.co.uk
@tomprior