Tag Archives: five minute lean

Excerpts From The Five Minute Lean Book

Like the book or want to share it with others?  Share this page and get the book on Amazon.

Five Minute Lean

Selected chapters from the story within Five Minute Lean:

Check out these selected chapters from the teachings within Five Minute Lean:

 

Want to learn about Lean? Get the book "Five Minute Lean", by David McLachlan - a wonderful book that blends teaching of the tools, culture and philosophy of traditional Lean with a modern-day Lean parable. You can get the whole book on Amazon here and enjoy your own copy.

Five Minute Lean – Solve the Real Cause of the Problem

Five Minute LeanThis is an excerpt from the book "Five Minute Lean", by David McLachlan - a wonderful book that blends teaching of the tools, culture and philosophy of traditional Lean with a modern-day Lean parable.

You can get the whole book on Amazon here and enjoy your own copy.

Solve the Real Cause of the Problem

‘Using a Fishbone diagram and the 5 Whys is a fast and easy way to get to, and solve, the real cause of a problem.’

Implementing solutions to problems in our job or business often takes time and money to do.  Many people spend this time and money only to discover they were solving the wrong thing – addressing only the symptoms and not the actual cause.  Using the power of Root Cause Analysis can help us discover and solve the real problem and avoid this waste.  Problems are also wonderful opportunities – if we can solve the real problem it can make our job easier and far more enjoyable.

When we have a specific problem that we need to solve, it is extremely important that we:

  • Clearly define the problem we are working on, before we begin.

This means we “go and see” the problem, directly where the work is done (at the Gemba, 2.2) and hopefully as soon as it happens (with Jidoka, 4.2).

It also means articulating the problem specifically as a gap from where we are to where we want to be, based on something measurable like our customer driven metrics (Quality, Delivery, Cost or Sales, 1.2) or reducing one or more of the eight wastes (3.1).

For Lisa this might mean reducing wait time in a queue from 10 minutes (where she is) to five minutes (where she wants to be) instead of just saying “less queue time”.  Defining a problem in this way also makes it easy to know when you have succeeded – you are not chasing a vague concept.  And because you have defined the problem as a measurable gap, it is also easier to present a clear view from the problem, to a solution.

During our Kaizen meetings, while mapping our process, or even when walking the Gemba, we may need to get to the real cause of these problems we reveal.  To do so we use a Fishbone diagram and the “Five Whys”.

Fishbone or Ishikawa Analysis

A Fishbone diagram is used to get a quick idea of where the cause of our problem might lie by separating ideas into categories.

The four categories are:

  1. People
  2. Information
  3. Process
  4. System

An easy way to remember them is “PIPS”.

In Manufacturing, the four categories can also be known as the “Four M’s”: Man and woman, Materials, Method, or Machine.

To use a Fishbone diagram, Lisa would note her clearly defined problem at one end, the “head” of the fish.  She could then have her team-mates call out reasons why they believe the problem is happening.  These reasons would be noted under any of the four categories, depending on where the cause lies.

As usual, a picture says a thousand words:

fishbone diagram

Figure 15: An example of a Fishbone or Ishikawa diagram, noting reasons under People, Information, Process and Systems.  Once complete, we can group similar problems or reasons together and then perform the Five Whys.

Once she had a few reasons, Lisa could group them together further.  For example, there might be a few reasons that relate to how people are trained, or others that always come back to a certain department.  This allows her to narrow down her causes effectively into one or two main reasons, and she can then delve even deeper with the Five Whys.

The Five Whys

Once we have an idea of where our problem lies using a Fishbone diagram, we can use the Five Whys to delve deeper into any of the main reasons that we have come up with, if we need to.

To perform the Five Whys, we ask “Why” this is happening, and with each new answer ask why again until the answers have been exhausted or we need to gather more data.

Let’s say that in one of the process steps at the Shoe Emporium Lisa identified that there is a high rework percentage, perhaps 50%.  Maybe it’s a form that doesn’t get filled out correctly and needs to be re-done.

The conversation might go a little like this:

Why does the form come back for rework 50% of the time?

 1.  The customer doesn’t fill it out correctly

Why?

2.  They don’t feel like they have to, or they don’t understand it

Why?

3.  We haven’t explained the importance of the form or how to fill it out

Why?

4.  We don’t focus on building in quality when gathering the information, and it is too easy to make a mistake.

In this scenario we didn’t need all five “whys” – this is OK.  The main point is to keep asking until the answers have been exhausted, or we need more information.  We also know our Five Whys are working when we can go back up the line of questions and replace “Why” with “Therefore”.

For example:

