• Save
Lean UX for Agile Teams
Upcoming SlideShare
Loading in...5
×
 

Lean UX for Agile Teams

on

  • 2,285 views

My slides from my talk at Agile Austin, March 2013. The talk covered key concepts from the book "Lean UX", written by Jeff Gothelf and me, and available here: www.leanuxbook.com

My slides from my talk at Agile Austin, March 2013. The talk covered key concepts from the book "Lean UX", written by Jeff Gothelf and me, and available here: www.leanuxbook.com

Statistics

Views

Total Views
2,285
Views on SlideShare
2,189
Embed Views
96

Actions

Likes
14
Downloads
0
Comments
0

2 Embeds 96

http://www.bedienhilfe.ch 59
http://www.scoop.it 37

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Lean UX for Agile Teams Lean UX for Agile Teams Presentation Transcript

    • March 11, 2013Lean UX forAgile Teams Jeff Gothelf Josh Seiden www.neo.com
    • Me and my #hashtagsJosh Seidenwww.neo.com@jseiden@neo_innovation#leanUX#leanStartup
    • Internet Mouse
    • The Lean UX CycleState  your  desired  outcomes IdeasDeclare  your  assump2onsHypothesize:  write  the  test  first Learn BuildDesign  an  Experiment  Make  an  MVPGet  out  of  the  buildingTeam  synthesis Data ProductRepeat Measure
    • AGENDA1. MANAGE OUTCOMES2. FREEDOM TO EXPERIMENT3. CONTINUOUS LEARNING 5
    • 1MANAGE OUTCOMES 6
    • Output
    • Outcome
    • Impact
    • Many companies manage to output.Instead, focus on outcomes.Don’t make teams responsible for impact.
    • Case Study: TheLadders 14%
    • Case Study: TheLadders 63%
    • 2FREEDOM TO EXPERIMENT 15
    • Kill
    • Pivot
    • Double-down
    • 2. Freedom to experiment….and fail1. Run small, low-risk experiments2. Refine your hypotheses3. Reward learning (aka failure)4. Make decisions based on objective observations
    • Case Study: Social Media BenchmarkingObserved: Small business owners want to use social mediafor marketing but don’t know how.Hypothesis: They would pay for a service that providesbenchmarking data from their peers. 20
    • What’s the smallest thing we can build? 21
    • Don’t design a product,design an experiment. 22
    • 23
    • 24
    • 25
    • 26
    • 3CONTINUOUS LEARNING 27
    • Reduce Inventory, Risk and Waste This is No one going to clicked. be BIG!Make adesign MONTHS Get feedback from marketdecision HOURS Concept credit: @clevergirl
    • A system built on continuous learning Risk Learning!Diagram concept: @clevergirl 29
    • 3. Continuous learning1. Instrument your software to measure usage2. Build a process that includes the customer (regularly)3. Combine the what (quantitative) with the why (qualitative) for a holistic view of your product
    • AGENDA1. MANAGE OUTCOMES2. FREEDOM TO EXPERIMENT3. CONTINUOUS LEARNING 31
    • THANK YOU!@jboogie | @jseidenwww.leanuxbook.comwww.neo.com 32