Continuous improvement

Nov 5 2018

Vade retro, Pareto ! | Cécile Roche | LinkedIn

Vilfredo Pareto (1848-1923)

“Vilfredo Pareto was a respected economist and sociologist, which few people know. He invented the theory of Pareto optimality, which describes a maximum efficiency of the competitive economy. Better known to the general public for his empirical law of 80/20 (in general, 20% of the causes generate 80% of the effects), his reputation is in reality often reduced to the use of the diagram of the same name (that he did not even invent!)

And that’s where things go wrong. I’m sure you know this famous diagram, the one where you stack problems in pre-labeled columns. Those who know me know that most of the time, these famous diagrams (actually invented by Joseph Juran) generate in me a reflex of distrust…”

Sourced from LinkedIn Pulse

Michel Baudin‘s comments: Cécile Roche’s article has a clever title that works in English as well as in French. The body of the article, however, is in French, and I recommend Google-translating it into the language of your choice. The result won’t be perfect but you will get the gist.

Her experience with Pareto diagrams confirms the points I have been making about them in this blog. I agree with Cécile’s conclusions that they are good for slides but not as drivers for actual change. On the other hand, I don’t believe it has to be that way and I see many practical uses for the analysis behind the diagrams, if not for the diagrams themselves.

Continue reading…

By • Blog clippings • 5 • Tags: , ,

Aug 15 2017

Using videos to improve operations | Part 8 – Video Repositories

The seven articles I posted four years ago on the art of using videos to improve operations included no pointers on what to do with the videos once you have them. This concern may seem premature in a manufacturing world where video recordings of operations are still rare, process instructions are in dusty binders and obsolete, customization specs come in the form of all-uppercase text from a 30-year old dot matrix printer with a worn-out ribbon, engineering project records reside in individual employees’ laptops, and management expects IT issues to be resolved by implementing a new, all-in-one ERP system.

In everyday life, on the other hand, videos are already in common use to explain how to pry loose a stuck garbage disposal, remove a door lock, change a special bulb in car headlight, or neatly cut a mango into cubes. You just describe your problem in a Youtube search, and up come videos usually shot and narrated by handy amateurs, and sometimes pros. It is particularly useful for tasks involving motion with key points that are difficult to explain with words or still images. The manufacturing world will eventually catch up.

Continue reading…

By • Information Technology • 1 • Tags: , , , ,

May 31 2017

Flattening the Organization- Problably Not the Answer | Gregg Stocker

“One of the misconceptions about lean thinking is that it automatically leads to flattening the organization. Many people think that layers of management are always a bad thing and start removing layers as a way to empower employees, speed up decision-making, and improve innovation. While there is no shortage of organizations that suffer from too many layers, it should be noted that flattening does not necessarily lead to improved performance. Many organizations that flattened their structures have experienced little more than burned out managers, frustrated employees, and high turnover.”

Sourced through Lessons in Lean

Michel Baudin‘s comments: For the second time in a week, I am clipping a post from Gregg’s blog but I can’t help it if I find his writings worth sharing. In my experience, “flattening the organization” is particularly harmful on the shop floor. I have heard managers brag about their structure being “lean” because they had only 1 supervisor for 100 operators. This isn’t what Toyota does in car assembly, where operators work in teams of 4 to 6 and you have a first-line manager for 4 to 6 teams. This means that the number of operators for a first-line manager ranges from 16 to 36, with a mean that is actually around 17. This low number is designed to allow the first-line managers to help operators in their professional development and to lead improvement projects. A supervisor with 100 direct reports can do neither.

#LeanManagement, #First-LineManager, #ShopFloor, #ContinuousImprovement

By • Blog clippings • 0 • Tags: , , ,

May 21 2017

Driving Improvement Through Systems Thinking | Gregg Stocker

“[…] When starting an improvement effort, I usually ask about the minimum target the team is attempting to achieve.  The answer is often something made up on the spot or a generalization, like as much as possible.  Improvement efforts should generally be driven by the actual requirements of the business.  For example,  if a company determines that the time between a customer placing an order and receiving the product is too long, it should determine an improvement target based on what the business needs.  If it currently takes 42 days and customers expect to receive the product in 22 days because of their needs or what competitors are offering, the minimum improvement needed is 20 days.[…]”

Sourced through Lessons in Lean

Michel Baudin‘s comments:

Gregg Stocker illustrates abstract principles with concrete examples, which makes his meaning clear and unambiguous. The above excerpt is meant to show the need for employees and managers to understand the consequences of local actions on the organization as a whole. As he points out in the rest of his post, it’s not always easy.

Continue reading…

By • Blog clippings • 1 • Tags: , , , ,

Mar 3 2016

Improving  50% is easy, improving 5% is difficult | Chris Hohmann

“It is with this enigmatic sentence that one of my Japanese mentors introduced the growing difficulty with continuous improvement. What it means is that at the beginning of an improvement program or when starting in a new area, the first and usually the easiest actions bring big improvement, hence the “easy” 50%. This is also…”

Sourced through Scoop.it from: hohmannchris.wordpress.com

 

 

Michel Baudin‘s comments:

I have been using this method, but for the categorization of improvement ideas within a project rather than whole projects. For example, starting a SMED project on a machine with a 30-minute setup time, you find that you can get it down to 12 minutes in one week for $300 by organizing and prepositioning tool carts. This is your A idea.

Then you find that, by modifying a fixture on the machine, you can get it down to 4 minutes, in three months for $5,000. That’s your B idea. Finally, you discover that an automation retrofit can get it down to 2 minutes, in a year for $50,000, and it is a C idea.

The one issue I have with applying this kind of thinking to whole projects is that the scope of “low-hanging fruits” changes over time with the skill level of the work force. Much of what appears inaccessible at the outset of your transformation becomes cheap and easy by its third year.

I also find that how long and how much money it will take to implement an idea is easier for teams to work with than a metric like ROI. The economic justification of improvement projects is a difficult and sensitive subject.

See on Scoop.it – lean manufacturing

By • Blog clippings • 1 • Tags: , , ,

Jan 26 2016

Is Vendor Selection Really The First Step in ERP Implementation?

A free guide that you can download from ERP Focus makes vendor selection the first of an 11-step implementation process, while defining success is the last.  In other words, they have you choose who you buy from before having a clear idea of what you are trying to accomplish.

It reminds me of a meeting at a client site where ERP implementation was about to begin. “This train has left the station,” I was told. The purpose of the meeting was to draw a “Value Stream Map” for the whole plant, in preparation for ERP, and the participants included managers from Manufacturing, Quality, Production Control, Maintenance, Purchasing, Sales, and Engineering.

Continue reading…

By • Information Technology • 3 • Tags: , ,

1 2 3 4 5
%d bloggers like this: