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
Search
Luís Ferreira
June 04, 2016
Technology
0
160
Design Sprints
Luís Ferreira
June 04, 2016
Tweet
Share
More Decks by Luís Ferreira
See All by Luís Ferreira
Winter is coming
zamith
0
750
SI - Module5
zamith
0
76
Continuous learning, teaching and the art of improving yourself
zamith
0
140
Crystal Clean
zamith
2
220
Clean Code
zamith
3
200
The best language I have ever learned.
zamith
3
1.6k
Testing Magic
zamith
3
1.5k
Clean Code
zamith
7
1.6k
Other Decks in Technology
See All in Technology
LLM時代のパフォーマンスチューニング:MongoDB運用で試したコンテキスト活用の工夫
ishikawa_pro
0
160
Webブラウザ向け動画配信プレイヤーの 大規模リプレイスから得た知見と学び
yud0uhu
0
230
react-callを使ってダイヤログをいろんなとこで再利用しよう!
shinaps
2
250
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
8.8k
[ JAWS-UG 東京 CommunityBuilders Night #2 ]SlackとAmazon Q Developerで 運用効率化を模索する
sh_fk2
3
450
株式会社ログラス - 会社説明資料【エンジニア】/ Loglass Engineer
loglass2019
4
65k
AWSで始める実践Dagster入門
kitagawaz
1
670
slog.Handlerのよくある実装ミス
sakiengineer
4
310
はじめてのOSS開発からみえたGo言語の強み
shibukazu
1
760
Codeful Serverless / 一人運用でもやり抜く力
_kensh
7
440
【実演版】カンファレンス登壇者・スタッフにこそ知ってほしいマイクの使い方 / 大吉祥寺.pm 2025
arthur1
1
890
Autonomous Database - Dedicated 技術詳細 / adb-d_technical_detail_jp
oracle4engineer
PRO
4
10k
Featured
See All Featured
4 Signs Your Business is Dying
shpigford
184
22k
The Cult of Friendly URLs
andyhume
79
6.6k
YesSQL, Process and Tooling at Scale
rocio
173
14k
Scaling GitHub
holman
463
140k
Typedesign – Prime Four
hannesfritz
42
2.8k
Making the Leap to Tech Lead
cromwellryan
135
9.5k
Imperfection Machines: The Place of Print at Facebook
scottboms
268
13k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
29
1.9k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
30
9.7k
GraphQLの誤解/rethinking-graphql
sonatard
72
11k
Product Roadmaps are Hard
iamctodd
PRO
54
11k
Speed Design
sergeychernyshev
32
1.1k
Transcript
Design Sprints
GOALS of a design sprint
Produce a prototype with a solution for the job to
be done, based on real world information and validate it with potencial customers
EMPATHY
CREATIVITY
RATIONALITY
Symptoms that you need a DS
Build the wrong thing Waste of time and resources Months
building before having real clients to learn from
Build the wrong thing Waste of time and resources Months
building before having real clients to learn from
Build the wrong thing Waste of time and resources Months
building before having real clients to learn from
Build the wrong thing Waste of time and resources Months
building before having real clients to learn from
! Understand Diverge Converge Prototype Test
Understand
Ideal
CUSTOMER has a lot of data from market research has
a product already, with analytics has related products where to get customer data from is expert in the area, or brings one
What we usually have
CUSTOMER has little to no data bases decisions on assumptions
is just starting the business and is not the expert we would want him to be
What we can do to help
COMPANY base all ideas on data point out and question
assumptions gather as much real world data and expertise as possible CUSTOMER
Warning: If we need more than 2 days of research,
we are NOT ready for a design sprint
How to do it?
Team UX/Product Lead UI Designer Developer Project Manager Client Associate*
Project Manager* *optional
Exercises
Intros Idea Parking Lot Explain agenda and design sprint Pitch
Practice #1 Goals and anti-goals Existing products, competitors and substitutes Facts and assumptions Problem statement (JTBD) Who-do Personas Customer interviews Journey map Daily retrospective (plus/delta) Team drinks
None
None
Diverge
GOAL
Mind mapping Crazy eights Silent critique Storyboard
None
None
CONVERGE
GOAL
Assumptions Table Identify conflicts Testing plan Final storyboard
None
None
PROTOTYPE
GOAL
Physical Marvel or Invision (clickable prototype) Video HTML/CSS
Test !
5 interviews scheduled
Test Plan
While some build the prototype, the rest of the team
can work on getting everything ready for the tests
2 people, 1 talks Practice not asking leading questions Finish
the assumptions board
After the Tests
If everything on the prototype stays and all assumptions are
met, there is a high chance the tests were biased
After the DS
Create a capture document with photos
Things that worked all most some none
Things that worked all most some none most
Tune prototype and get to work
Things that worked all most some none some
Smaller design sprint
Things that worked all most some none none
Start over
TL; DR
Accelerate Learning
Design Sprints