Lean startup is a methodology for developing businesses and products that aims to shorten product development cycles and rapidly discover if a proposed business model is viable; this is achieved by adopting a combination of business-hypothesis-driven experimentation, iterative product releases, and validated learning.
Central to the lean startup methodology is the assumption that when startup companies invest their time into iteratively building products or services to meet the needs of early customers, the company can reduce market risks and sidestep the need for large amounts of initial project funding and expensive product launches and failures.
- 1 Overview
- 2 Precursors
- 3 Definitions
- 3.1 Definitions based on The Lean Startup
- 3.2 Business model templates
- 4 The movement
- 5 Lean concepts
- 6 History
- 7 Criticism
- 8 See also
- 9 References
Similar to the precepts of lean manufacturing and lean software development, the lean startup methodology seeks to eliminate wasteful practices and increase value-producing practices during the earliest phases of a company so that the company can have a better chance of success without requiring large amounts of outside funding, elaborate business plans, or a perfect product. Customer feedback during the development of products or services is integral to the lean startup process, and ensures that the company does not invest time designing features or services that consumers do not want. This is done primarily through two processes, using key performance indicators and a continuous deployment process.
When a startup company cannot afford to have its entire investment depend upon the success of a single product or service, the lean startup methodology proposes that by releasing a minimum viable product that is not yet finalized, the company can then make use of customer feedback to help further tailor the product or service to the specific needs of its customers.
The lean startup methodology asserts that the "lean has nothing to do with how much money a company raises"; rather it has everything to do with assessing the specific demands of consumers and how to meet that demand using the least amount of resources possible.
Use of the word lean to describe the streamlined production system of lean manufacturing was popularized by the 1990 book The Machine That Changed the World. The Toyota Production System pioneered by Taiichi Ohno combined flow principles that had been used by Henry Ford since the early 1900s with innovations such as the TWI programs introduced to Japan in 1951.
Lean manufacturing systems consider as waste the expenditure of resources for any goal other than the creation of value for the end customer, and continually seek ways to eliminate such waste. In particular, such systems focus on:
- minimizing inventory throughout the assembly line,
- using Kanban cards to signal only when the necessary inputs to production are needed, and in so doing, reduce assembly waste (inventory) and increase productivity,
- identifying mistakes or imperfections during assembly as early as possible at immediate quality control checkpoints to ensure that the least amount of time is expended developing a faulty product, and
- maintaining close connections with suppliers in order to understand their customers' desires.
Lean manufacturing was later applied to software as lean software development.
The lean startup methodology is based on the customer development methodology of Silicon Valley serial entrepreneur-turned-academic Steve Blank. In his book The Four Steps to the Epiphany: Successful Strategies for Products that Win (2005, 5th edition 2013), Blank pointed out the pitfalls of a narrow emphasis on product development; instead he argued that startups should focus on what he called "customer development", which emphasizes "learning about customers and their problems as early in the development process as possible".:12 Blank's customer development methodology proposed four steps::16–19
- Customer discovery tests hypotheses about the nature of the problem, interest in the product or service solution, and business viability.
- Customer validation tests the business viability through customer purchases and in the process creates a "sales road map", a proven and repeatable sales process. Customer discovery and customer validation corroborate the business model.
- Customer creation executes the business plan by scaling through customer acquisition, creating user demand and directing it toward the company's sales channels.
- Company building formalizes and standardizes company departments and operations.
In an article published in the Harvard Business Review in 2013, Steve Blank described how the lean startup methodology also drew inspiration from the work of people like Ian C. MacMillan and Rita Gunther McGrath who developed a technique called discovery-driven planning, which was an attempt to bring an entrepreneurial mindset to planning.
Definitions based on The Lean StartupEdit
Minimum viable productEdit
A minimum viable product (MVP) is the "version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort" (similar to a pilot experiment). The goal of an MVP is to test fundamental business hypotheses (or leap-of-faith assumptions) and to help entrepreneurs begin the learning process as quickly as possible.
As an example, Ries noted that Zappos founder Nick Swinmurn wanted to test the hypothesis that customers were ready and willing to buy shoes online.:57–58 Instead of building a website and a large database of footwear, Swinmurn approached local shoe stores, took pictures of their inventory, posted the pictures online, bought the shoes from the stores at full price after he'd made a sale, and then shipped them directly to customers. Swinmurn deduced that customer demand was present, and Zappos would eventually grow into a billion dollar business based on the model of selling shoes online.:57–58
Continuous deployment (only for software development)Edit
Continuous deployment, similar to continuous delivery, is a process "whereby all code that is written for an application is immediately deployed into production," which results in a reduction of cycle times. Ries stated that some of the companies he's worked with deploy new code into production as often as 50 times a day. The phrase was coined by Timothy Fitz, one of Ries's colleagues and an early engineer at IMVU.
A split or A/B test is an experiment in which "different versions of a product are offered to customers at the same time." The goal of a split test is to observe differences in behavior between the two groups and to measure the impact of each version on an actionable metric.
A/B testing is sometimes incorrectly performed in serial fashion, where a group of users one week may see one version of the product while the next week users see another. This undermines the statistical validity of the results, since external events may influence user behavior in one time period but not the other. For example, a split test of two ice cream flavors performed in serial during the summer and winter would see a marked decrease in demand during the winter where that decrease is mostly related to the weather and not to the flavor offer.
Another way to incorrectly A/B test is to assign users to one or another A/B version of the product using any non-random method.
Actionable metrics can lead to informed business decisions and subsequent action. These are in contrast to vanity metrics—measurements that give "the rosiest picture possible" but do not accurately reflect the key drivers of a business.
Vanity metrics for one company may be actionable metrics for another. For example, a company specializing in creating web based dashboards for financial markets might view the number of web page views per person as a vanity metric as their revenue is not based on number of page views. However, an online magazine with advertising would view web page views as a key metric as page views are directly correlated to revenue.
A typical example of a vanity metric is "the number of new users gained per day". While a high number of users gained per day seems beneficial to any company, if the cost of acquiring each user through expensive advertising campaigns is significantly higher than the revenue gained per user, then gaining more users could quickly lead to bankruptcy.
A pivot is a "structured course correction designed to test a new fundamental hypothesis about the product, strategy, and engine of growth." A notable example of a company employing the pivot is Groupon; when the company first started, it was an online activism platform called The Point. After receiving almost no traction, the founders opened a WordPress blog and launched their first coupon promotion for a pizzeria located in their building lobby. Although they only received 20 redemptions, the founders realized that their idea was significant, and had successfully empowered people to coordinate group action. Three years later, Groupon would grow into a billion dollar business.
This topic focuses on how entrepreneurs can maintain accountability and maximize outcomes by measuring progress, planning milestones, and prioritizing. The topic was later expanded upon to include three levels of innovation accounting related to the types of assumptions being validated.
The Build–Measure–Learn loop emphasizes speed as a critical ingredient to product development. A team or company's effectiveness is determined by its ability to ideate, quickly build a minimum viable product of that idea, measure its effectiveness in the market, and learn from that experiment. In other words, it's a learning cycle of turning ideas into products, measuring customers' reactions and behaviors against built products, and then deciding whether to persevere or pivot the idea; this process repeats as many times as necessary. The phases of the loop are: Ideas → Build → Product → Measure → Data → Learn.
Business model templatesEdit
Business Model CanvasEdit
The Business Model Canvas is a strategic management template invented by Alexander Osterwalder around 2008 for developing new business models or documenting existing ones. It is a visual chart with elements describing a firm's value proposition, infrastructure, customers, and finances. It assists firms in aligning their activities by illustrating potential trade-offs.
The template consists of nine blocks: activities, partners, resources, value proposition, customers, customer channels, customer relationships, costs and revenue. Startups use the template (and/or other templates described below) to formulate hypotheses and change their business model based on the success or failure of tested hypotheses.
The Lean Canvas is a version of the Business Model Canvas adapted by Ash Maurya in 2010 specifically for startups. The Lean Canvas focuses on addressing broad customer problems and solutions and delivering them to customer segments through a unique value proposition. "Problem" and "solution" blocks replace the "key partners" and "key activities" blocks in the Business Model Canvas, while "key metrics" and "unfair advantage" blocks replace the "key resources" and "customer relationships" blocks, respectively.
Value Proposition CanvasEdit
The Value Proposition Canvas is a supplement to the Business Model Canvas ("customer segment" and "value proposition" blocks) published in 2012 to address the customer–product relationship, the perceived value of the product or service, and potential product/market fit. The "value proposition" block is divided into three categories—products and services, gain creators, and pain relievers—that correspond to three categories in the "customer segment" block—customer jobs, gains, and pains.
Mission Model CanvasEdit
The Mission Model Canvas is a version of the Business Model Canvas developed by Alexander Osterwalder and Steve Blank for entities such as government agencies that have a predetermined budget instead of a goal of raising revenue. It was published in 2016. Earlier publications by Osterwalder and colleagues had suggested how to adapt the Business Model Canvas for nonprofit enterprises that depend on raising revenue. "Mission budget/cost" and "mission achievement/impact factors" blocks replace the "cost structure" and "revenue streams" blocks in the Business Model Canvas, while "beneficiaries", "buy-in/support" and "deployment" blocks replace the "customer segments", "customer relationships" and "channels" blocks, respectively.
Ries and others created an annual technology conference called Startup Lessons Learned which has subsequently changed its name to the Lean Startup Conference. Lean startup meetups in cities around the world have garnered 20,000 regular participants. The first lean startup meetup named Lean Startup Circle was created by Rich Collins on June 26, 2009 hosting speaking events, workshops, and roundtable discussions. As of 2012, there are lean startup meetups in over 100 cities and 17 countries as well as an online discussion forum with over 5500 members. Third-party organizers have led lean startup meetups in San Francisco, Chicago, Boston, Austin, Beijing, Dublin, and Rio de Janeiro, among others—many of which are personally attended by Ries—with the Chicago and New York City Lean Startup Meetups attracting over 4,000 members each. The Lean Startup Machine created a new spin on the lean startup meetups by having attendees start a new company in three days. As of 2012, the Lean Startup Machine claimed to have created over 600 new startups this way.
Prominent high-tech companies have begun to publicly employ the lean startup methodology, including Intuit, Dropbox, Wealthfront, Votizen, Aardvark, and Grockit. The lean startup principles are also taught in classes at Harvard Business School and UC Berkeley and are implemented in municipal governments through Code for America.
Academic researchers in Finland have applied the lean startup methodology to accelerating research innovation.
The United States Government has employed lean startup ideas. The Federal Chief Information Officer of the United States, Steven VanRoekel noted in 2012 that he was taking a "lean-startup approach to government". Ries has worked with the former and current Chief Technology Officers of the United States—Aneesh Chopra and Todd Park respectively—to implement aspects of the lean startup model. In particular, Park noted that in order to understand customer demand, the Department of Health and Human Services recognized "the need to rapidly prototype solutions, engage customers in those solutions as soon as possible, and then quickly and repeatedly iterate those solutions based on working with customers". In May 2012, Ries and The White House announced the Presidential Innovation Fellows program, which brings together top citizen innovators and government officials to work on high-level projects and deliver measurable results in six months.
Hacking for DefenseEdit
Steve Blank, working with retired United States Army colonel Pete Newell and former United States Army Special Forces colonel Joe Felter, adapted lean startup principles for U.S. government innovation under the moniker "Hacking for Defense", a program in which university students solve problems that the Department of Defense, the United States Armed Forces, and the United States Intelligence Community submit to participating universities. Hacking for Defense and variants like Hacking for Diplomacy have expanded to the United States Department of State, Department of Energy, NASA, and nonprofits.
Lean startup principles have been applied to specific competencies within typical startups and larger organizations:
The lean startup methodology was first proposed in 2008 by Eric Ries, using his personal experiences adapting lean management and customer development principles to high-tech startup companies. The methodology has since been expanded to apply to any individual, team, or company looking to develop new products, services, or systems without unlimited resources. The lean startup's reputation is due in part to the success of Ries' bestselling book, The Lean Startup, published in September 2011.
Ries' said that his first company, Catalyst Recruiting, failed because he and his colleagues did not understand the wants of their target customers, and because they focused too much time and energy on the initial product launch. Next, Ries was a senior software engineer with There, Inc., which Ries described as a classic example of a Silicon Valley startup with five years of stealth R&D, $40 million in financing, and nearly 200 employees at the time of product launch. In 2003, There, Inc. launched its product, There.com, but they were unable to garner popularity beyond the initial early adopters. Ries claimed that despite the many proximate causes for failure, the most important mistake was that the company's "vision was almost too concrete", making it impossible to see that their product did not accurately represent consumer demand.
Although the lost money differed by orders of magnitude, Ries concluded that the failures of There, Inc. and Catalyst Recruiting shared similar origins: "it was working forward from the technology instead of working backward from the business results you're trying to achieve."
After Ries later co-founded IMVU Inc., IMVU investor Steve Blank insisted that IMVU executives audit Blank's class on entrepreneurship at UC Berkeley. Ries applied Blank's customer development methodology and integrated it with ideas from lean software development and elsewhere to form the lean startup methodology.
Ben Horowitz, the co-founder of venture capital firm Andreessen Horowitz, wrote an article in 2010 criticizing the lean startup method for over-emphasizing "running lean" (constantly cutting and reducing non-essential parts of the company to save time and money). He specifically disagreed with portraying "running lean" as an end rather than a means to winning the market without running out of cash. Horowitz gave as an example his startup Loudcloud, which by "running fat" was able to outperform 20 direct competitors and after 8 years reach a value of $1.6 billion. However, at least since 2008, numerous advocates of lean methods have pointed out that "running lean" does not mean cost cutting.
Trey Griffith, the VP of technology at Teleborder, stated in 2012 that the majority of backing for the lean startup methodology was anecdotal and had not been rigorously validated when first presented. However, he goes on to note that better support of the method comes out of a 2011 analysis of the factors of success in growth companies as described in the 2011 book Great by Choice.
John Finneran, a business writer and former user of the lean startup method, described in 2013 a number of the method's assumptions that he did not recognize during his use of the method. In particular, he observed that his clients were often not motivated to invest time and effort into helping iterate a minimal viable product; instead they wanted a more polished product to begin with. Second, he found virtually no early adopters who were willing to try to give feedback on unpolished software simply to be the first to get a chance at it. Third, he argued that lean startup can distract from essential traditional management practices like development discipline and budget protection. In general, he stated that it is important to be critical and skeptical of lean startup methods rather than pre-supposing that they will be effective. Ries had already anticipated this criticism in his book: "We cannot afford to have our success breed a new pseudoscience around pivots, MVPs, and the like. This was the fate of scientific management, and in the end, I believe, that set back its cause by decades.":279 This implies that the concept of validated learning applies to the lean startup methods themselves, and not just to products. There is a large literature on action learning and human error management developed in work psychology and in other fields which shows many people can learn from errors under certain circumstances; an error-management culture allows and encourages people to learn from errors.
- Penenberg, Adam L. (8 September 2011). "Eric Ries is a Lean Startup machine". Fast Company. Retrieved 4 June 2015.
- Adler, Carlye (30 August 2011). "Ideas are overrated: startup guru Eric Ries' radical new theory". Wired. Retrieved 4 June 2015.
- Ries, Eric (October 2011). "Creating the Lean Startup". Inc. 33 (8): 56–63. Retrieved 4 June 2015.
- Tam, Pui-Wing (20 May 2010). "Philosophy helps start-ups move faster". The Wall Street Journal. Retrieved 4 June 2015.
- Ries, Eric (11 September 2011). "Are you building the right product?". TechCrunch. Retrieved 4 June 2015.
- Schonfeld, Erick (30 July 2011). "Don't be fooled by vanity metrics". TechCrunch. Retrieved 4 June 2015.
- Loizos, Connie (26 May 2011). "'Lean Startup' evangelist Eric Ries is just getting started". PeHUB. Retrieved 4 June 2015.
- Womack, James P.; Jones, Daniel T.; Roos, Daniel (1990). The machine that changed the world: based on the Massachusetts Institute of Technology 5-million dollar 5-year study on the future of the automobile. New York: Rawson Associates. ISBN 0892563508. OCLC 21977626.
- Dinero, Donald A. (2005). Training within industry: the foundation of lean. New York: Productivity Press. pp. 49–53. ISBN 1563273071. OCLC 58042977.
- Womack, James P.; Jones, Daniel T. (2003) . Lean thinking: banish waste and create wealth in your corporation (Revised ed.). New York: Free Press. p. 232. ISBN 0743249275. OCLC 51031471.
- Feld, William M. (2001). Lean manufacturing: tools, techniques, and how to use them. Boca Raton, FL; Alexandria, VA: St. Lucie Press; APICS. p. 84. ISBN 157444297X. OCLC 44732233.
- Blank, Steven G. (2007). The four steps to the epiphany: successful strategies for products that win (PDF) (3rd ed.). Pescadero, CA: S. G. Blank. ISBN 0976470705. OCLC 778813594.
- Blank, Steven G. (May 2013). "Why the lean start-up changes everything". Harvard Business Review. 91 (5): 63–72.
Lean start-up practices aren't just for young tech ventures. Large companies, such as GE and Intuit, have begun to implement them.... Over the years managerial experts such as Clayton Christensen, Rita McGrath, Vijay Govindarajan, Henry Chesbrough, Ian MacMillan, Alexander Osterwalder, and Eric von Hippel have advanced the thinking on how large companies can improve their innovation processes. During the past three years, however, we have seen large companies, including General Electric, Qualcomm, and Intuit, begin to implement the lean start-up methodology.
- Ries, Eric (2014) . The lean startup: how today's entrepreneurs use continuous innovation to create radically successful businesses. Crown Publishing. p. 103. ISBN 9780307887894. OCLC 693809631.
- Ries, Eric (3 August 2009). "The lean startup". startuplessonslearned.com. Retrieved 4 June 2015.
- Tokareva, Julia (27 February 2018). "What is a minimum viable product, and why do companies need them?". Forbes.com. Forbes. Retrieved 16 October 2018.
- Ries, Eric (30 March 2009). "Continuous deployment in 5 easy steps". radar.oreilly.com. Retrieved 4 June 2015.
- Fitz, Timothy (10 February 2009). "Continuous deployment at IMVU: doing the impossible fifty times a day". timothyfitz.wordpress.com. Retrieved 4 June 2015.
- Ries, Eric (19 May 2009). "Vanity metrics vs. actionable metrics". fourhourworkweek.com. Retrieved 4 June 2015.
- Blank, Steven G.; Dorf, Bob (2012). The startup owner's manual: the step-by-step guide for building a great company. Pescadero, CA: K&S Ranch, Inc. ISBN 9780984999309. OCLC 780144160.
- Blank, Steven G. (17 May 2014). "Startup Wisdom: Steve Blank, Consulting Associate Professor of Stanford University". YouTube. Retrieved 4 June 2015. Talk given in May 2013; the audience is composed of the CEOs of the portfolio companies of Khosla Ventures.
- Ries, Eric (1 June 2012). "Innovation accounting: secret to fast growth". Inc. Live. Retrieved 4 June 2015.
- Kaplan, Soren (11 December 2017). "Lean startup's newest tool is a game changer for innovators". Inc. Live. Retrieved 30 September 2018.
- Maurya, Ash (2012) . Running lean: iterate from plan A to a plan that works. The lean series (2nd ed.). Sebastopol, CA: O'Reilly. p. 12. ISBN 9781449305178. OCLC 759911462.
- Kromer, Tristan (23 February 2012). "Build Measure Learn vs. Learn Measure Build". grasshopperherder.com. Retrieved 4 June 2015.
- Osterwalder, Alexander (2 July 2008). "What is a business model?". business-model-design.blogspot.com. Archived from the original on 6 September 2008. Retrieved 17 October 2018.
- Osterwalder, Alexander; Pigneur, Yves; Clark, Tim (2010). Business model generation: a handbook for visionaries, game changers, and challengers. Hoboken, NJ: John Wiley & Sons. ISBN 9780470876411. OCLC 648031756.
- Maurya, Ash (11 August 2010). "How I Document my business model hypotheses". ashmaurya.com. Archived from the original on 15 August 2010. Retrieved 17 October 2018.
- Maurya, Ash (27 February 2012). "Why Lean Canvas vs Business Model Canvas?". leanstack.com. Retrieved 4 June 2015.
- Osterwalder, Alexander (29 August 2012). "Achieve product–market fit with our brand-new Value Proposition Designer Canvas". businessmodelalchemist.com. Archived from the original on 7 June 2013. Retrieved 16 October 2018.
- Osterwalder, Alexander; Pigneur, Yves; Bernarda, Gregory; Smith, Alan (2014). Value proposition design: how to create products and services customers want. Strategyzer series. Hoboken, NJ: John Wiley & Sons. ISBN 9781118968055. OCLC 894271736.
- The Mission Model Canvas was introduced in a joint blog post published on the blog of Osterwalder's consulting firm Strategyzer and on Blank's blog: Blank, Steven G. (23 February 2016). "The Mission Model Canvas: an adapted Business Model Canvas for mission-driven organizations". steveblank.com. Retrieved 16 October 2018. And: Osterwalder, Alexander (25 February 2016). "The Mission Model Canvas: an adapted Business Model Canvas for mission-driven organizations". blog.strategyzer.com. Retrieved 17 October 2018.
- Osterwalder, Alexander (27 August 2009). "Business models beyond profit—social entrepreneurship lecture". businessmodelalchemist.com. Archived from the original on 4 April 2014. Retrieved 17 October 2018.
- Clark, Tim; Osterwalder, Alexander; Pigneur, Yves (2012). Business model you: a one-page method for reinventing your career. Hoboken, NJ: John Wiley & Sons. ISBN 9781118156315. OCLC 751834016.
- Ries, Eric (27 June 2012). "Announcing the 2012 Lean Startup Conference in SF". startuplessonslearned.com. Retrieved 4 June 2015.
- Roush, Wade (6 July 2011). "Eric Ries, the face of the Lean Startup movement, on how a once-insane idea went mainstream". Xconomy. Retrieved 4 June 2015.
- "About Lean Startup Circle". leanstartupcircle.com. Retrieved 4 June 2015.
- Collins, Rich (28 April 2012). "New leadership". blog.leanstartupcircle.com. Retrieved 4 June 2015.
- "Find Meetup Groups near you: 'Lean Startup'". Meetup. Retrieved 4 June 2015.
- "About Lean Startup Machine". leanstartupmachine.com. Retrieved 4 June 2015.
- "Why startup founders need to talk to their customers (video)". mashable.com. 24 January 2012. Retrieved 4 June 2015.
- Lohr, Steve (25 April 2010). "The rise of the fleet-footed start-up". The New York Times. p. BU5. Retrieved 4 June 2015.
- "The Lean Startup: case studies". theleanstartup.com. Retrieved 4 June 2015.
- Greenwald, Ted (18 May 2012). "Upstart Eric Ries has the stage and the crowd is going wild". Wired. Retrieved 4 June 2015.
- Still, Kaisa (May 2017). "Accelerating research innovation by adopting the lean startup paradigm". Technology Innovation Management Review. 7 (5): 32–43. doi:10.22215/timreview/1075. Retrieved 16 October 2018.
- Schreiber, Danny (5 April 2012). "U.S. CIO VanRoekel talks startups, savings, new tech in Iowa visit". Silicon Prairie News. Retrieved 4 June 2015.
- Ries, Eric (30 May 2012). "Lean government". startuplessonslearned.com. Retrieved 4 June 2015.
- McKendrick, Joe (28 October 2011). "In search of the US government's inner 'startup': federal CIO". ZDNet. Retrieved 4 June 2015.
- "Making a difference: innovation pathway and entrepreneurs in residence: interview with Todd Park, Chief Technology Officer of the United States". blogs.fda.gov. 10 April 2012. Retrieved 4 June 2015.
- Foley, John (30 April 2012). "Busting through the federal IT budget ceiling". InformationWeek. Retrieved 4 June 2015.
- Park, Todd (23 May 2012). "Wanted: a few good women and men to serve as presidential innovation fellows". The White House. Retrieved 4 June 2015.
- Ricks, Thomas E. (25 January 2017). "A neat new way to attack military problems: 'Hacking for Defense'". Foreign Policy. Retrieved 16 October 2018.
- Blank, Steven G. (19 July 2017). "National Security Innovation just got a major boost in Washington". steveblank.com. Retrieved 16 October 2018.
- Satell, Greg (8 July 2018). "This army colonel is showing large enterprises how to innovate like lean startups". Inc.com. Retrieved 16 October 2018.
- Perry, Tekla S. (25 July 2017). "U.S. defense budget may help fund 'Hacking for Defense' classes at universities". spectrum.ieee.org. IEEE Spectrum. Retrieved 16 October 2018.
- Perry, Tekla S. (4 January 2018). "First Hacking for Impact class buzzes around the mosquito problem". spectrum.ieee.org. IEEE Spectrum. Retrieved 16 October 2018.
- In September 2008, Ries coined the term lean startup on his blog, Startup Lessons Learned: Ries, Eric (8 September 2008). "The lean startup". startuplessonslearned.com. Retrieved 4 June 2015.
- Wilson, Nick (7 December 2011). "How Eric Ries changed the framework for startup success". Financial Post. Retrieved 4 June 2015.
- "Best sellers". The New York Times. 2 October 2011. Retrieved 2 June 2015.
- "Venture Capital: Eric Ries, author of 'The Lean Startup'". YouTube. 21 November 2011. Retrieved 4 June 2015.
- Horowitz, Ben (17 March 2010). "The case for the fat start-up". allthingsd.com. Dow Jones & Company. Retrieved 4 June 2015.
- Trent, Robert J. (2008). End-to-end lean management: a guide to complete supply chain improvement. Ft. Lauderdale, FL: J. Ross Pub. p. 17. ISBN 9781932159929. OCLC 227914436.
Lean purists are quick to point out, however, that lean is not about the short-term pursuit of cost savings that characterizes many organizations. Cost reductions achieved by eliminating important tests during product development or using lower grade materials, for example, may not be supportive of a lean philosophy.
- Bohan, Rick (8 November 2010). "Want to succeed at lean? Forget cost cutting". IndustryWeek. Retrieved 4 June 2015.
My point is that lean methods and concepts have come to be seen primarily as cost-cutting tools. But this is wrong. An emphasis on cost reduction risks the success of the lean initiative.
- Waddell, Bill (11 July 2011). "Why lean is not a good cost reduction strategy". Retrieved 4 June 2015.
The problem is that lean is not a cost reduction strategy. Properly applied, lean principles will not reduce spending much at all. Lean is aimed at enhancing the top line – sales – not the total spending line.
- Graban, Mark (2012) . Lean hospitals: improving quality, patient safety, and employee engagement (2nd ed.). New York: Productivity Press/Taylor & Francis. p. 31. ISBN 9781439870433. OCLC 726074707.
Lean thinkers see cost as the end result of all our systems and processes. As an end result, cost is not something that can be directly impacted. Or at least we do not have an impact on it in the traditional "cost-cutting" ways, which typically have meant layoffs and possibly the scaling back of services provided to our community. Lean hospitals focus on reducing waste, not cutting costs. Lean organizations also focus on the customers (the patients) and the value that is being delivered to them. In this way, Lean is not focused on doing less but rather on delivering the right amount of value. If we are reducing waste, we can often provide more value while expending less effort and less cost.
- Sarkar, Debashis (2012). Lessons in lean management: 53 ideas to transform services. Chennai: Westland. p. 4. ISBN 9789381626801. OCLC 821263409.
Organizations often view Lean as purely a cost-cutting tool. This is a parochial view from individuals or organizations that do not entirely comprehend what Lean thinking is and what it can do to a business. Lean is not a cost-cutting tool but a method that drives cost-efficiency.
- Grady, Kenneth (25 February 2015). "Lean is not about cost cutting". seytlines.com. Retrieved 4 June 2015.
If we go back to the central premise of this post – lean is not about cost cutting – then I need to address what lean "is" about. Lean is a philosophy through which we look at value from the client's perspective and focus what we do on delivering that value while respecting people.
- Markovitz, Daniel (30 March 2015). "For the last time: cost cutting isn't 'lean'". markovitzconsulting.com. Retrieved 4 June 2015.
There's plenty of research proving that cost reduction isn't sustained in the long run. Just like weight always comes back after drastic dieting, costs always creep back two to three years after drastic cuts, because the underlying processes and capabilities haven't been improved.
- Paterson, James C. (2015). Lean auditing: driving added value and efficiency in internal audit (1st ed.). Chichester, UK; Hoboken, NJ: John Wiley & Sons. p. 9. doi:10.1002/9781119017066. ISBN 9781118896884. OCLC 890127776.
Lean ways of working should not simply be equated with cost cutting.
- Griffith, Trey (17 January 2012). "Empirically validating the lean startup: making a startup great by choice". tgriff3.com. Retrieved 4 June 2015.
- Finneran, John (1 April 2013). "The Fat Startup: lessons from my failed Lean Startup". johnffinneran.com. Retrieved 4 June 2015.
- Maurya, Ash (2012) . Running lean: iterate from plan A to a plan that works. The lean series (2nd ed.). Sebastopol, CA: O'Reilly. p. xxviii. ISBN 9781449305178. OCLC 759911462.
One of the things that particularly drew me to the Lean Startup methodology is that it is a metaprocess from which more specific processes and practices can be formulated. The same principles used to test your product can and should be applied to test your tactics when taking these principles to practice. There is no room for faith in a Lean Startup.... There are no silver bullets. No methodology can guarantee success. But a good methodology can provide a feedback loop for continuous improvement and learning.
- Seddon, John; Caulkin, Simon (April 2007). "Systems thinking, lean production and action learning". Action Learning: Research and Practice. 4 (1): 9–24. doi:10.1080/14767330701231438.
- Frese, Michael; Keith, Nina (January 2015). "Action errors, error management, and learning in organizations". Annual Review of Psychology. 66: 661–687. doi:10.1146/annurev-psych-010814-015205. PMID 25251490.