The document describes the Design Sprint process, which allows teams to solve design problems and test ideas with customers in 2-5 days. The process involves 5 stages: 1) Understand the problem through research, 2) Diverge by generating many potential solutions through brainstorming techniques, 3) Converge by defining a prototype and assumptions to test, 4) Prototype quickly using paper or digital tools, and 5) Validate by testing the prototype with users and gathering feedback. Design Sprints use methods from Design Thinking to help teams break out of processes and focus on the user perspective to create innovative products.

1. DESIGN SPRINT
HOW TO DESIGN, PROTOTYPE AND TEST PRODUCT IN 5 DAYS
Marian Mota

2. UX Consultant
2.5 years in Eleks, 4 years in SoftServe
30 projects
Team of 5 designers
Traveling, Bike, Comics, Cinema
MARIAN MOTA

3. Design sprints are a process for teams of any size to
solve and test design problems in 2-5 days.
Its answering critical business questions through design,
prototyping, and testing ideas with customers.
DESIGN SPRINT

4. The Design Sprint process, created by Google Ventures,
is rooted in the Design Thinking mindset.
Basically, Design Thinking is a structured way for
product teams break out of the mold of corporate
processes. It’s about involving the perspectives of the
user, business and technology, to provide a way to
create the “next big thing”.
DESIGN SPRINT

5. “Design thinking is a human-
centered approach to
innovation that draws from the
designer's toolkit to integrate
the needs of people, the
possibilities of technology, and
the requirements for business
success.” —Tim Brown,
president and CEO, IDEO
DESIGN THINKING

6. DESIGN SPRINT

7. What problems, needs, and motivations do people have?
Do people understand your product’s value proposition?
Which messages are most effective at explaining your
product?
Can people figure out how to use your product?
Why do people stop using your product?
Why don’t people adopt new features when you launch
them?
DESIGN SPRINT

8. DESIGN SPRINT
IS SUPER FAST

9. Understand Diverge Converge Prototype Test
DESIGN SPRINT

10. Each of the stages can include design best practices,
known as methods, such as “user interviews” or
“competitive reviews.”
There are more than 40 possible methods, and you
never need to use all of them. Select the right methods
for your sprint, or add and invent your own best
practices.
DESIGN SPRINT

11. DAY 0
Select and invite the sprint team
Prepare the sprint room
Prepare the supplies
Gather data

12. DESIGN ROOM
Your own Design War Room with
Whiteboards, rolling desk, etc.

13. SUPPLIES
Sharpies, paper, tape, sticky notes, voting
dots, a timer

14. TEAM
The sprint team should include designers,
engineers, product managers and experts.

15. 1. UNDERSTAND
Understand who the target audience is. Come to a common
understanding of the goal and business opportunity for the
sprint. Agree upon what success will look like and how it will be
measured.

17. Name Behaviors
Needs and GoalsFacts and
Demographics

20. COMPETITORS

21. DESIGN PRINCIPLES

22. Imagine it’s time to launch your
product. What is the first announcing
tweet you will send out?
FIRST TWEET

23. 2. DIVERGE
The purpose of these activities will be to generate insights and
churn out many possible solutions to address the Problem
Statement.
Individual and group Mind Mapping
Rapid iterative individual sketching or “Crazy 8s”
Storyboarding
Silent Critique and vote (5-10 minutes)
Repeat

24. SKETCH THE MOST
IMPORTANT USER STORY
Highlights the story most critical to the
challenge at hand. Where does your
customer start, where should they end up
and what needs to happen along the way?

25. CRAZY EIGHTS
Give everyone a sheet of paper and ask
them to fold it 3 times 1 min
Ask the team to unfold the paper and
notice the 8 grid rectangle created.
Ask them to sketch 8 ideas in 5 mins, one in
each rectangle.

26. STORYBOARD

27. SILENT CRITIQUE
This allows everyone to form their own
opinions before they get biased by others.

28. 3-MINUTE CRITIQUES (3
MINUTES PER IDEA)
At this point, the team can discuss the best
ideas and decide which ones to prototype.

29. 3. CONVERGE
Define a minimal viable product and decide what to test
and prototype.
Identify conflicts
Eliminate solutions that can’t be pursued
List out assumptions
Identify how each assumption will be tested
Create a prototype storyboard to define what needs to be
prototyped
Write user test script

31. ASSUMPTIONS

33. STORYBOARD
a comic book-style story of your customer moving
through the previously-defined critical path. The
storyboard is the blueprint for the prototype

34. Low cost rapid way of gaining insights about what the product
needs to be
The end results will help the team understand what is working
and what is not
4.PROTOTYPE

35. TYPES
Paper prototypes
Keynote
Wireframes
Interactive prototypes, like InVision, Marvel, POP,
Origami, Pixate
Axure
HTML+CSS

36. SKETCH

37. INVISION

38. User test
Stakeholder feedback
Technical feasibility check
5.VALIDATE

39. Test with at least 4 people
Test people individually
Prepare questions in advance
Observe and take notes, record if you can.
Use understandable language.
The results may not match your expectations
USER TEST

40. Observe and interview customers as they interact with
your prototype.
Observe and interview customers as they interact with
competitive products.
Debrief with the team of the day’s testing sessions
USER TEST

41. We're testing the software, not
you
USER TEST

42. Sketch
InVision
QuickTime
Join.Me
Evernote
TOOLS

43. YOU’VE FINISHED YOUR
DESIGN SPRINT! NOW
WHAT?
Most stuff worked
Some big questions
Everything exploded

44. MATERIALS
http://bit.ly/1bVi7ke