Design SprintsPioneered by IDEO, the d.school at Stanford and Google Ventures.

Design Sprints

A framework for how to solve and test big hairy design challenges in 5 days or less.

What you’ll need.

What you’ll need.

1. A design problem.

1. A design problem.

The problem needs to be quantifiable.

1. A problem.

2. A multi-disciplinary team.

What you’ll need.

2. A multi-disciplinary team.

The team needs to represent the business, who will build it and who interacts with the user.

1. A problem.

2. A multi-disciplinary team.

What you’ll need.

3. A war room and provisions.

3. A war room and provisions.

Keep it simple - writing supplies and a whiteboard.

Context Diverge Converge Prototype Test

1 2 3 4 5

How does it work?

Context

1

Context1

What’s the business opportunity?

Context1

What does the problem “look” like?

Context1

What existing research do we have?

Context1

What analytics do we have?

Context1

What do WE know about this problem?

Context1

You’re successful coming out of this meeting if you have a list of constraints to help guide you.

Diverge

2

Wait!Before you can continue, schedule user interviews.

Diverge2

Using constraints, design quick solutions individually.

Diverge2

You know you’re successful after this stage if each person has 1 solution they’re ready to present.

Converge

3

Converge3

Present your best ideas and decide which to build.

Converge3

When presenting, point to constraints and how you’re solving the problem.

Converge3

You know you’re successful after this stage if you have a storyboard outline for your solution.

Prototype

4

Prototype4

Build the least to learn the most.

Prototype4

Use tools like Power Point, Keynote, even sketches.

Prototype4

At the end of this stage, you know you’re successful if you have a working prototype and a test script.

Prototype4

Your test script should use non leading questions to elicit responses from users that relate to the problem.

Test

5

Test5

1-1 user interviews.

Test5

Listen to learn.

Test5

Take notes as a team or record your sessions.

Test5

Not every prototype will be a resounding success.

Test5

Learn without building.

Rinse & Repeat

Iterate.

The end.Hit me up on Twitter or LinkedIn.

https://twitter.com/dmatiaudes

https://www.linkedin.com/in/dmatiaudes

Resources:

http://www.gv.com/sprint/

https://developers.google.com/design-sprint/downloads/DesignSprintMethods.pdf

http://www.fastcodesign.com/1672889/from-google-ventures-the-6-ingredients-you-need-to-run-a-design-sprint

http://www.fastcodesign.com/1672905/the-first-step-in-a-design-challenge-build-team-understanding

http://bokardo.com/archives/1-hour-of-research-saves-10-hours-of-development-time/