4.  We don’t focus on building in quality when gathering information

Therefore:

3.  We haven’t explained the importance of the form or how to fill it out

Therefore:

2.  Our customers don’t understand it

Therefore:

1.  Our customer doesn’t fill it out correctly and it comes back 50% of the time.

Once you have narrowed down your answers, you can add the real problems into your Value Stream Map as Kaizen Bursts, and brainstorm solutions with your team-mates.

When you are brainstorming solutions, you can use ideas from Chapters Three, Four and Five to help you.  This will give you tools such as having a standard process, error proofing or stopping when a defect is found, working towards one-piece flow, then changing how people are measured or rewarded and making information, process steps, queue times or other things visible, which can all have a huge impact.

It is also a good idea to use the 5 Whys on our processes – as in “Why do we do this step?”  In many cases a process may have been created long ago and things have changed or moved on, leaving the process unnecessary.  If the only reason for doing something is because “this is the way it’s always been done,” then thank goodness you are going through a Lean transformation!

Five Minute LeanThis is an excerpt from the book "Five Minute Lean", by David McLachlan - a wonderful book that blends teaching of the tools, culture and philosophy of traditional Lean with a modern-day Lean parable.

You can get the whole book on Amazon here and enjoy your own copy.

Selected chapters from the story within Five minute Lean:

Check out these selected chapters from the teachings within Five Minute Lean:

Five Minute Lean – Go to the Gemba

Five Minute LeanThis is an excerpt from the book "Five Minute Lean", by David McLachlan - a wonderful book that blends teaching of the tools, culture and philosophy of traditional Lean with a modern-day Lean parable.

You can get the whole book on Amazon here and enjoy your own copy.

Go to the Gemba

‘To truly know a process we must go to where the work is done – second hand information will not suffice.’

Now that we know what brings our customer value from chapter one, we can use the following tools to map out the process of creating that value so everyone can see it clearly and use it to move forward.  For this reason, the Lean Enterprise Institute calls this step “Map”, and a good map will also reveal opportunities, problems and “waste” (3.1) in a process.  We will go through all of these in this chapter.

We also started this book by saying that most businesses don’t have an existing standard, repeatable process for their work.  Mapping the process is an easy way to articulate the current way of working, to use as a makeshift standard process before you start improving it.  After all, you can’t improve something you don’t have.

First, in order for us to truly know a process we have to go to where the work is done.  In Lean this is called going to the “Gemba”, and Gemba is the Japanese word for “Actual Place”.

In a Lean transformation, getting reports on a situation or hearing it from someone else (like a team-mate or a manager reporting to you) is not good enough.  To find out the true situation we must go and experience it first-hand, preferably every day.

This could mean:

  1. Walking the Gemba (going directly to where the work is done), spending time with the people and asking questions or mapping the process as you go.
  2. Involving people from the front lines in a Kaizen Event (2.2) as you map a process and get to the root cause of problems, and;
  3. To a lesser degree, using an LCA Board (5.2) to track metrics of front-line processes.

But it doesn’t just mean going to where the work is done.  It also means that we “go and see” as soon as a problem occurs, so we can get our team-mates’ consensus on what the problem might be before we try and solve it.  While this may seem like more work initially, it will save you many hours of wasted effort in the future as a problem gets older or becomes embedded in the workplace culture.

If you are an employee like Lisa, you will already be very familiar with your process, and this book will give you a great way to visualise problems and the tools you need to solve them.  If you are a manager or an owner like Steve, you may be more removed from the front-line process during the course of your daily work, which is another reason why learning to regularly go to the Gemba to see and experience for yourself is worth many times its weight in gold.

If you are not sure of a problem, or even a solution, nothing can replace the experience of actually going to where the work is done.

Five Minute LeanThis is an excerpt from the book "Five Minute Lean", by David McLachlan - a wonderful book that blends teaching of the tools, culture and philosophy of traditional Lean with a modern-day Lean parable.

You can get the whole book on Amazon here and enjoy your own copy.

Selected chapters from the story within Five minute Lean:

Check out these selected chapters from the teachings within Five Minute Lean:

Five Minute Lean: Glossary

Five Minute LeanThis is an excerpt from the book "Five Minute Lean", by David McLachlan - a wonderful book that blends teaching of the tools, culture and philosophy of traditional Lean with a modern-day Lean parable.

You can get the whole book on Amazon here and enjoy your own copy.

Five Minute Lean Glossary

5S

A method of organising a workplace to improve safety and efficiency.  The 5S steps are: Sort, Straighten, Shine, Standardise, and Sustain.

5 Whys

