22
WELCOME Dean (@deanmalmgren) Mike (@mstringer) Laurie (@laurieskelly)

Design thinking for dummies (data scientists)

Embed Size (px)

DESCRIPTION

These are our slides from our Strata 2014 (Santa Clara) workshop.

Citation preview

Page 1: Design thinking for dummies (data scientists)

WELCOMEDean (@deanmalmgren)

Mike (@mstringer)Laurie (@laurieskelly)

Page 2: Design thinking for dummies (data scientists)

WHY DESIGN?

Page 3: Design thinking for dummies (data scientists)

INTERVIEWEXPLORESYNTHESIZESKETCHOBSERVEPROTOTYPE

FORM GROUPS

Page 4: Design thinking for dummies (data scientists)

INTERVIEW

Page 5: Design thinking for dummies (data scientists)

INTERVIEW

listen carefullybe thoughtful, ask why, dig deepempathy is key

10 MINUTES

Page 6: Design thinking for dummies (data scientists)

INTERVIEWWHEN DATA IS INVOLVED

• Learn about the nuances of a problem• What makes this relevant for humans?• Who uses it and why?

Page 7: Design thinking for dummies (data scientists)

EXPLORE

Page 8: Design thinking for dummies (data scientists)

EXPLORE

build on others thoughtsprefer radical ideasone mouth at a time

20 MINUTES

Page 9: Design thinking for dummies (data scientists)

EXPLOREWHEN DATA IS INVOLVED

• Have the attitude that “anything is possible (eventually)”• Don’t focus too much on the details of the data or analysis• Speak the language of the problem, not the solution

Page 10: Design thinking for dummies (data scientists)

SYNTHESIZE

Page 11: Design thinking for dummies (data scientists)

SYNTHESIZE

clump post-its in groupsstars will force a decisionmistakes are OK

15 MINUTES

Page 12: Design thinking for dummies (data scientists)

SYNTHESIZEWHEN DATA IS INVOLVED

• Tweak or discard clearly infeasible ideas• But still focus on usefulness, not feasibility

Page 13: Design thinking for dummies (data scientists)

SKETCH

Page 14: Design thinking for dummies (data scientists)

SKETCH

sketch out your conceptsignore distracting detailsugly is just !ine

20 MINUTES

Page 15: Design thinking for dummies (data scientists)

SKETCHWHEN DATA IS INVOLVED

• Usually sketch many times before writing any code• Make sure concept addresses one use case well• Use finer tipped markers, pens, and pencils for more detail• Build even more refined wireframes with inkscape/photoshop• Keep using the language of the problem owners, not nerd speak.

Page 16: Design thinking for dummies (data scientists)

OBSERVE

Page 17: Design thinking for dummies (data scientists)

OBSERVE

observe carefullydon’t defend, they’re helping youempathy is key

10 MINUTES

Page 18: Design thinking for dummies (data scientists)

OBSERVE

• Understand which parts of concept are useful or not (and why!)• Ask for suggestions and questions

WHEN DATA IS INVOLVED

Page 19: Design thinking for dummies (data scientists)

PROTOTYPE

Page 20: Design thinking for dummies (data scientists)

PROTOTYPE

make your concept realit’s not the !inished productbuild for more feedback

40 MINUTES

Page 21: Design thinking for dummies (data scientists)

PROTOTYPEWHEN DATA IS INVOLVED

• This involves getting data, doing some analysis, and presenting results• Short iteration cycle forces you to focus on essential parts• Important thing is to start building trust with end users• The details of feasibility come up here• It’s OK to fail; you’ve got lots of good ideas on the backburner

Page 22: Design thinking for dummies (data scientists)

THANKSDean (@deanmalmgren)

Mike (@mstringer)Laurie (@laurieskelly)