design sprint info deck
TRANSCRIPT
Design Sprintby Google Ventures
The sprint is a five-dayprocess for answering
critical business questionsthrough design, prototyping,
and testing ideas withcustomers.
Why and Who?Design Sprint
Why do it? Who is needed? Basic rules?
It's quick and in-expensiveway to learn about importantmarket problems or validatenew ideasYou create cross functionalteam where every participantfeels attached to a problemyou all try to solve It beats opinions as everybodysees real response from thereal people It encourages team work -everyone could see the valueof others so as struggles theyhave
A facilitatorA designerA CEO (could beanybody with a realdecision power)A product managerA user expertAn EngineerA MarketerAnybody else who’sinterested
5 day processSet the stage1 day: Unpack the problem2 day: First sketches3 day: Decide4 day: Prototype5 day: Test with real peopleMain objective is to get anactionable solution out of thesprint
Unpackthe
problem
Sketchthe
solutions
Decideon
solution
Prototypethe
solution
Test thesolution
Dig into problemEverybody bringsall data they canfind on theproblem
Outcomeof the day
Everybody knows everything about the problem
Sketch as manysolutions aspossibleDraw, mind map,note, storyboard,crazy 8
Outcomeof the day
Tons of solution sketches
Decide on bestsolution(s)"Best shot" or"Battle Royal"
Outcomeof the day
One or few best solutions
PrototypeAll shouldcontribute
Outcomeof the day
Prototype
Test with realpeoplePeople not fromyour companyEntire teamwatches and takenotes
Outcomeof the day
Knowledge
Unpackthe
problem
Exercises
Outcomeof the day
Everybody knows everything about the problem
Business opportunity: The CEO or product leader should walkthe sprint team through the business opportunity and market.Lightning demos: Look at competitors’ products, look at non-competitive products that solve a similar kind of problem in adifferent market.Lay it out: Print out all the important screens in your product, layit out, and walk through it as a user would.Success metrics: How will you measure the success of thisdesign?Existing research: whatever data you do know about yourcustomers.Team interviews: go around interviewing people at thecompany who have specific expertise.Analytics: Look at any data you have.
DoNote everything"How might we"formatDraw picturesSKETCH THEMOSTIMPORTANT USERSTORY
Source
Exercises
Choose part of the problem: Everybody focus on the same partof the problem. Faster cycles.Notes: If not already, capture all ideas in notes.Mind map: Mix up ideas and notes to create a structured "cheatsheet" for later UI sketches."Crazy 8": Everybody takes a sheet of paper, folds it in half 4times. Draw 8 sketches on each panel.Storyboard: Everybody sketch an actual UI. Work independentlyor in groups, share anonymously.Silent critique: Everybody looks at different storyboards and puta sticker on every idea or part of the idea that they like. No limiton amount of stickers.Three-minute critique: Each person speaks about eachstoryboard. First what they liked, then if something is missing.Most popular ideas do not need explanation.
DoPaper firstWork individuallyor in groupsSticky note"Super Vote" ifneeded
Source
Sketchthe
solutions
Outcomeof the day
Tons of solution sketches
5 min
15 min
5 min
20 min
10 min
3 min/idea
Exercises
Search for conflicts: Two or more approaches to solve thesame problem. Each conflict is a gold mine."Best shot" or "Battle Royale": Either choose one, best solutionto test ("Best shot") or, if not possible, select few best solutionsfor the "Battle royale" - test them all.Test your assumptions: Write down all your majorassumptions and the ways you will validate them.Whiteboard the user story: Draw final storyboard that will be aspec for your prototype. Get one person to draw, but othersshould help.
DoCombat the groupeffectMake decisions(don't hide behind"Battle royal")
Source
Decideon
solution
Outcomeof the day
One or few best solutions
Exercises
Make it minimally real: Prototype does not need to be pixelperfect. It needs to be believable.Write real text: Forget "lorem ipsum". Use real text, made it up.Prototyping tools vs code: Use tools that will allow you tocreate a prototype in a shortest time possible.Divide and conquer: Everybody should be able to help withprototype creation. Divide work.Build an asset library: Build a template slide deck. Includeanything that everyone will need — screenshots, user avatars,logos, formatted text; whatever you think might help.Review with an outsider: Schedule 30 minutes with someonewho is not doing design work today. The outside eyes will helpprevent you from going too far down any groupthink rabbitholes.
DoKeynote(PowerPoint) arethe bestprototyping toolsAppoint an emailsheriffPointers, text,browser bar andother finaltouches
Source
Prototypethe
solution
Outcomeof the day
Prototype
Exercises
List your key questions: The interviewer and the observersshould make a list of the key questions for the day.Set up the observation room: Everybody who participated inthe sprint should be in the room. There’s no substitute forwatching real humans use your product, and this is a goldenopportunity to do it!Every observer takes notes: Everybody should take notes onthings they see during the interviews: good, bad, and other.Insist on paper note-taking — it’s best to keep laptops closed,lest you lose your fellow observers to email..Make a scoreboard: Clear one big whiteboard to collect thegroup’s notes. Make a column for each participant and a row foreach part of the interview (e.g. background, first prototype,second prototype, etc).“Things that work” and “Problems to solve”: These are yourtop-line findings. The CEO or decider for the project shouldbless that list before you leave the room.
DoDon’t diss theuserDesignate a courtreporterNext sprint, it willbe easier
Source
Test thesolution
Outcomeof the day
Knowledge
Design SprintWar chest
Remember Ingridients
PICK A BIG FIGHTGET THE RIGHT PEOPLESCHEDULE THE USER STUDYBEFORE YOU HAVE ANYTHINGTO TEST
Sticky notesDrawing pensWhiteboardsWhiteboard markersDot stickersBlank copy paperTime Timer ClockSnacksSticky stuff
Resources that were used to create this info deck
How To Conduct Your Own Google Ventures DesignSprint
The 6 Ingredients You Need To Run A Design Sprint
Lean more about the Design Sprint
The Design Sprint
www.test-n-tell.com