A method of getting to the root cause of a problem, where we keep asking “why” until the real issue is revealed.

8 Wastes

Also “Muda” in Japanese, the eight wastes note the most common forms of waste in company processes that increase costs and inefficiencies.  Our aim in Lean is to eliminate them all.  They are: Defects, Over Production, Waiting, Non-use of Time and Talent, Transport, Inventory, Motion, and Excessive Processing.  Two additional inefficiencies are Overburden (Muri) and Unevenness (Mura) in a process.

A3

An A3 is a single page that shows the details of a Lean implementation at a glance.  It will include a clearly defined problem, then items from the “Plan, Do, Check, Act” cycle with analysis such as root cause diagrams, process maps, action registers and metrics for determining if the implementation is having the desired effect.

A/B Testing or Split Testing

Split testing is the method of testing different versions of the same product, message or process at the same time and gathering the results to determine which works better.

Agile

Agile is a method of implementing a project or change based on short, quick iterations in order to gather feedback as quickly as possible.  This allows us to determine if our project is on the right track so we can either continue or adjust.

Andon

A Japanese term for “light” and a part of Visual Management, an Andon is where the status of a process or operation is shown at a glance, using a light, such as with green (for go) or red (for stop) signals.

Autonomation (Jidoka)

Where machines and/or team-mates have the ability to detect when something is wrong and immediately stop work, so the root cause can be found quickly and solved.

Batch Processing

The enemy of Lean and smooth flowing processes, this is a mass production approach where product is created regardless of whether it is required, and often results in overproduction and waste.

Capabilities, the Four

As defined by Steven Spear in “The High Velocity Edge”, the Four Capabilities were found to be in high performing leaders and are as follows: designing their work to reveal problems & opportunities, swarming those problems to solve them and build new knowledge, sharing that knowledge throughout the organisation, and developing the first three skills in everyone else.

Chunking

Chunking is the process of taking a large problem or project and breaking it into chunks to make it easier to solve or implement.

Customer

A “customer” in Lean terms is defined as any process downstream from the current one.  The end customer, of course, is the one who ultimately buys a product or service.

Cycle time

The total time it takes to complete a process step within our value stream.

FIFO Lane

First-In-First-Out lane, where items that come in first ultimately go out first.

Fishbone Diagram

Also known as an Ishikawa diagram, this is a method of getting to the root cause of a problem where you note the effect or problem at the “head” of the fish, then the causes you can think of under the “bones” of People, Information, Process or Systems.  Similar causes are grouped and whichever group has the most causes is typically looked at first.

Flow

The Flow of a process is how well it moves continuously from upstream to downstream processes.  Improving Flow involves reducing wasteful steps or interruptions and improving efficiency from the time a customer places an order to the time a product or service is completed and delivered.

Jidoka

See Autonomation

Gemba

The Gemba is the Japanese term for “Actual Place” and is often used as a single word to describe the front lines where the work is done.  In English it can also be spelled Genba.  “Walking the Gemba” is a large part of Lean which means we must go to where the work is done to get the real answers and not rely on reports or second hand information.

Just in Time

Just in Time is a system of production that makes and delivers only what is needed, when it is needed.  It combines five Lean elements for success: Takt time or customer demand, Continuous Flow, a Pull System, Line Balancing, and removing Waste.

Kaizen and Kaizen Events

Kaizen is the Japanese term for “Improvement” and is most often referred to in English as continuous improvement.  A Kaizen meeting or event, therefore, is an improvement meeting where we go through the “Plan, Do, Check, Act” process or the five steps outlined in this book.

Kanban

Literally “sign” or “sign-board” in Japanese, Kanban in its many forms is most used as a trigger for upstream suppliers to produce more product.

Kanban Board

Used in Agile, a Kanban Board is a visual way to manage work and consists of cards with small pieces of work on them assigned to a team-member and moved along columns such as “To Do”, In Progress”, and “Done”.  Columns can also be named depending on your own work phases or departments.

Kano Analysis

Kano analysis divides customer feedback (the Voice of the Customer) into Dissatisfiers, Satisfiers and Delighters where the aim is to increase Delighters and remove Dissatisfiers.

Kata

Brought to the world’s attention in “Toyota Kata” by Mike Rother, Kata involves three main steps:

  1. Grasping the current situation,
  2. Defining the desired situation, then;
  3. Moving toward that goal in iterations so as to uncover feedback or obstacles.

LCA Board

A Layered Check Act board is a method of visual management.  Usually a board will be at least one to two meters in diameter, and it shows the metrics of a current process measured against the proposed targets.  If the metrics are not meeting these targets, then countermeasures are added (often after a Lean initiative) to assist in bringing them into line.

