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
760
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
OpenCensusと歩んだ7年間
bgpat
0
280
【SORACOM UG Explorer 2025】さらなる10年へ ~ SORACOM MVC 発表
soracom
PRO
0
190
CLIPでマルチモーダル画像検索 →とても良い
wm3
2
680
DSPy入門
tomehirata
6
760
AI時代の発信活動 ~技術者として認知してもらうための発信法~ / 20251028 Masaki Okuda
shift_evolve
PRO
1
130
GTC 2025 : 가속되고 있는 미래
inureyes
PRO
0
140
어떤 개발자가 되고 싶은가?
arawn
1
330
新米エンジニアをTech Leadに任命する ー 成長を支える挑戦的な人と組織のマネジメント
naopr
1
320
AIとの協業で実現!レガシーコードをKotlinらしく生まれ変わらせる実践ガイド
zozotech
PRO
2
200
IBC 2025 動画技術関連レポート / IBC 2025 Report
cyberagentdevelopers
PRO
2
230
データとAIで明らかになる、私たちの課題 ~Snowflake MCP,Salesforce MCPに触れて~ / Data and AI Insights
kaonavi
0
200
パフォーマンスチューニングのために普段からできること/Performance Tuning: Daily Practices
fujiwara3
2
180
Featured
See All Featured
Statistics for Hackers
jakevdp
799
220k
Context Engineering - Making Every Token Count
addyosmani
8
320
Writing Fast Ruby
sferik
630
62k
Mobile First: as difficult as doing things right
swwweet
225
10k
Rails Girls Zürich Keynote
gr2m
95
14k
Building Applications with DynamoDB
mza
96
6.7k
Agile that works and the tools we love
rasmusluckow
331
21k
The Art of Programming - Codeland 2020
erikaheidi
56
14k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
46
7.7k
Being A Developer After 40
akosma
91
590k
Optimizing for Happiness
mojombo
379
70k
Code Review Best Practice
trishagee
72
19k
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