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
140
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
270
The designer with business confidence
tomprior
1
380
The collaborative creator: Climate, mindset, and mastery.
tomprior
1
310
Mapping Competitive Advantage with The Kano Model
tomprior
0
280
The Project Pre-Mortem: Harnessing prospective hindsight for healthier projects.
tomprior
0
740
An Adaptive Approach
tomprior
0
140
From Responsive to Reactive: Harnessing Context on the Web
tomprior
4
520
Driven by experience (and cupholders)
tomprior
1
330
Other Decks in Design
See All in Design
minpaku-community-scrum-patterns
norinity1103
1
310
Design Studio Deck | インクルーシブデザインスタジオCULUUM
culumu
3
3.7k
Hatena Engineer Seminar #33 チームと開発するためのモック
takuwolog
0
420
AIで加速するアクセシビリティのこれから
magi1125
3
660
Cyber Heart Online Book
hjnasby
0
170
Bulletproof Design System with TypeScript
takanorip
7
4k
「描く」という衝動に立ち返る〜Figma Drawがひらく思考のかたち〜
transit_kix
1
1.1k
[2025.6.30 もがく中堅デザイナー、キャリアの分岐点] なんでもやる系デザイナーのもがきかた
taka_piya
1
3.1k
Goodpatch Tour💙 / We are hiring!
goodpatch
31
880k
FigmaのFigmaファイルから学ぶTips & Tricks
hilokifigma
0
660
サービスデザインにおける、 映像活用の可能性(Spectrum Tokyo Meetup #18)
ka71
0
160
なぜプレイドにデザインエンジニアが必要だったのか?
t32k
0
1.7k
Featured
See All Featured
Side Projects
sachag
455
43k
Designing for humans not robots
tammielis
253
25k
Docker and Python
trallard
45
3.5k
RailsConf 2023
tenderlove
30
1.2k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
186
54k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
139
34k
Agile that works and the tools we love
rasmusluckow
330
21k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.6k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
53k
Why You Should Never Use an ORM
jnunemaker
PRO
59
9.5k
Music & Morning Musume
bryan
46
6.8k
YesSQL, Process and Tooling at Scale
rocio
173
14k
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