Lead Time

The total time it takes to create your product or service from the moment the customer orders to the time it is delivered, including both Value-Add and Non-Value-Add time.

Line Balancing

Line Balancing is based on the premise that a process is only as fast as its slowest step.  Based on this, in many cases we can combine faster processes together, provided they are still faster than Takt time or customer demand.  This means we can also split longer steps up to ensure they are under Takt time.

Net Promoter Score

The Net Promoter Score is from the book “The Ultimate Question 2.0”, where we ask our customer “On a scale of 1 to 10, how likely are you to recommend our product / service to a friend?”  The results are often used in conjunction with Kano Analysis.

Overburden (Muri)

Overburden or Muri is where team-mates or equipment are required to work harder, faster or more than is necessary, often because of wasteful steps or processes.

Pareto Chart

A Pareto chart is based on the idea that 80% of results come from approximately 20% of the effort.  It shows item measurements in a bar chart, and the cumulative percentage in a line graph overlaying the chart.  In this way, we can see which items will have the greatest impact when fixed, and focus on these first.

Poka Yoke

“Error-Proofing” in Japanese, this means putting steps in place to make it impossible to make a mistake.  A USB cable and port, or an electric plug is a good example of this.

Problem Charter

Problem charters are often created at the beginning of a larger project.  They often include: The stated problem, the current situation, the impact it has, the stakeholders or problem owners and any team members assigned to the problem.

Pull

A Pull System is one where downstream departments signal their needs to upstream activities (often using a Kanban), allowing them to pull work in accordance with demand.

Push

The opposite of Pull, where upstream departments create product regardless of demand, and push it through to their downstream customers.  This can result in waste such as over-production, over-burden and over-processing.

Silo

A silo in a company is when a management system, process or department is cut off from the rest of the business or unable to communicate with other sources of company information.  This can result in misinformation, miscommunication, slower processes and lower morale.

SIPOC

A SIPOC chart shows the Suppliers, process Inputs, Process steps, process Outputs, and Customers.  We can also add Customer Requirements, and Measures of a process as well.  It gives a “high level” view of the process steps, and is a good foundation for other tools on larger projects, especially when we need to know the stakeholders involved.

SMED / Quick Changeover Techniques

Single Minute Exchange of Dies (SMED) is a process of changing over equipment (or people, stations, or anything else you might think of) from one to another in as little time as possible.  It is based on Internal changeover operations that can only be done when the process is stopped, and External operations that can be done while the process is still going.  The aim then becomes to convert all Internal changeover operations to External changeover operations to simplify and speed up the changeover process.

SOP

A Standard Operating Procedure (SOP) is a standard, repeatable way of carrying out a process.  Often in writing and better still in the form of a checklist, using a SOP ensures staff operate the same way.  It makes it easier to train, easier to quality check and helps reduce single points of failure if staff are sick or on holidays.

Spaghetti Diagram

A Spaghetti Diagram is a diagram of a production floor with lines following the product as it travels through the steps or workstations.  Often initially a diagram will look like cooked spaghetti as the product goes back and forth and around a workspace.  Simplifying this movement can significantly reduce waste.

Supermarket

A Supermarket in Lean terms is a predetermined standard inventory kept to supply a downstream process.  Keeping no more than is needed, when a supermarket is empty a Kanban is often sent to the supplier to replenish the standard inventory.

Supplier

Any workstation, department, person or company that is upstream from the current process.

Swim Lane Chart

A flow chart of process steps where departments or stations are noted vertically, and the steps are noted horizontally.  In this way, we can clearly see movement between departments and potential wastes.

Takt Time

The product demand time as determined by the Customer.  For example if a Customer buys 80 items in an 8 hour work day, our Takt Time is 10 items an hour.

TPM

Total Productive Maintenance (TPM) is a set of techniques to improve usability and longevity of machines.  It involves cleaning and repairing, performing error proofing, developing a maintenance database and a standard process for continuing maintenance in the future.

Unevenness (Mura)

Unevenness or “Mura” in an operation is when a process has excessive wait time followed by excessively busy periods.  In other words, team-mates are forced to “hurry and then wait”.  Not only does Unevenness in a process reduce morale, it is often a wasteful use of team-mates’ time and resources.  Unevenness can be reduced by using Line Balancing, working towards One Piece Flow, and reducing Rework in a process.

Value

Value is always defined by the Customer, and in its purest form it is something within a process that a Customer is willing to pay for.  For example making a product’s process simpler may not directly add value to a customer, however the cost reduction, speed of delivery, and increase in quality or savings to a customer will.

