Designing the right product Michele Ide-Smith, @micheleidesmith - - PowerPoint PPT Presentation

designing the right product
SMART_READER_LITE
LIVE PREVIEW

Designing the right product Michele Ide-Smith, @micheleidesmith - - PowerPoint PPT Presentation

Designing the right product Michele Ide-Smith, @micheleidesmith Senior UX Architect University of Cambridge @micheleidesmith | #GOTOBer A cautionary tale In 2002 I worked on a mobile (WAP) application. Over several weeks We


slide-1
SLIDE 1

@micheleidesmith | #GOTOBer

Designing the right product

Michele Ide-Smith, @micheleidesmith Senior UX Architect University of Cambridge

slide-2
SLIDE 2

@micheleidesmith | #GOTOBer

A cautionary tale

  • In 2002 I worked on a mobile (WAP)
  • application. Over several weeks…

– We discussed requirements – I designed user flows and crafted wireframes – We created a working prototype – We did lots of internal testing

  • Then we launched the product…
slide-3
SLIDE 3

@micheleidesmith | #GOTOBer

We may as well have built one of these…

Photo by Steve Way: http://www.flickr.com/photos/steve_way/3409302647/

slide-4
SLIDE 4

@micheleidesmith | #GOTOBer

We made a lot of assumptions

slide-5
SLIDE 5

@micheleidesmith | #GOTOBer

We didn’t validate our assumptions

slide-6
SLIDE 6

@micheleidesmith | #GOTOBer

We didn’t do any research with customers

slide-7
SLIDE 7

@micheleidesmith | #GOTOBer

“Unfortunately, we again made the mistake

  • f focusing on engineering first and

customer development second…We released our first version to some moderate success and then proceeded to continue to churn out features without really understanding customer needs.” Devver Blog – Lessons Learned

slide-8
SLIDE 8

@micheleidesmith | #GOTOBer

It’s tempting to design a product with loads of really cool features.

slide-9
SLIDE 9

@micheleidesmith | #GOTOBer

But in reality your users will only use a handful of useful features

slide-10
SLIDE 10

@micheleidesmith | #GOTOBer

% Software features used

20 50 30

Used Never used Rarely used Source: Standish Chaos Manifesto 2013

slide-11
SLIDE 11

@micheleidesmith | #GOTOBer

“ There is no doubt that focusing

  • n the 20% of the

features that give you 80% of the value will maximize the investment in software development and improve overall user satisfaction.” Standish Chaos Manifesto

slide-12
SLIDE 12

@micheleidesmith | #GOTOBer

An evolution of thinking…

slide-13
SLIDE 13

@micheleidesmith | #GOTOBer

Lean: deliver value to customers, minimising waste in the production process

Photo by Toyota Material Handling http://www.flickr.com/photos/toyotamheurope/8472007819

slide-14
SLIDE 14

@micheleidesmith | #GOTOBer

slide-15
SLIDE 15

@micheleidesmith | #GOTOBer

“There are no facts inside your building, so get outside” Steve Blank & Bob Dorf

slide-16
SLIDE 16

@micheleidesmith | #GOTOBer

“The question is not “Can this product be built?” Instead, the questions are "Should this product be built? "” Eric Ries

slide-17
SLIDE 17

@micheleidesmith | #GOTOBer

Principles of Lean Startup

  • Eliminate uncertainty
  • Work smarter, not harder
  • Develop an MVP (Minimum

Viable Product)

  • Validated learning
slide-18
SLIDE 18

@micheleidesmith | #GOTOBer Ideas Build Code Measure Data Learn

slide-19
SLIDE 19

@micheleidesmith | #GOTOBer

“Lean UX is the practice of bringing the true nature of our work to light faster, with less emphasis on deliverables and greater focus on the actual experience being designed.” Jeff Gothelf

slide-20
SLIDE 20

@micheleidesmith | #GOTOBer

Principles of Lean UX

  • Cross-functional teams
  • Outcomes, not output
  • Continuous discovery
  • GOOB: user-centricity
  • Shared understanding
  • Externalising your work
  • Making over analysis
  • Getting out of the deliverables business
slide-21
SLIDE 21

