agile ux nyc - lessons learn
DESCRIPTION
TRANSCRIPT
@glusman
LESSONS LEARNED
Andres Glusman VP, Strategy & Community Meetup
Co-organizer: NYC Lean Startup Meetup
AGILEUXNY - FEB 2012
@glusman 2
Accidental Lean Startup
1) Agile development with multiple pushes per day
2) Extensive customer development
3) Experiment then double down Customer Development
@glusman
On pace to do 600-800 usability sessions this year
Will cost around $30,000 (less than 1 outsourced usability project)
@glusman
Test 2-3 days a week (t, w, th)
Setup tests prior to knowing what will be tested
Recruit participants from community and through recruiter (compensate for their time)
Use gotomeeting to broadcast sessions to developers
Use silverback to record
Follow each session with discussion & notes/video
@glusman
MALKOVICH BIAS:
THE TENDENCY TO BELIEVE THAT EVERYONE USES TECHNOLOGY LIKE YOU DO
@glusman
@glusman
Watching people use the stuff you build, is the best way to confront the Malkovich Bias
@glusman
Shifts the conversation from how I would use the website to how this user uses the website
@glusman
“This Group meets the first
Saturday of every month “ “This Group
meets the first Saturday of
every month “
“This Group meets the first
Saturday of every month “
“This Group meets the first
Saturday of every month “
@glusman
Testing on our DIY iPhone Rig
Similar approach to iPhone testing
@glusman 10
Lean Startup
1) Agile development with multiple pushes per day
2) Extensive customer development
3) Experiment then double down Experiment then double down
@glusman 11
@glusman 12
@glusman 13
@glusman
Experimenting is more than A/B Testing
@glusman
Long term experiments
15
Every new Organizer on Meetup has a coach on the community team & gets personalized emails from their coach with advice they need based on their situation
Community Coaching
@glusman
How’s work?
16
@glusman
How’d we get here?
17
Only greeted 80% of new Organizers
@glusman
Results
18
No change!
Except….
@glusman
Implemented across the board
19
@glusman
Customer Development lessons learned 1. Give team direct access to customers
2. Look for boulders in the road
3. Substitute frequency for precision
4. Strip out costs wherever possible …but be willing to trade money for time
5. Have discussions
6. Launch & learn
7. Accept that failure is most likely outcome
8. Experiment then double down
@glusman 21
@glusman 22
@glusman 23
PROCESS
@glusman
Just started doing it
@glusman
Snuggle up with failure
@glusman
WHAT WOULD YOU DO IF YOU ASSUMED YOU WOULD FAIL?
@glusman
RUN INTO A BUZZ SAW AS FAST AS WE CAN�
@glusman
GO AFTER THE THINGS THAT WILL CAUSE US TO FAIL AS FAST AND OFTEN AS WE CAN
