Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo
March 11, 2013


Lean UX for
Agile Teams
    Jeff Gothelf
   Josh Seiden
  www.neo.com
Me and my #hashtags


Josh Seiden
www.neo.com
@jseiden
@neo_innovation

#leanUX
#leanStartup
Internet Mouse
The Lean UX Cycle
State	
  your	
  desired	
  outcomes
                                                        Ideas
Declare	
  your	
  assump2ons
Hypothesize:	
  write	
  the	
  test	
  first   Learn              Build
Design	
  an	
  Experiment	
  
Make	
  an	
  MVP
Get	
  out	
  of	
  the	
  building
Team	
  synthesis                              Data              Product
Repeat
                                                       Measure
AGENDA
1. MANAGE OUTCOMES
2. FREEDOM TO EXPERIMENT
3. CONTINUOUS LEARNING



                           5
1
MANAGE 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%
Lean UX for Agile Teams
Lean UX for Agile Teams
Case Study: TheLadders




               63%
2
FREEDOM TO EXPERIMENT



                        15
Kill
Pivot
Double-down
2. Freedom to experiment….and fail



1.   Run small, low-risk experiments
2.   Refine your hypotheses
3.   Reward learning (aka failure)
4.   Make decisions based on objective
     observations
Case Study: Social Media Benchmarking
Observed: Small business owners want to use social media
for marketing but don’t know how.


Hypothesis: They would pay for a service that provides
benchmarking 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
3
CONTINUOUS LEARNING



                      27
Reduce Inventory, Risk and Waste

            This is             No one
           going to             clicked.
           be BIG!




Make a
design                MONTHS              Get feedback
                                          from market
decision




                      HOURS      Concept credit: @clevergirl
A system built on continuous learning


                               Risk




                                      Learning!




Diagram concept: @clevergirl                      29
3. Continuous learning




1.   Instrument your software to measure usage
2.   Build a process that includes the customer
     (regularly)
3.   Combine the what (quantitative) with the
     why (qualitative) for a holistic view of your
     product
AGENDA
1. MANAGE OUTCOMES
2. FREEDOM TO EXPERIMENT
3. CONTINUOUS LEARNING



                           31
THANK YOU!
@jboogie | @jseiden
www.leanuxbook.com
www.neo.com
                      32

More Related Content

Lean UX for Agile Teams