@micheleidesmith | #GOTOBer

Think Make Check

Reduce cycle time, not build time Design research Competitor Analysis Personas Ideation Hypothesis Sketching Prototyping Coding Usability testing A/B testing Analytics

slide-22
SLIDE 22

@micheleidesmith | #GOTOBer

“Requirements are assumptions.” Jeff Gothelf

slide-23
SLIDE 23

@micheleidesmith | #GOTOBer

Some case studies…

slide-24
SLIDE 24

@micheleidesmith | #GOTOBer

“We wanted to make sure we were getting customer feedback as we worked so that we were never working

  • n anything that wasn’t valued by the customer.”

Nordstrom Innovation Lab: Sunglasses iPad App

Photo by Prayitno http://www.flickr.com/photos/34128007@N04/5279860498

slide-25
SLIDE 25

@micheleidesmith | #GOTOBer

Case Study #2

slide-26
SLIDE 26

@micheleidesmith | #GOTOBer

Hypothesis: Oracle Developers & DBAs need a better way to source control their database schemas >70% interest – develop a tool a.s.a.p.

Photo by Paigggeyy http://www.flickr.com/photos/paigggeyy/5533236567

slide-27
SLIDE 27

@micheleidesmith | #GOTOBer

slide-28
SLIDE 28

@micheleidesmith | #GOTOBer

25 feedback sessions with users

slide-29
SLIDE 29

@micheleidesmith | #GOTOBer

Continual validation of assumptions through surveys, interviews and testing

slide-30
SLIDE 30

@micheleidesmith | #GOTOBer

Think Make Check

Reduce cycle time, not build time Design research Competitor Analysis Personas Ideation Hypothesis Sketching Prototyping Coding Usability testing A/B testing Analytics

slide-31
SLIDE 31

@micheleidesmith | #GOTOBer

Get the team on the same page

  • Why are we doing this?
  • Who are building this for?
  • How will we know if we have succeeded?
slide-32
SLIDE 32

@micheleidesmith | #GOTOBer

State your assumptions!

  • Review your user stories or requirements
  • Which ones do you know to be true?
  • Which assumptions pose the biggest risk?
slide-33
SLIDE 33

@micheleidesmith | #GOTOBer

Create a one page plan

Put it up where everyone can see it!

slide-34
SLIDE 34

@micheleidesmith | #GOTOBer

“Design is problem solving. Design research is problem seeking.” Ac4d design library

Photo by Tom Ryan http://www.flickr.com/photos/t0msk/3983980813

slide-35
SLIDE 35

@micheleidesmith | #GOTOBer

“To make excellent products that truly understand our users’ contexts, we must look further, and investigate context first- hand” Cennydd Bowles

slide-36
SLIDE 36

@micheleidesmith | #GOTOBer

How and where will people use your application?

Photo by Phil Dragash http://www.flickr.com/photos/philman/2697665803

slide-37
SLIDE 37

@micheleidesmith | #GOTOBer

Who are they with?

Photo by Jo Shlabotnik http://www.flickr.com/photos/joeshlabotnik/7364192792

slide-38
SLIDE 38

@micheleidesmith | #GOTOBer

Some research methods

  • Observation & contextual interviews

– experience activities in context – observe how people behave – look for pain points and workarounds

  • Surveys
  • Guerilla usability tests

– 5 minutes in a coffee shop

slide-39
SLIDE 39

@micheleidesmith | #GOTOBer

Beware of asking people what they do,

  • r what they want.
slide-40
SLIDE 40

@micheleidesmith | #GOTOBer

Avoid questions like…

  • Which of these features would be useful

to you?

  • How would you like this to work?
  • What would you most like to see in the

product?

  • How do you think we should design this?
slide-41
SLIDE 41

@micheleidesmith | #GOTOBer

“What people say, what people do, and what they say they do are entirely different things.” Margaret Mead, Cultural Anthropologist

slide-42
SLIDE 42

@micheleidesmith | #GOTOBer

Ask questions like…

  • Tell me about the last time you did...
  • What went well? What didn’t go so well?
  • What happened?
  • Why was that?
  • What did you do?
  • Tell me more about that…
