Design Sprints: my take on the The Google Venture's Way

Post on 10-Nov-2014

525 views 3 download

Tags:

description

In this presentation I have tried to explain the way googleventure's organize design sprints for the startups. I find it very useful specially how they manage to avoid the "design by committee" effect. You may read the whole series in www.gv.com/design-sprints

Transcript of Design Sprints: my take on the The Google Venture's Way

Design Sprints: A Five Day RecipeGoogle Venture’s Way

Novin Andishan Sarava Pars

My Personal Observation

• Startup Weekends

• Real World

• Design by Committee

Novin Andishan Sarava Pars

Till I get to know this guy

Jake Knapp of GV

Novin Andishan Sarava Pars

The Analogy of a Design Sprint

• Preparation (Before the Sprint)

• Day 1: Understand

• Day 2: Diverge

• Day 3: Decide

• Day 4: Build

• Day 5: Validate

Novin Andishan Sarava Pars

Preparation: who is in the sprint?

• The big boss (CEO, COO, …)

• Designer (if you have any)

• Product Manager (if you have any)

• User Expert

• Engineer

• Anybody else who is interested

Novin Andishan Sarava Pars

Preparation: Create time pressure

• Recruit users before the sprint

• This will help you to commit

• And move faster

• Put it on everyone’s calendar

Sunday WednesdayMonday Tuesday Thursday

Users come in here

Novin Andishan Sarava Pars

Preparation: Find a faci

• You need a hero for this or someone who is really mean

Novin Andishan Sarava Pars

The Ingredients

• Sticky Notes

• Drawing Pens

• Whiteboards

• Whiteboard marker

• Dot stickers

• Blank paper

• Sticky stuff

• Food

Day 1: Understanding

Novin Andishan Sarava Pars

Common Understanding of The Problem

Bring everyone in one page

Instructions:

Ask everyone to talk about their understanding of the problem

Hand everyone “sticky notes”

Novin Andishan Sarava Pars

Things to talk about

• Business opportunity

• Competitors product or services

• Print out of the current product pages

• Success Metrics

• Existing research

• Team interviews

• Analytics

Novin Andishan Sarava Pars

Sketch

• The most important user story

• Which user story is the most important?

Novin Andishan Sarava Pars

Focus

• You can’t prototype everything

Day 2: Diverge

Novin Andishan Sarava Pars

Diverge

• Illuminate all the paths

• Dust of the old ideas

Novin Andishan Sarava Pars

Paper first

• It is fast!

• Everyone can contribute

• Nobody gets attached

Novin Andishan Sarava Pars

Rules

• Choose a part of the user story

• Take the “how could we…” notes

Novin Andishan Sarava Pars

Brainstorm (10-15mins)

• It is an individual brainstorming

Novin Andishan Sarava Pars

Crazy Eights (5 mins)

• 40 sec for each sketch

• Use a thick marker

Novin Andishan Sarava Pars

Storyboard (10-20 mins)

• Take the ideas from the crazy eights

• Draw the UI in 3 frames

• Show a progress: first this, then that, then that.

• Important rules • It has to make sense by itself otherwise it is a piece of shit! • Keep it anonymous • Give it a cool name to discuss it later • Hang them side by side like an art gallery

Novin Andishan Sarava Pars

Draw the UI in 3 frames Show a progress: first this, then that, then that.

Novin Andishan Sarava Pars

Art Gallery

Novin Andishan Sarava Pars

Silent Critique (5-10 mins)

• Dot Stickers, dots, …

• No limit for votes

Novin Andishan Sarava Pars

Critique per idea (3mins)

• People talk

• Then ask the owner

Novin Andishan Sarava Pars

Super Vote (5 mins)

• Give decider the vote

Day 3: Decide

Novin Andishan Sarava Pars

Combat the Group Effect

• Call the CEO out

• Look for conflicts, each conflict is like a goldmine

Best Shot Battle Royale

Novin Andishan Sarava Pars

Test Your Assumptions

• List your assumptions • About users • About the business • About technology • About the messaging

Novin Andishan Sarava Pars

Whiteboard the user story

• Click-by-click

• This is the spec

Novin Andishan Sarava Pars

Whiteboard the user story

• Instructions • Draw a big grid • It is a comic book • A single action in each

frame

Novin Andishan Sarava Pars

Don’t Be Nice

• If there are still conflict

Day 4: Prototype

Novin Andishan Sarava Pars

Prototype

• Make it minimally real

• Write real text

• Divide and conquer

• Timebox

• Assign a facebook or email sheriff

• Lightening critique

• Review with an outsider

• Final touches

It is OK Michelangelo

Day 5: Test

Novin Andishan Sarava Pars

Test It with Real Humans

• Start from the end

• Review your conflicts and assumptions

• Show them the competitors products

• It is not a usability test!

Novin Andishan Sarava Pars

Set the Room

• Everybody n the sprints should be in the room

• Don’t diss the user

• Every observer takes notes

• No laptop allowed (just the master note taker)

Novin Andishan Sarava Pars

Make a Scorecard

Novin Andishan Sarava Pars

Take Away

• Create a time pressure

• Get into the prototype mindset

• Get into the quick research mood