Record of Annual WSJ Just-in-Time / Lean Blunders

10
8

The Wall Street Journal, sadly, has a long track record of not understanding Lean, as I've written about many times on my blog. There's a major flare-up at least once a year, as listed below:

2011:  

2010:  

2009:

2008:

2007:

2006:


What do you think? Please scroll down (or click) to post a comment. Or please share the post with your thoughts on LinkedIn – and follow me or connect with me there.

Did you like this post? Make sure you don't miss a post or podcast — Subscribe to get notified about posts via email daily or weekly.


Check out my latest book, The Mistakes That Make Us: Cultivating a Culture of Learning and Innovation:

Get New Posts Sent To You

Select list(s):
Previous articleLean Parody Audio & Video: GEICO Commercial
Next articleMental Models: Standardized Work and Performance Measures
Mark Graban
Mark Graban is an internationally-recognized consultant, author, and professional speaker, and podcaster with experience in healthcare, manufacturing, and startups. Mark's new book is The Mistakes That Make Us: Cultivating a Culture of Learning and Innovation. He is also the author of Measures of Success: React Less, Lead Better, Improve More, the Shingo Award-winning books Lean Hospitals and Healthcare Kaizen, and the anthology Practicing Lean. Mark is also a Senior Advisor to the technology company KaiNexus.

8 COMMENTS

  1. The most recent 2011 WSJ bad piece on Lean/JIT:

    http://online.wsj.com/article/SB10001424052748703916004576271631993174792.html#articleTabs%3Darticle

    This article is full is mis-perceptions about Lean that the business world (and the WSJ) are still trying to recover from. Back in the 1980’s, most thought that Lean was just about just-in-time materials, supply chain, inventory, and production scheduling practices – people missed the broader management system of Lean and Toyota. This broader management system is really a total business system (see lean.org or the book The Toyota Way for more modern definitions of “lean.”)

    Another comment is correct that JIT was designed for local deliveries and supply chains within Japan, a small country where warehouse space was at a premium in factories. Toyota has more inventory in its supply chain when bringing parts from Japan to North America then they would for a supplier in their San Antonio plant and local business park. If companies are bringing parts across the ocean on a boat from China, you can’t do JIT. But you can still be a “lean thinking” company. It’s not all about zero inventory.

    Lean and JIT has never meant to be a substitute for thinking.

    If you have long supply chains, highly variable demand, or lots of risk in your supply chain, why would you assume JIT or Lean are possible? We are still recovering from an unfortunately titled book “Zero Inventories” from the 1980s. Executives apparently didn’t read that the title.

    Lean is about continuous improvement and total business effectiveness. It never was all about low inventory.

    These companies and this article miss the point. We can’t say “shame on Lean” but rather “shame on the companies that misapplied it” unless they companies learn and change their practices going forward. That’s a learning organization and that’s what Lean is really all about.

    One other thought – people say JIT is liable to disruptions. What if Japanese companies had huge factories pull of parts sitting there? The parts might have been damaged in the earthquake and tsunami. No production system can protect you from huge catastrophes. Truly lean supply chains are more flexible and allow companies to respond faster after disasters (such as Toyota’s quick recover from previous supplier plant fires and earthquake damage in past years).

    Here’a a consolidated record on how the WSJ usually gets it wrong on Lean/JIT; https://www.leanblog.org/2010/08/record-of-annual-wsj-jitlean-blunders/

LEAVE A REPLY

Please enter your comment!
Please enter your name here

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