Web2.0 Presentation on Lean Startups

Preview:

DESCRIPTION

 

Citation preview

@glusman

Beyond 2 guys in a garage

1

Lean startup lessons for any sized company

@glusman 2

@glusman 3

Meetup helps you meet the people you want to meet who are doing the things you want to do

@glusman

@glusman

the most likely

@glusman

95% of new initiatives fail à 5% success�

@glusman

95% of new initiatives fail à 5% success�

90% of new initiatives fail à 10% success�

2X odds of suc

cess�

+ Customer Discovery Interviews�+ MVP�+ Iterative Development �+ Usability Testing �+ Split Testing �+ 5 Why Analysis + Customer Advisory Board + Smoke Tests + etc

@glusman

Still fail 90% of the time �

@glusman

FAIL FAIL

FAIL FAIL

FAIL FAIL

FAIL FAIL

SUCCESS FAIL

@glusman

Not starting from scratch�WHY START FROM SCRATCH?�

@glusman

95% of new initiatives fail à 5% success�

90% of new initiatives fail à 10% success�

85% of new initiatives fail à 15% success�

2X �

3X �PIVOT: �

@glusman

95% of new initiatives fail à 5% success�

90% of new initiatives fail à 10% success�

85% of new initiatives fail à 15% success�

80% of new initiatives fail à 20% success�

75% of new initiatives fail à 25% success�

2X �

3X �

4X �

5X �

PIVOT: �

PIVOT: �

PIVOT: �

@glusman

Still fail 75% of the time �

1/4 1/10 vs.

@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 �

@glusman

MALKOVICH BIAS:

THE TENDENCY TO BELIEVE THAT EVERYONE USES TECHNOLOGY LIKE YOU DO

@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

“That was humbling” - A developer after a session

@glusman

On pace to do 600-800 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

Do remote tests via gotomeeting

Follow each session with discussion & notes/video

@glusman

“This Group meets the first

Saturday of every month “

@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

DO try this at home….

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.  Do as much as you can in low tech way, then scale

@glusman

@GLUSMAN ANDRES@MEETUP.COM