Value Stream

A Value Stream is the process of creating our product or service – it is the “stream” of process steps that create our product to bring value to the customer.

Value Stream Map

Also known as a VSM, this is the standard method of mapping out a process, often including the Suppliers and Customer, Systems, Process Steps, Process Timings, Rework and any other useful information.

A “Future State VSM” is created when you have analysed a current process and want to show the new process with added value and without the waste.

VOC

The Voice of the Customer (VOC) refers to data captured around customer metrics or feedback.

Work in Process

Also known as Standard Inventory, it is the minimum number of items or parts (including parts in machines or queues) needed to keep a workstation or department flowing smoothly.  A Supermarket is a good example of this.

Five Minute LeanThis is an excerpt from the book "Five Minute Lean", by David McLachlan - a wonderful book that blends teaching of the tools, culture and philosophy of traditional Lean with a modern-day Lean parable.

You can get the whole book on Amazon here and enjoy your own copy.

Selected chapters from the story within Five minute Lean:

Check out these selected chapters from the teachings within Five Minute Lean:

Avoid This Deadly Trap Of Failed Lean Transformations

Everything Has a Honeymoon Period

When companies begin a Lean transformation, there is often an air of excitement that surrounds it.  After all, you already know (and if you don’t a quick Google search will reveal) the huge benefits a business can gain from going through Lean process improvement, namely:

  • Improved quality
  • Reduced defects and rework
  • Improved lead times and faster processes
  • Less burdensome work and happier employees

The potential can seem so great, that anything touched by the hand of Lean during the honeymoon period can seem to do no wrong.  But what happens when Lean has been a part of your company for two years?  Five years?  What about 10 years?  Employees know  lip-service when they see an idea with a distinct lack of follow up, and it doesn’t take long for them to brand your potential improvements as “just another fad”.  When this happens, it can be very very hard to bring back your improvement initiative from the brink.

And here’s the real kicker: it’s not your fault.  You had the best of intentions.  You thought you were doing all the right things.  You read the books, you hired the “gurus”, you attended the seminars.  But you didn’t know about the one deadly trap that you absolutely must avoid during your Lean transformation.

The Deadly Trap: Educate To The Lowest Level Of Your Company Or You Will Fail

The simple fact is you need to teach Lean from the very top to the very bottom of your organisation, or your initiative will fail.  You need management to be well versed and on board, otherwise projects will find it hard to get off the ground.  You also need front line staff – team-mates from the Gemba – to know the improvement methods so they can use it to improve their job and your business every day.  This is extremely powerful stuff.

Teaching it company-wide gives you passionate business-improvers at all levels of a company.  You now have people working in the Gemba who know how to map and improve their process as part of their job.

You see, the power of Lean is in its simplicity.  Yes, there are things to learn and yes you will need to think differently, but in the end the message is simple: Map your process, reduce wasteful steps, use a Pull system, build in quality or error proofing and experiment in a controlled space until you win.  This means that:

  • Lean can be easy to explain to others
  • When it is easy to explain, it is easy to share
  • When it is easy to share, it is easy to teach
  • When it is easy to teach, it is easy for many people to take advantage of the tools and lessons

And that is the power of Five Minute Lean.  A simple message with a simple “toolbox” of improvement techniques that fit seamlessly together.

We Want Momentum, Not Inertia

Teaching Lean to all levels of a company also helps us build momentum for our change initiative.  Momentum has a habit of growing, like a snowball rolling down a hill gathering speed.

On the flip side, for every person who doesn’t understand Lean properly, you can consider each one an anchor thrown over the side of your boat, slowing you down until you are forced to stop all together.  They will either passively or actively dismiss your Lean transformation, and both are extremely dangerous.

Find A Way To Teach Others Easily

If you can find a quick, simple, waste-free way to teach and get your team-mates involved on your Lean journey, you will win.  In fact, everyone will win, as processes become easier, faster and less burdensome.  A great place to start is my book – Five Minute Lean – where the chapter titles double as a standard process checklist that anyone can use and learn from.  Having this in the hands of each of your team-mates can do amazing things.

Yours in change,

David McLachlan

Get the Leadership Card Deck or the Five Minute Lean Book:

Leadership CardsView All The Leadership Cards (48)

- or - Have the Leadership Cards delivered for your next meeting

 

Want to learn about Lean? Get the book "Five Minute Lean", by David McLachlan - a wonderful book that blends teaching of the tools, culture and philosophy of traditional Lean with a modern-day Lean parable. You can get the whole book on Amazon here and enjoy your own copy.