slide-43
SLIDE 43

@micheleidesmith | #GOTOBer

Get a shared understanding of user needs and problems. Involve the whole team in research!

slide-44
SLIDE 44

@micheleidesmith | #GOTOBer

Write the things you see or hear on sticky notes.

slide-45
SLIDE 45

@micheleidesmith | #GOTOBer

Group similar sticky notes together and discuss as a team how you will solve those problems for users.

slide-46
SLIDE 46

@micheleidesmith | #GOTOBer

You can’t design for

  • everyone. Personas

represent the main user behaviours you are designing for.

slide-47
SLIDE 47

@micheleidesmith | #GOTOBer

Think Make Check

Reduce cycle time, not build time Design research Competitor Analysis Personas Ideation Hypothesis Sketching Prototyping Coding Usability testing A/B testing Analytics

slide-48
SLIDE 48

@micheleidesmith | #GOTOBer Experiment template by: www.luxr.co | @luxrco

slide-49
SLIDE 49

@micheleidesmith | #GOTOBer

“if the call-to-action button is red then the number of people registering will go up”

www.mindtheproduct.com/2012/08/experiments-101/

slide-50
SLIDE 50

@micheleidesmith | #GOTOBer

Make sure it’s easy to test!

slide-51
SLIDE 51

@micheleidesmith | #GOTOBer

51

Design studio: a lo-fi method to generate lots of ideas quickly, then refine them.

slide-52
SLIDE 52

@micheleidesmith | #GOTOBer

Combine the best ideas and start prototyping

slide-53
SLIDE 53

@micheleidesmith | #GOTOBer

Easy to get feedback and quick to change

Paper prototyping: quick and easy to change before you commit to code

slide-54
SLIDE 54

@micheleidesmith | #GOTOBer

Get designs off the screen and on the walls!

slide-55
SLIDE 55

@micheleidesmith | #GOTOBer

Think Make Check

Reduce cycle time, not build time Design research Competitor Analysis Personas Ideation Hypothesis Sketching Prototyping Coding Usability testing A/B testing Analytics

slide-56
SLIDE 56

@micheleidesmith | #GOTOBer

Validation

  • Usability testing
  • A/B (multi-variant / split) testing
  • Analytics
slide-57
SLIDE 57

@micheleidesmith | #GOTOBer

Closing the feedback loop

  • Get the whole team to observe and

analyse usability test sessions

  • Make usability testing habitual
slide-58
SLIDE 58

@micheleidesmith | #GOTOBer

Summary

  • Treat requirements as assumptions
  • Get out of the building and observe

customers in context

  • Build a shared understanding in the team
  • f customer problems
  • Rapid think > make > check cycles
  • Everyone in the team owns the user

experience of the product!

slide-59
SLIDE 59

@micheleidesmith | #GOTOBer

“Efficiency is doing things right; effectiveness is doing the right thing” Peter Drucker

slide-60
SLIDE 60

@micheleidesmith | #GOTOBer

Michele Ide-Smith Senior User Experience Architect University of Cambridge @micheleidesmith www.ide-smith.co.uk

slide-61
SLIDE 61

@micheleidesmith | #GOTOBer

References

Steve Blank and Bob Dorf, The Startup Owner’s Manual: www.stevenblank.com/startup_index_qty.html Eric Ries, Lean Startup: http://theleanstartup.com Jeff Gothelf and Josh Seiden, Lean UX Book / Hypothesis Template: www.leanuxbook.com Cennydd Bowles, Designing With Context: www.cennydd.co.uk/2013/designing-with-context Nordstrum Innovation Lab: Sunglass iPad App Case Study www.youtube.com/watch?v=szr0ezLyQHY

slide-62
SLIDE 62

@micheleidesmith | #GOTOBer

References

Alexander Osterwalder, Business Model Canvas: www.businessmodelgeneration.com/canvas Ash Mayura, Lean Canvas: http://leanstack.com/ Atlassian, Experience Canvas: http://blogs.atlassian.com/2013/10/fight-the-dark-side-of-lean-ux- with-the-experience-canvas/ Luxr, Experiment Template: www.luxr.co @luxrco