The document discusses the Lean Startup methodology. Some key points:
1. Lean Startup advocates rapid prototyping and customer feedback to quickly test assumptions and evolve products faster than traditional methods.
2. It encourages frequent releases, often multiple times per day, to incorporate customer input through practices like continuous deployment.
3. A central tenet is reducing waste by increasing customer contact to test assumptions early and avoid incorrect directions. This aims to decrease the time to find product-market fit.
4. The document then provides an example story of a company applying Lean Startup tactics like prototyping ideas, using metrics to analyze customer behavior and decisions, and remaining flexible to change based on learning.
4. WTF =
wikipedia to fools
Lean Startup is a concept coined (and trademarked) by Eric Ries. Ries writes that lean startups are born out of the following three trends:
1. use of free and open source software,
2. application of agile software development methods, and
3. ferocious customer-centric rapid iteration, as exemplified by the Customer Development process[1].
Lean Startup initially advocates the creation of rapid prototypes designed to test market assumptions, and uses customer feedback to evolve them much faster than via more traditional software
engineering practices, such as the Waterfall model. It is not uncommon to see Lean Startups release new code to production multiple times a day[2], often using a practice known as Continuous
Deployment[3].
According to the New York Times, "The term 'lean start-up' was coined by Mr. Ries, 31, an engineer, entrepreneur and blogger. His inspiration, he says, was the lean manufacturing process, fine-
tuned in Japanese factories decades ago and focused on eliminating any work or investment that doesnʼt produce value for customers." [4]
Lean Startup is sometimes described as Lean Thinking applied to the entrepreneurial process[5]. A central tenet of Lean Thinking is to reduce waste. Lean Startup processes reduce waste by
increasing the frequency of contact with real customers, therefore testing and avoiding incorrect market assumptions as early as possible[6]. This approach attempts to improve on historical
entrepreneurial tactics by reducing the work required to assess assumptions about the market, and to decrease the time it takes a business to find market traction. This is referred to as Minimum
Viable Product.
In The Entrepreneur's Guide to Customer Development, Brant Cooper and Patrick Vlaskovits add a fourth element, and that is the use of powerful, low-cost and easy-to-use analytics. While some
characteristics of lean startups have been practiced for years, the confluence of these trends is a recent phenomenon and offers the potential for unprecedented "speed of iteration" or "number of
learning cycles per dollar" as business hones in on product-market fit[7].
[edit]
16. Change of plans!
- security systems
- online project management
- first personal computers
17. Change of plans!
- security systems
- online project management
- first personal computers
- collection of links to
research papers
18. Change of plans!
- security systems
- online project management
- first personal computers
- collection of links to
research papers
- online game
19. Change of plans!
- security systems
- online project management
- first personal computers
- collection of links to
research papers
- online game
- printer drivers
45. prototype
• developing new
product
• adding new
feature
• can we test our
idea without
implementing?
46. test
• give it to the market
• take data how the
customers use the
feature (what
indicators?)
• decide the necessity of
the feature
47. example: share button
Idea: let the users share the
room to their friends
Prototype: share button to
facebook or vkontakte wall, to
twitter or via email
Test: nobody uses the button
48. example: topics
Idea: people need topics for
discussion
Prototype: creating rooms
the number of for different topics
messages per day
Test: how many people
discussed topics
Decision: let’s create topics
49. Next step for topics
• How we can test without implementing and
waiting?
• We have got Squeek - a dolphin bot
• Let the bot give the topic (or ask about it)
• How can we evaluate the result?