Lock in $30 Savings on PRO—Offer Ends Soon! ⏳
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
780
SI - Module5
zamith
0
79
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
20251209_WAKECareer_生成AIを活用した設計・開発プロセス
syobochim
7
1.5k
AI 駆動開発勉強会 フロントエンド支部 #1 w/あずもば
1ftseabass
PRO
0
350
評価駆動開発で不確実性を制御する - MLflow 3が支えるエージェント開発
databricksjapan
1
170
AWS Trainium3 をちょっと身近に感じたい
bigmuramura
1
140
手動から自動へ、そしてその先へ
moritamasami
0
300
Karate+Database RiderによるAPI自動テスト導入工数をCline+GitLab MCPを使って2割削減を目指す! / 20251206 Kazuki Takahashi
shift_evolve
PRO
1
740
Gemini でコードレビュー知見を見える化
zozotech
PRO
1
250
AWSを使う上で最低限知っておきたいセキュリティ研修を社内で実施した話 ~みんなでやるセキュリティ~
maimyyym
2
420
regrowth_tokyo_2025_securityagent
hiashisan
0
230
Snowflakeでデータ基盤を もう一度作り直すなら / rebuilding-data-platform-with-snowflake
pei0804
5
1.5k
Edge AI Performance on Zephyr Pico vs. Pico 2
iotengineer22
0
140
Power of Kiro : あなたの㌔はパワステ搭載ですか?
r3_yamauchi
PRO
0
120
Featured
See All Featured
Context Engineering - Making Every Token Count
addyosmani
9
510
Side Projects
sachag
455
43k
Building a Modern Day E-commerce SEO Strategy
aleyda
45
8.3k
[SF Ruby Conf 2025] Rails X
palkan
0
510
Why Our Code Smells
bkeepers
PRO
340
57k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
55
3.1k
Fantastic passwords and where to find them - at NoRuKo
philnash
52
3.5k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
31
3k
Speed Design
sergeychernyshev
33
1.4k
Balancing Empowerment & Direction
lara
5
800
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3.2k
BBQ
matthewcrist
89
9.9k
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