LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestras Condiciones de uso y nuestra Política de privacidad para más información.
LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestra Política de privacidad y nuestras Condiciones de uso para más información.
DESIGN SPRINTTESTING IDEAS AND SOLVING THE BIG PROBLEMS
What is a Design Sprint?
A design sprint is a ﬁve-phase framework that helps answer cri8cal business
ques8ons through rapid prototyping and user tes8ng. Sprints let your team
reach clearly deﬁned goals and deliverables and gain key learnings, quickly. The
process helps spark innova8on, encourage user-centered thinking, align your
team under a shared vision, and get you to product launch faster.
While a Design Sprint requires focus and commitment from a team, it
can provide validated direc8on and reliable input from customers or
users. It should be considered as part of a Product Team’s journey
towards accomplishing its objec8ve rather than a “tax” on produc8vity.
When to do a Sprint?
Answers big ques-ons, provides clarity to the whole team at once
Tests concepts with real users, validates or invalidates assump-ons
Brings teams together to collaborate in a facilitated, user-centric methodology
When a Product Team achieves a previous
objec8ve or a new opportunity arises and
can beneﬁt from the focus a Design Sprint
When a team is formed and needs to
validated a goal and direc8on for future
Some8mes a team can’t get past a current
roadblock and needs to chart a new course
Study the experience, ask the
experts, select a target
Put ideas on paper, mix and
Storyboard concepts, discuss,
vote on a winner
Build something you can test
Put the prototype in front of
users, listen and learn
Did you clarify the goal and
answer any big ques8ons?
What do we do in a Design Sprint?
A Design Sprint is setup as a framework that supports both divergent thinking (free-form crea8ve brainstorming) and convergent thinking (linear,
logical thinking). It is primarily for a small team who is focused on a speciﬁc problem or goal. The end result of a successful Design Sprint is a
clear direc8onal indica8on and validated (or invalidated) concept that can serve as a launching point for a new product, feature or service.
How is this diﬀerent than what we normally do?
The main diﬀerence between a design sprint and our normal product development cycle is that everyone on the team par8cipates evenly in all
aspects of the process and collaborates in a design centric approach.
UNDERSTAND SKETCH DECIDE PROTOTYPE
Phases and Methods
Phase 1 - Deﬁning the Goal
• Set long term goal - Why are we doing this?
• Where do we want to be in 6 months/1 year?
• Should reﬂect team’s principles and aspira8ons
• What ques8ons do we want to answer in this sprint?
• To meet our long term goal, what has to be true?
• Imagine a future where this project fails, what might have
Make a map
• Show user’s moving through experience
• User map to narrow challenge to a speciﬁc target
• On the leW - show users/actors
• On the right - end states
• Should include all major steps
• Tells a story with beginning, middle and end
Interview the experts
• Can be from the team or from outside it
• Everyone takes notes individually
• Use “How Might We” format
• Organize and consolidate notes
Phase 1 - Choosing the Target
Phase 2 - Draw Conclusions
• Everyone makes a list of products or
services to review for inspira8on
• 3 minute demos of each
• Capture ideas as you go - sketch “what
• Sketch solu8on - best idea
• 3 panel storyboards
• Should be self explanatory
• Ugly is ok
• Words ma`er
• Give it a catch 8tle
• Each team member works individually
• Boot-up process:
• Gather notes
• Jot down rough ideas
• Crazy 8’s
Phase 3 - Decision Day
• Hang up sketches in a “Gallery”
• Heat mapping - dots indicate areas of
interest across all concepts
• Quick discussion of highlights for each
• Straw poll - each person votes with a
• Supervote - Decider places ﬁnal vote
• Illustrate each element in the
prototype to show how it will work
• Grid out interac8ons, elements and
Select the Concept Time to build
Phase 4 - Fake it
Phase 5 - Test and Interpret
Prototype for testing
• Prototype can be anything
• Can be working code or mockups
• Should be disposable, nothing sacred
• Build enough to learn, no more
• Must be realis8c
Interview and learn
• Talk to users
• Gather feedback
• Test against ini8al ques8ons
• Look for pa`erns
• Debrief and learn as a team
Test with users
At the end of the sprint its important to understand what to do with
what you learned. Usually there is a clear path forward but its
important to take a few key cons8tuencies into account as well as
ﬁguring out next steps as a team.
The main focus of the 5th phase is
tes8ng with users and gehng
real-8me feedback on design and
Gehng feedback from leadership
can be cri8cal, even early on in
the sprint process
If you don’t have a developer on
the team (which you should) or if
you need addi8onal valida8on
from an engineer make sure you
bring them into the process.
RECAP AND NEXT STEPS
Sit down as a team and discuss
how to proceed. Typically
technology spikes and addi8onal
design experiments will be clear.
A design sprint is a ﬁve-phase framework that helps answer cri8cal
business ques8ons through rapid prototyping and user tes8ng.
Sprints let your team reach clearly deﬁned goals and deliverables and
gain key learnings, quickly. The process helps spark innova8on,
encourage user-centered thinking, align your team under a shared
vision, and get you to product launch faster.
HOW MIGHT WE
take the insights and pain points and
reframe them as opportuni8es
Dive deep into the user’s experience
Deﬁne step by step what you will build
Sprint Book on Amazon
ESTABLISH A GOAL
Set long term goal - Why are we doing this?
Where do we want to be in 6 months/1 year?
Should reﬂect team’s principles and aspira-ons