My take on Eric Ries' book The Lean Startup, as presented to my colleagues at XING Barcelona.
DISCLAIMER: This is a sketched presentation. Can be disappointing.
2. Lean:
● production practice
● that considers the expenditure of resources
for any goal other than the creation of value
for the end customer to be wasteful,
● and thus a target for elimination.
Startup:
● A human institution
● designed to deliver a new product/service
● under conditions of uncertainty.
Entrepreneurship == Management
3. 1. Generate an hypothesis
○ Value hypothesis (“customers come back?”)
○ Growth hypothesis (“customers recommend us?”)
2. Build it
○ Minimum Viable Product
○ Small batches
3. Prove it
○ Metrics
○ Feedback
The scientific method approach to
management
4. Outcome: “validated learning”
“It is not so important to be productive, to do things on time
or budget. The goal is to figure out the right thing to build as
quickly as possible”
Employee productivity != Project productivity
Corollary:
Profit != Value
Growth != Value
(look for value, profit and growth will come)
5.
6.
7.
8.
9. Ideas
Think big, start small.*
Get out of the building (genchi gembutsu)
Remove any feature, process, or effort that
does not contribute directly to the learning you
are seeking.
*applies to build, measure and learn
10.
11. Build
Examples
● The Concierge MVP (Food on the Table)
● The Video MVP (Dropbox)
Words of caution:
● MVP != prototype (business model vs UX)
● If we don’t know who the customer is, we
don’t know what quality is.
Start with early adopters (they are forgiving)
and localized (no fireworks yet). Give them the
best you’ve got.
12.
13. Measure
Examples:
● Wizard of Oz Testing
● The Smoke Test
The AAA’s of Metrics:
● Actionable
● Accessible
● Auditable
Vanity Metrics vs. Actionable Metrics
14.
15. Learn
Example:
● The 5 whys
○ Ask 5 times why to a problem
○ Solve each proportionally (proportional investment)
○ Work with small batches (adaptative organisation)
VISION — STRATEGY — PRODUCT
(untouched) (pivots) (optimizes)
Rigorously measure the actual numbers. Devise
experiments to learn how to move the numbers to the
desired business plan.
16.
17. Thank you
“A solid process lays the foundation for a
healthy culture, one where ideas are evaluated
by merit and not by job title.”
Notas do Editor
Some slides taken from http://www.slideshare.net/startuplessonslearned/eric-ries-the-lean-startup-google-tech-talk
You as agile developers may be thinking “ booooring ” , but…
… it is a method we are already applying to the development of the product...
... The difference is that this time it is applied to the learning process in the product management side.
So how sould you approach the decision making in order to define the product? Start with the ideas and move from there clockwise right? The right way is to start an idea and then, counter clockwise, formulate an hypothesis needs to be validated (learn) and devise what measures will validate it (measures). THEN you can decide what to build.
* this will come back with the “ follow the vision but pivot ” idea, and also applies to MVP and testing phases.
Start with one hypothesis at the time. Target a subset of the desired users. Think big, act small.
Example of Vanity vs Actionable metrics? Measure one hypothesis at the time. Use only a subset of the users if you are experimenting with new things. Think big, act small.
If a problem is endemic, it will continue to pop up in one of the 5 whys, and it will be solved little by little. This is proportional investment and adaptative organization. Small batches. Think big, act small. The most mind-blowing revelation for me is applying the cycle to the strategy level. Pivot or Persevere meeting. Have a Vision and stick to it. Or have a Business Plan (desired numbers) and stick to it. Think big. But act at small chunks, small batches. Act small.