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

Developing a Lean UX Practice

Wren Lanier
November 14, 2016

Developing a Lean UX Practice

Presented at Charlotte UX Meetup

Wren Lanier

November 14, 2016
Tweet

More Decks by Wren Lanier

Other Decks in Design

Transcript

  1. Developing a Lean UX Practice
    Senior Product Designer, Windsor Circle
    Wren Lanier
    @heywren

    View Slide

  2. Who I Am
    - Work at Windsor Circle, a startup in Durham
    - Design software for ecommerce marketers
    - UX Team of One
    …I love working on interesting problems

    View Slide

  3. My happy place

    View Slide

  4. Solutions in search of a problem are waste

    View Slide

  5. Reduces waste on design &
    product teams
    Lean UX

    View Slide

  6. Toyota Way (origin of Lean)

    View Slide

  7. Build
    Measure
    Learn

    View Slide

  8. The output of Lean teams is
    validated learning (not deliverables)
    Lean UX

    View Slide

  9. doubt certainty
    Reduce risk, replace it with learning

    View Slide

  10. Continuous validated learning 

    about your users
    Lean UX

    View Slide

  11. Four Lean Habits Anyone Can Adopt

    View Slide

  12. Focus on problems, not solutions
    1

    View Slide

  13. Product Death Cycle 

    by @davidjband

    View Slide

  14. Organizations who have grown up in a
    feature mindset will struggle with the
    shift to customer problems.


    - Jared Spool
    Themes: A Small Change to Product Roadmaps with Large Effects

    View Slide

  15. Develop an efficient research cadence
    2

    View Slide

  16. • Pick a dedicated time for research
    • Same day, same time, every week
    • Divide it into time slots

    View Slide

  17. Use an office hours tool to allow
    users to self-schedule

    View Slide

  18. Committing to weekly research
    keeps your team accountable

    View Slide

  19. Use research to discover problems,
    share experiments, test mockups or
    prototypes

    View Slide

  20. Turn assumptions into hypotheses
    3

    View Slide

  21. • Because people will use this and love it
    • Because our competition built it
    • Because it will cause customers to do [thing]

    View Slide

  22. Assumptions are where risk
    hides in projects

    View Slide

  23. We can reduce risk by testing
    our assumptions

    View Slide

  24. Assumption: 

    Adding links to our daily email will increase logins
    Hypothesis: 

    When we add links to our daily email we will see an
    increase in logins. We will know this is true when we see
    increased click % and increased logins via the daily email.

    View Slide

  25. You can turn almost any piece
    of work into a hypothesis

    View Slide

  26. Test solutions with rapid experiments
    4

    View Slide

  27. An experiment is any low-effort
    way to test an assumption

    View Slide

  28. Experiments should try to
    simulate “real” conditions

    View Slide

  29. Real clients require more
    creativity and more honesty

    View Slide

  30. Usability tests are a great way to
    measure all sorts of things

    View Slide

  31. Run “beta” experiments with
    active customers

    View Slide

  32. Don’t get hung up on statistical
    significance

    View Slide

  33. Be honest about what you’re
    learning & what it means

    View Slide

  34. QUESTIONS?

    View Slide