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
740
SI - Module5
zamith
0
75
Continuous learning, teaching and the art of improving yourself
zamith
0
130
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
[OCI Technical Deep Dive] OracleのAI戦略(2025年8月5日開催)
oracle4engineer
PRO
1
260
自治体職員がガバクラの AWS 閉域ネットワークを理解するのにやって良かった個人検証環境
takeda_h
2
370
Android Studio の 新しいAI機能を試してみよう / Try out the new AI features in Android Studio
yanzm
0
240
会社にデータエンジニアがいることでできるようになること
10xinc
9
1.5k
広島発!スタートアップ開発の裏側
tsankyo
0
190
人と組織に偏重したEMへのアンチテーゼ──なぜ、EMに設計力が必要なのか/An antithesis to the overemphasis of people and organizations in EM
dskst
1
140
夢の印税生活 / Life on Royalties
tmtms
0
270
モノレポにおけるエラー管理 ~Runbook自動生成とチームメンションの最適化
biwashi
0
520
[OCI Skill Mapping] AWSユーザーのためのOCI(2025年8月20日開催)
oracle4engineer
PRO
2
110
AIドリブンのソフトウェア開発 - うまいやり方とまずいやり方
okdt
PRO
9
510
ECS モニタリング手法大整理
yendoooo
1
110
Goでマークダウンの独自記法を実装する
lag129
0
200
Featured
See All Featured
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Fireside Chat
paigeccino
39
3.6k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.8k
A better future with KSS
kneath
239
17k
How STYLIGHT went responsive
nonsquared
100
5.7k
GitHub's CSS Performance
jonrohan
1031
460k
Faster Mobile Websites
deanohume
309
31k
Unsuck your backbone
ammeep
671
58k
Docker and Python
trallard
45
3.5k
Practical Orchestrator
shlominoach
190
11k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
110
20k
XXLCSS - How to scale CSS and keep your sanity
sugarenia
248
1.3M
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