Toyota Product Development System


Industry Week Article

Here's a list of 13 principles from the Toyota Product Development System, as explained in the book The Toyota Product Development System: Integrating People, Process And Technology by Jeff Liker and James Morgan.

Is anyone working to apply this system at their company?


Get New Posts Sent To You

Mark Graban is an internationally-recognized consultant, author, and professional speaker who has worked in healthcare, manufacturing, and startups. His latest book is Measures of Success: React Less, Lead Better, Improve More. He is author of the Shingo Award-winning books Lean Hospitals and Healthcare Kaizen, as well as The Executive Guide to Healthcare Kaizen. He also published the anthology Practicing Lean that benefits the Louise H. Batz Patient Safety Foundation, where Mark is a board member. Mark is also a Senior Advisor to the technology company KaiNexus.

  1. David Carlton says

    I’m certainly curious to learn more about it. Lean product development is getting some traction in software development: the ‘agile programming’ community has been growing for the last ten years or so, and recently Mary and Tom Poppendieck have been pointing out to us how much agile programming ideas are like lean product development ideas, and pointing out areas in which we can learn more from lean. I haven’t yet read Liker and Morgan’s book (I’ve just read the Poppendiecks’ books and Michael Kennedy’s book on the subject), but I’ll find time soon.

    I’m especially curious since I work for a company that does hardware design as well as software; lean might be a way for me to apply some of what I’ve learned to other areas of the company.

  2. Ron Pereira says


    I really think you are on to something and hope to hear about your progress!

    Whenever there is a product or service there is a value stream. And whenever there is a value stream Lean is waiting to help.

    Good luck,

  3. JWDT says

    We implemented a form (I call it a form because it wasn’t the exact way) of this at a previous Company. The Engineering processes we looked at were initially Software Development, then we expanded to Hardware Design, etc. The Chief engineer and I came up a with the way, when we mixed what I knew about LEAN & what he knew about rapid prototyping. We figured out the thing we were missing was how we capture & maintain the different “modules” lessons learned & design CTQ’s. Long story short, we took an historical 18-30 months SW cycle down to less than 4 months, with a concept to monetized design (customer purchasing new units) from 3-5 years down to roughly 12-13 months. Using this. As with most things at this former company, I was forced to move on because I was not leadership material, he was eventually pushed into another area because several others ‘ladder climbers’ stole his thunder & received the credit for the work. What is interesting is that now that we are out of it, the new products are reverting back to the old processes.

    So yes, it does work and can work in a very short period of time (we began in April/May of 2005, with noticeable improvement by November/December 2005 results. These tracked all through 2006.

Leave A Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.