InVision Design Sprints Guidebook
InVision Design Sprints Guidebook
Design Sprints
Facilitation Guide
By Richard Banfield
This guide is drawn from
the book Enterprise Design
Sprints, written by Richard
Banfield and published on
DesignBetter.Co.
Pre-Sprint Preparation 10
Three Big Questions
Research Requirements
Pro Tip
The info in this guide is intended to give direction while
allowing room to customize your design sprint. Build
on the ideas here and experiment with the best way
to deliver value to your team and organization.
01 02 03
Impartiality and Expects Strong verbal
objectivity and creates and written
high-quality communication
interactions skills
and outputs
04 05 06
Encourages Can resolve More interested
cooperative minor conflicts in asking questions
interactions or overcome than giving
bottlenecks answers
• What was the outcome you wanted to create with this sketch?
Pro Tip
I make a point of telling teams numerous times that
“additive” questions and comments (e.g. Yes, and...)
are what we’ll use as a group to encourage a high
volume of ideas and reduce judgmental thinking.
Leading a design sprint gets easier with practice. After just one
design sprint your facilitation skills will improve significantly.
Give yourself permission to experiment with the tasks and don’t
expect to be a pro right out of the gate.
Before getting into the nuts and bolts of logistics, you’ll want
to address three interconnected questions:
If you can’t get full commitment from key people who you need to
participate in the design sprint, postpone the kickoff date. There’s
nothing more frustrating and distracting for the group than to have
one or two people dropping in and out because of other obligations.
Research Requirements
I recommend:
This is where the rubber meets the road. Here you’ll find useful tips
and to-do’s for each phase/day of your design sprint.
Phase 4: Phase 5:
Build Test
To do’s:
Give a quick Explain what will Consider playing a
introduction to be done on short intro video
the process. each day. like this one
by Jake Knapp.
Pro Tip
Never assume everyone has read the pre-sprint emails
or notes you provided.
To do’s:
Present the agenda Reinforce the importance
numerous times each day. of meeting time limits.
Pro Tip
Use your smartphone’s timer to set alarms for
each exercise.
Pro Tip
Don’t forget to take photos of all the work you do. Even if
you’re taking notes, a visual reference of all the experience
maps, personas, Jobs To Be Done, or Who/Do will be
extremely valuable.
Expert Input
To do’s:
Use your pre- Read out Encourage
sprint interviews survey answers participants take
to seed or pain-point the insights and
the Diverge descriptions. improvise.
conversations.
Pro Tip
Encourage participants to look around and take inspiration
from the ideas of others.
Sticky Notes
To do’s:
Ensure that all ideas are Display sticky notes on
written or drawn on a sticky appropriate boards.
note (one idea per sticky).
Storyboarding
Initially this task might go slower than anticipated. Warm up the team
by asking them to do a rough sketch first and then start with the
detailed storyboard exercise.
Pro Tip
Plan extra time for participants who find drawing
especially challenging.
Choosing one idea over another can get personal. You don’t
want that.
To do’s:
Explain that the decision Display voting clearly
is based on voting, not a so everyone can see how
single opinion. it played out.
Pro Tip
Use a timer to ensure nobody blows through a 2-3 minute
time limit.
To do:
Create a parking lot or pipeline where ideas that don’t make
the cut are preserved for the future.
Recruit Early
Lining up test subjects in advance early makes the Build phase less
stressful. This is especially true of projects that need to be tested
with senior executives or customers.
To do:
Depending on the team size assign one or two people to recruit
test subjects in advance of the Build phase.
Make sure everyone has a clear role to play during the Build
phase. If necessary, create printouts for the team roles so there’s
no confusion.
To do’s:
Designers Testers need to Recruiters need
need to create develop interview to organize test
prototypes. questions. subjects and
scheduling.
Pro Tip
Nudge the team to prototype solutions that include
interaction or service-experience models. For example,
the team can set up role-playing scenarios where they are
the service providers and test subjects are the customers.
Conflict Resolution
To do’s:
Make sure note takers and Label and upload Screenflow,
interviewers convene for a few video and/or audio recordings
minutes after each interview after each interview.
to discuss the feedback.
Pro Tip
If test subjects begin to ramble on about their experiences
you can redirect them by thanking them and then asking
direct questions like, “Thanks for your feedback. Let’s table
that for now and go back to this specific feature,” or “You’ve
given us way more than we anticipated. Can we shift gears
and talk about XYZ?”