Lean product development
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)(Learn how and when to remove this template message)
|This article may need to be rewritten entirely to comply with Wikipedia's quality standards. (December 2015)|
- Need for more innovative solutions
- Reducing long development cycle times
- Many redevelopment cycles
- Reducing high development costs
- Reducing long production cycle times
- Reducing high production costs
History of lean product development
Toyota started its journey with lean product development at Toyoda Loom Works (see History of Toyota), rather than the lean manufacturing that became famous through the book "The Machine that changed the world".
When Toyota started developing cars, there was a difference between its context in Japan and its competitors in the USA. Toyota had few educated engineers and little prior experience. Car companies in US had the benefit of engineering schools and a well-educated work force in the cities. To tackle this shortfall in knowledge and experience, Toyota conducted an incremental approach to development that build on this knowledge and became the basis of the lean systems Toyota uses today.
Allen Ward studied Toyota’s lean product development system, and found parallels with the US airplane industry. For instance, the Wright brothers’ method of constructing their airplane became one of the legacies they passed on to the aviation industry. This approach enabled the USA to create one of World War 2's most successful fighter planes from scratch, in just six months. After the war Toyota incorporated many of the airline industry's findings into its own product development methodology.
Differences between lean product development and lean production
While some basic principles and guidelines are applicable across lean product development and lean production, such as waste reduction, many applications of lean process for development have focused more on the production approach.
The purpose of production, is to manufacture products reliably within margins of control. The flow of value is physically evident and the link between cause and effect is easy to see. For example, feedback on adjusting the speed of production is immediately realized in an increase or decrease in rejected items. Any decisions made mus be based on best practice.
The purpose of product development, on the other hand, is to design new products that improve the life of customers. This is a complex space where the flow of value can only be discerned at an abstract level and cause and effect might be separated by time and space. For example, feedback on the decision to design a certain feature will not be received until the product has been built and is in the hands of the customer. This means that decisions are made on short-cycle experimentation, prototyping, set-based design, and emergent practice. A premium is placed on creating reusable knowledge and reducing risk at handover points.
An essential point about these differences is summarized in the advice Jim Womack gives Harley Davidson: "Don't try to bring lean manufacturing upstream to product development. The application of Lean in product development and manufacturing are different. Some aspects may look similar, but they are not! Be leary of an expert with experience in lean manufacturing that claims to know product development" 
The most common high level concepts associated with lean product development are:
- Creation of re-usable knowledge
- Set-based concurrent engineering.
- Teams of responsible experts. Lean product development organizations develop cross-functional teams and reward competence building in teams and individuals.
- Cadence and pull. Managers of lean product development organizations develop autonomous teams, where engineers plan their own work and work their own plans.
- Visual management. Visualization is a main enabler of lean product development.
- Entrepreneurial system designer. The lean product development organization makes one person responsible for the engineering and aesthetic design, and market and business success, of the product.
Results of lean product development
The following results have been claimed for lean product development:
In the year 2000, Toyota launched 14 new products which is more than whole of GM. At that point, Toyota had just 70,000 employees, while GM had more than five times as many (360,000).
Applicability of lean product development
Researchers divide product development projects accordingly to their need driver:
- Wished: there is no such product on the market, only a wish for such a product. These projects can be on the edge of what is possible to do.
- Wanted: there are only a few basic similar products on the market that usually require improvement.
- Needed: there are enough products in existence so knowledge about this is abundant on the market.
For example: In the 1990s the mobile phone was a Wanted product, it was on the leading edge of technology. Today it is regarded as a Needed product, it is common in the market and there is enough knowledge in the public domain so that even small companies can make a good mobile phone.
Product development methods can be classified according to whether they are focused on handling stable or unstable conditions. Lean product development is a dynamic method of product development that handles unstable conditions.
Putting this together gives us an understanding of how why it is important to understand both need driver and if your projects are deemed short or long compared to market changes and have a product development approach that addresses the situation you face.
|Wanted||moderately non-stable||moderately non-stable||non-stable|
Notes and references
- Kimoto, Shoji (1991). Quest for the Dawn (1st ed.). Dougherty Co. ISBN 1878150014.
- Ward, Allen. Lean Product and Process Development. LEI. p. 3. ISBN 978-1934109137.
- Sato, Masaaki (December 16, 2008). The Toyota Leaders: An Executive Guide (1st ed.). Vertical. pp. 40–45. ISBN 978-1934287231.
- Melvin, Bob. Knowledge Based Product Development: A Practical Guide. CreateSpace Independent Publishing Platform. p. 16. ISBN 1492705969.
- Ballé, Michael; Ballé, Freddy. "Lean Development" (PDF). Business Strategy Review. pp. 17–22.
- Oosterwal, Dantar (January 13, 2010). The Lean Machine. Productivity Press. pp. 131–132. ISBN 978-0814432884.
- Holmdahl, Lars. Visual Management in Lean Product Development. pp. 1–15. ISBN 978-91-979196-1-6.
- Allen Ward - Lean Product and Process Development
- Oosterwal, Dantar (January 13, 2010). The Lean Machine. Productivity Press. pp. 237–240. ISBN 978-0814432884.
- Ottosson, Stig (2006). Handbook in Innovation Management. www.complexityforum.com.
- Holmdahl, Lars. Visual Management in Lean Product Development. pp. 18–20. ISBN 978-91-979196-1-6.
- Lean Product Development Does Not Equal Build, Sorry
- Why Customer Learning Comes Before Building in Lean Startups
- How the Lean Startup Evolved from Lean
- 7 Questions to Consider Before Building an MVP
- Lean Product Development books
- Annual Event: By Lean Product & Process Development Exchange, Inc., a 501(c)3 non-profit organization
- LEAN Product Design By The Huthwaite Innovation Institute
- Annual LEAN Design Summit