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
150
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
690
SI - Module5
zamith
0
69
Continuous learning, teaching and the art of improving yourself
zamith
0
130
Crystal Clean
zamith
2
220
Clean Code
zamith
3
190
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
トラシューアニマルになろう ~開発者だからこそできる、安定したサービス作りの秘訣~
jacopen
2
1.5k
スタートアップ1人目QAエンジニアが QAチームを立ち上げ、“個”からチーム、 そして“組織”に成長するまで / How to set up QA team at reiwatravel
mii3king
1
1.1k
リーダブルテストコード 〜メンテナンスしやすい テストコードを作成する方法を考える〜 #DevSumi #DevSumiB / Readable test code
nihonbuson
11
5.8k
[2025-02-07]生成AIで変える問い合わせの未来 〜チームグローバル化の香りを添えて〜
tosite
1
290
技術的負債解消の取り組みと専門チームのお話 #技術的負債_Findy
bengo4com
1
1.2k
30分でわかる『アジャイルデータモデリング』
hanon52_
9
2.2k
まだ間に合う! エンジニアのための生成AIアプリ開発入門 on AWS
minorun365
PRO
4
580
組織貢献をするフリーランスエンジニアという生き方
n_takehata
1
1k
明日からできる!技術的負債の返済を加速するための実践ガイド~『ホットペッパービューティー』の事例をもとに~
recruitengineers
PRO
3
100
サーバーレスアーキテクチャと生成AIの融合 / Serverless Meets Generative AI
_kensh
12
3k
Developer Summit 2025 [14-D-1] Yuki Hattori
yuhattor
19
5.1k
データの品質が低いと何が困るのか
kzykmyzw
6
1k
Featured
See All Featured
The World Runs on Bad Software
bkeepers
PRO
67
11k
The MySQL Ecosystem @ GitHub 2015
samlambert
250
12k
RailsConf 2023
tenderlove
29
1k
Facilitating Awesome Meetings
lara
51
6.2k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
114
50k
Product Roadmaps are Hard
iamctodd
PRO
50
11k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
366
25k
Making the Leap to Tech Lead
cromwellryan
133
9.1k
Being A Developer After 40
akosma
89
590k
Gamification - CAS2011
davidbonilla
80
5.1k
Building Applications with DynamoDB
mza
93
6.2k
Code Reviewing Like a Champion
maltzj
521
39k
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