Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Designing with Data

Ben Holliday
September 25, 2015

Designing with Data

Presentation for service managers and product owners.

Ben Holliday

September 25, 2015
Tweet

More Decks by Ben Holliday

Other Decks in Design

Transcript

  1. Ben Holliday Hans Monderman (1945 - 2008) “The trouble with

    traffic engineers is that when there's a problem with a road, they always try to add something”
  2. Ben Holliday Philip Scranton, Historian “They didn’t know what they

    were doing, but they were willing to fail until they got something that worked”
  3. Ben Holliday User research isn’t about making sure we’re right

    all the time, but it means that we’re never just guessing
  4. Ben Holliday Why are we doing this work? or What

    is our motivation for building this product or service? Who are our users? or Who do we think would need to use this product or service? What outcome will users get from this service? or What problem will it solve for people? What outcome are we looking for? or What problem will it solve for our organisation? What are our key metrics? or What do we need to measure against these outcomes? benholliday.com/frame-the-problem
  5. Ben Holliday A minimum viable product is the smallest release

    that we believe will start delivering the outcomes we’re looking for
  6. Ben Holliday When you cross the street, you remove data,

    anything but the big truck Nassim Taleb (Antifragile)
  7. Ben Holliday Because I think [this] is true 
 I

    think that doing [this] 
 will mean [this will happen]
  8. Ben Holliday Each design is a proposed business solution –

    a hypothesis. Your goal is 
 to validate the proposed solution as efficiently as possible by using customer feedback Jeff Gothelf (Lean UX)
  9. Ben Holliday We believe [this statement is true]. We will

    know we're [right/wrong] when we see the following feedback: [qualitative feedback] and/or [quantitive feedback] and/or 
 [key performance indicator change]
  10. Ben Holliday 1. Measure what's happening 2. Work out why

    3. Design, and iterate solutions 
 with user feedback 4. Write a hypothesis 5. Make a change to your live 
 product or service