1. What Is Lean?
Jonathan Irwin
Managing Director & Advisor
Neo San Francisco
jonathan.irwin@neo.com
@jonathanirwin
Thursday, January 30, 14
2. is 83 people.
43 engineers.
15 designers.
10 product leaders (like me).
and some overhead.
We advise.
And we build products.
Thursday, January 30, 14
4. stematically
the se s, and sy
write hypo
ssumptions
te st our a
scientific
data-driven
customer-centric
process for finding product/market fit.
for reducing uncertainty.
for continuous learning.
for building the right thing.
Lean is a
measure ever y thing
talk to our customers
aste time
you don’t w g thing
so
the wron
building
ed by
nform omer
ays i cust
e a l w t he
we’r
so
because building things people
don’t want or use sucks!
Thursday, January 30, 14
products
customers
ill adopt &
w
pay for
5. Le ad with v ision.
But te st assumptions ruthle ssly.
Lean is not
but it’s ok ay to take on
debt in order to le arn
not che ap. ef f icient
it’s actually
ver y dif f icult
Agile
ild it the
If you bu
Thursday, January 30, 14
Waterfall
will come
y
a replacement for vision.
permission to make crap.
cheap.
easy.
the only way to make stuff.
15. for le arning
The MVP is not only a product, it’s a process.
Thursday, January 30, 14
16. In all these cases, the product teams learned
market size
about
adoption
...from actual customers. pricing
scope
better ideas they didn’t
...BEFORE building the whole have themselves.
thing.
Thursday, January 30, 14
17. The question is NOT, “Can you build it?”
Thursday, January 30, 14
18. The question is, “Should you build it?”
Thursday, January 30, 14
20. Lean Principles
1. Solve real, painful problems that exist in a reachable market.
2. Enable & measure progress around outcomes vs. outputs.
3. Value making over analysis.
4. Create an environment of continuous learning.
5. Encourage failing fast.
6. Work on cross-functional, dedicated teams.
7. Increase shared understanding by externalizing your work.
8. Remove waste from deliverables and process.
9. When uncertainty is high, reduce complexity.
Thursday, January 30, 14
23. Tactics
1.Declare your assumptions.
2.Identify the riskiest assumptions.
3.Write a hypothesis to test your assumption.
4.Run an experiment (interview, MVP, etc.)
5.Measure the outcomes.
6.Synthesize the learnings, and do it again.
Thursday, January 30, 14