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

Designing with Data

196a4242eecbd120dcb4cd9a80899e34?s=47 Ben Holliday
September 25, 2015

Designing with Data

Presentation for service managers and product owners.


Ben Holliday

September 25, 2015


  1. Ben Holliday Designing with data Ben Holliday
 Head of User

  2. Ben Holliday Design is not about how things look. It’s

    about how things work
  3. Ben Holliday User experience is 
 the responsibility 

  4. Ben Holliday First, some stories about trial and error…

  5. Ben Holliday Hans Monderman (1945 - 2008)

  6. 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”
  7. Ben Holliday

  8. 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”
  9. Ben Holliday gov.uk/design-principles

  10. Ben Holliday

  11. Ben Holliday We’re not great at predicting what will work

    so we need 
 to iterate
  12. Ben Holliday

  13. Ben Holliday

  14. Ben Holliday User research isn’t about making sure we’re right

    all the time, but it means that we’re never just guessing
  15. Ben Holliday

  16. 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
  17. Ben Holliday userresearch.blog.gov.uk/metrics-that-matter-and-user-research

  18. Ben Holliday gov.uk/performance

  19. Ben Holliday A minimum viable product is the smallest release

    that we believe will start delivering the outcomes we’re looking for
  20. Ben Holliday Analytics shows you what’s happening User research can

    help you understand why
  21. Ben Holliday When you cross the street, you remove data,

    anything but the big truck Nassim Taleb (Antifragile)
  22. Ben Holliday All design is hypothesis- driven design

  23. Ben Holliday Because I think [this] is true 

    think that doing [this] 
 will mean [this will happen]
  24. Ben Holliday

  25. 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)
  26. 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]
  27. Ben Holliday

  28. Ben Holliday Successful products 
 come from countless small acts

    of failure
  29. Ben Holliday Look for good experiments with the most gain

    and the 
 lowest risk
  30. 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
  31. Ben Holliday @benholliday ben.holliday@dwp.gsi.gov.uk