WHY is asking "WHY" so important?

How many times have you thought you have solved a problem just to be plagued by its unwelcomed return? This is not only frustrating for you but think of the team members within your company trying to do their job and the "same ole" problems are hindering them each day. By NOT getting to the root cause of a problem this situation can be a costly act for the company, as well as break the mutual trust between you and your workforce since a leader's responsibility is to serve their customers (the team members).

It is important to ask WHY repeatedly when visiting the GEMBA to determine what is current happening versus what should be happening. In many cases we stop at a symptom to the problem because we are often pressured for results and quickly solving the problem without going past the symptom seems to be the best answer.

By repeatedly asking WHY, you can practice the "Go and See" trait to uncover the layers of symptoms that can lead to the root cause of a problem. Very often the first reason for a problem will lead you to another question then to another. Although some label it the "5 WHY's" you may find that you will need to ask the question fewer or more times than five before you find the issue that is responsible for the problem.

An important key factor to asking WHY is to determine the Cause and Effect relationship between the WHY's. This shows the relationship of given factors or cause that lead to the given situation "or effect" that is happening with the process. A rule or practice that I use is asking WHY or BECAUSE downward as we identify the root cause, and then to test the logic we ask THEREFORE upward back to the problem.

For example:

My car will not start (the problem)
WHY? The battery is dead (first why)
WHY? The alternator is not functioning properly (second why)
WHY? The alternator belt was broken (third why)
WHY? The alternator belt had worn over time (fourth why)
WHY? Owner had not replaced belt at recommended interval (fifth why) - ROOT CAUSE

So what happens if we keep asking WHY? How do we know when to STOP?

A couple of common rules I tend to teach by is:

• when the problem changes context by asking another why.
• when we tend to blame behaviors in people.
• when it is out of our control or scope.

Let's look at an example that ask WHY too many times.
I overslept today (The problem)

• WHY? My alarm clock didn't go off
• WHY? The clock wasn't registering the time
• WHY? The Clock was flashing on and off
• WHY? There was a power failure or interruption
• WHY? Lightning hit a nearby transformer
• WHY? There was a storm
• WHY? Barometric pressure changes in the atmosphere
• WHY? Hot air and Cold air interact
• WHY? Seasonal changes on the Earth
• WHY? The Earth rotates.

When did we need to stop in that chain of WHYS? When could we have effectively countermeasured the problem?
If you are countermeasuring "storms" or "earth rotation" you have gone too far, this is out of your control. Will countermeasuring the storm solve the actual problem of oversleeping? These are the questions you ask to determine when you are at the actual root cause.
So the next time you are at the GEMBA remember a few of these rules to effectively getting to root cause and past a symptom. This will not only help your team members but effect cost and productivity as well. Till next time,
@tracey_san
Tracey Richardson

The Seven Mudas (Wastes)-- Are you recognizing them?

What is WASTE? What does it mean to a Company or to the Customer? When we talk about waste within a company we tend to classify it as any activity that takes up company resources that does NOT create value for the customer. Some say its work the customer is NOT willing to pay for. The problem is for many companies they do not recognize waste and tend to pass on these hidden costs. I suppose this is acceptable if the customer is willing to pay for it, but its optimal when a company can recognize its waste, therefore not passing this on. If recognized it can potentially create more profit for long term sustainability and job security. Its a win win situation for both the customer and company.

So what are we looking for out there? Do we have a process for recognizing waste?

Within the Toyota Production System, Taiichi Ohno put waste into Seven different categories:

• Over Production
• Waiting
• Conveyance
• Over Processing
• Inventory
• Motion
• Correction

Let's take a look at these a little closer.
Over Production happens when "Just in time" to the customer isn't followed. It allows you to produce, because you can, at a rate that is normally faster than customer demand. These products are then "stockpiled" for a "rainy" day or whatever reason to meet the need at any given time. This waste normally "hides" or "masks" problems since there are plenty of parts stored in any empty space found (Sometimes even warehouses). This is one of the worst waste categories there are because it leads to excess Inventory (another waste) which leads to increasing costs for the company and customer. Other aspects companies do not think about is the Quality control processes with Over Production, it is very hard to control versus a first in first out process.
Waiting takes place when an operator may have idle time when waiting on machines, parts, or production. If fluctuations happen in production volumes, waiting can be seen as more than process related. Entire lines can be effected by Over production, and part shortages can create a snowball effect to others in the process. As you will see these 7 Wastes are all interrelated.
Conveyance is necessary to many production areas in the form of "water-spiders" or production control logistics due to the nature of transferring parts from place to place. Many consider Conveyance itself to be muda or waste. What companies must look at is "how" we transport product or materials and are we doing it the most effective/efficient way. It's important to look at the shortest routes, maximizing space on the truck, the Heijunka (part leveling) of parts taken (highest demand to lowest) and contain sizes. These are just a few ways to look at waste in conveyance.
Over Processing is the one most often confused with Over Production. What is the difference you may ask? Over-processing is happening within a process at the Gemba (work-site)....it can be equipment, resources or people related. For example, if a machine/mold is responsible for cutting out the sunroof opening on the Roof Headliner wouldn't you want that machine to do it in the most efficient and effective way possible. One of the lessons the Japanese taught me was to look for unnecessary motion in equipment. In this case was the machine traveling open too far creating extra time for the cycle time? If the machine time could be cut by 10 seconds it can prevent team members waiting on the machine and add more value to the process instead. These are the types of Over processing wastes we were taught to look for in regard to equipment. Its a very common waste most overlook.
Inventory is related to Over production. Its a very costly waste to the company in regard to excess space, storage and quality control methods. Again it happens when "just in time" isn't being followed to customer demand or takt time. This can be in the form of raw materials, work in process, and finished parts.
Motion is one of my favorites to look for at the GEMBA. These are motions within the process that do NOT add value to the customer or product. These can be see as excess walk time, simple actions of picking up a hand full of screws and orientating them in your hand correctly, reaching too far or in unacceptable ergonomic positions, repetitive actions not being streamlined, and many others in regard to an operators path in completing their work or parts orientation. Sometimes motion can be interrelated to the Heijunka of parts coming down the line, if a flow rack isn't correctly stocked depending upon the part leveling then a lot of wasted motion can occur in unnecessary trips or steps to the flow rack. It's another common waste that is accepted as the "norm" at the GEMBA.
Correction means we do not get it right the first time. It's when we must recreate a product or part because of a quality issue or discrepancy within the process. It can also be in the form of inspection. If a operator doesn't build in Jidoka the first time, re-inspection may need to occur and this is considered a waste in time and manpower. If scrap or rework is high in your company then a daily go and see should be happening to determine current situation.
I hope this has helped to explain the Seven Wastes as described by Taichii Ohno.... if focused upon can change the way you look at your processes therefore adding value to the customer.
Until next time
@tracey_san
Tracey Richardson

Enhancing Standardized Work through understanding the Necessary Conditions in our work (JKK)

The Toyota Production System is based on 2 Pillars which are, Jidoka and Just in Time (JIT). Jidoka is "Building in Quality" at the process and JIT is building what is needed, when is needed in the amount needed. Toyota has always had the philosophy of stopping the line when defects are found, this can be done by anyone who sees a discrepancy with a known Standard (what should be happening within a process). The lines can also be stopped by Machines which are sometimes called "pokeyoke" (fail-safe devices), in order to ensure a defect is not passed on.
Now, more than ever, in this economy it is important to ensure we are looking at our work in the perspective of the customer. If you have a set standard or a known defect rate that is acceptable in "your" company; has that standard been set or determined in the "eye of the customer"? When you think about it, if you are the customer and you have a defect on your vehicle that rate becomes 100% for you. For the company it may be .001% which doesn't seem too big of a deal right? WRONG!! What if you were that person? How does that make you feel in regard to a high quality vehicle?
One way Toyota looks at this perspective is to ensure that Jidoka is within each process on the line, they do this by a process call JKK (Jikotei Kanketsu) literally meaning - Building in Quality with Ownership. What does "Ownership" mean to a person on a process? Ownership is defined in JKK as understand all the "necessary conditions" and "process criteria" so that ZERO defects are passed on. If team members understand these perspectives then they are more apt to understand when the process is NOT to standard and to be able to countermeasure the discrepancy through problem solving or PDCA thinking.
Necessary Conditions can be items like design, equipment parameters, engineering, and manufacturing. Having those aspects understood then Standards can be written and "skills" can be taught in order to ensure the process stops when necessary and defects are not passed on.

For example: If I worked at a Sub shop and my job was to make high quality sub sandwiches for customers based on their favorite selection, then as a sub creator, I must understand my standardized work, necessary conditions and process criteria in order to make the highest quality sub possible. The equipment must be working correctly in order to bake the bread at a certain temperature in a timely manner. (not to over or under cook). Properly labeling all the different kinds of breads to ensure visual controls. A team member must also understand the necessary condition for keeping the meats, cheeses and condiments at the right temperature. The should be laid out in order of need or frequent usage. I need to also understand how thick to slice the cheese, where to put the meat, how much meat is the standard per type of sandwich, how to spread the mayonnaise, and where to cut the sandwich etc. All these items are process criteria and necessary conditions to create a "made to order" sub sandwich which meets the customer needs.

The same criteria needs to be understood in your environment as well, whether your making sub sandwiches, cars, or computers, if there are processes, people, and equipment then standards can be set, along with necessary conditions and process criteria to ensure team member have a "self quality check" giving them the authority to stop the line. I called this "Enhanced Standardized Work" which means taking Standardized work to the next level, understand the key points and reasons to why it was set that way to begin with. Standards are the foundation of the Toyota Production System, understanding their importance and following them is one of the key's to success in implementing Lean. Until Next Time,

@tracey_san
Tracey Richardson

Strategy Deployment - What does it mean for a company?

First off, I would like to apologize for my absence in July, I have been on the road doing great things with companies implementing Lean. I hope to be back on schedule with the blog posts this month and hereafter.

So what does the term Hoshin Kanri mean? Sound familiar to some of you? It is the Japanese term for "Strategy Deployment" or "Policy Management" within companies who have defined their "Line of Sight" or "True North". The words together can be defined as:

A system (or a way of thinking) which intends to create an organization capable of sustained high performace by its leadership and team members to produce continual and repeatable results. A company can achieve this by setting Mid-to-Long Term Management Plans (Annual Plans) that prioritize daily activitites and resources by department or group. The goal is to involve ALL members from the top down who will clarify these targets and value added activity from their own departments/positions. The Hoshin targets can be achieved by continuously turning over the PDCA (Plan-Do-Check-Act) Management Cycle at the MACRO and MICRO levels; checks are performed and follow-ups made during these implementation cycle of the Hoshin. This allows the entire company/organization to have a "line of sight" or work in "one direction" with members at all levels taking initiative solving problems. Some refer to this term as "Catchball". Catchball is a term that describes value added ideas being "thrown back and forth" from management to the team members and team members to the management level which help reach the Hoshin targets.

It's important to remember that a company should first define their values, mission, or goals they want to achieve (which should take into consideration - their customer) in order to understand the strategies involved in developing the Annual Plan. The Hoshin will then be broken down into Divisions, Sections, and Individual Teams. These areas will then determine the value-added activities it takes to successfully meet the goals.

See the visual below of the Hoshin breakdown process between the different levels within a company.

Another key point to remember is that "Problem solving" and "Standardization" are a key components to a Company's ability to see deviation from existing Standards and "thinking" through those discrepancies using the PDCA management cycle in order to get to root cause. The Japanese call this "Kanri Cycle Turnover". Again the micro PDCA activities that solve value added problems towards the company Hoshin goals.

How does your company deploy its strategies for continuous improvement and customer satisfaction? Has your Company Culture evolved to this level or are you still "Managing by Objectives dictated from the top? Til next time,

@tracey_san

Tracey Richardson

Does it really matter if I "Go and See" or not?

The answer is YES!!!

I have to admit during my time as a Group Leader on the production floor at TMMK (Toyota Motor Manufacturing KY) I was guilty, on occassion, of doing certain levels of problem solving from behind my desk or at the computer. I was often in such a hurry to get my A3 written and turned in to my Managers that I would often forget the essential element in the problem solving process. I would usually tell myself-- "I just don't have time", or "I already know what the problem is". Do some of these comments/thoughts sound familiar to you? It's ok you can admit, I just did :0).

It was often a hard lesson to understand the importance of actually going to the GEMBA (japanese term for actual workplace) when your in the middle of those daily reactive moments of "fire-fighting". One of the many lessons the japanese taught me was: "What is more value added, spend time getting to the root cause, or only solving a symptom of the problem"? When we try to solve a problem from our desks we miss the experience of actually "seeing" the problem first hand, and also talking with the team members who know the problem characteristics better than we do. I consider them the "professionals" out there! This action helps build mutual trust and respect with your team members as well as the potential on the job development (OJD) opportunities with team members or leaders learning to understand good traits in effective problem solving or A3 writing process.
One of my favorite quotes from Taiichi Ohno (father of TPS) was: "Of course Data is important, but I place the greatest importance on facts or the truth". This statement is about Genchi Genbutsu (Go and See).... in some of my classes at the Toyota plants many have coined that japanese phrase "Get your boots on!". Meaning, go out to the floor, visit the GEMBA and find the facts; not assumptions and get to root cause. When you demonstrate this disclipline to your team members you are being an effective leader, and efficiently solving problems. Repetition of these actions can create a strong problem solving culture and awareness at the worksite as well as developing good habits in the way we think about our GAPS (Gap= a discrepancy in the Ideal Situation and Current Situation).
So the next time you are faced with solving a problem, and you find yourself falling into the time trap trying to solve it from assumptions or past experiences, just remember to "Get your boots on" and GO and SEE. You will actually find you will spend LESS time on your problem than chasing around symptoms. Until next time,
@tracey_san
Tracey Richardson (Have a good 4th of July weekend!)

Process vs. Results - Which are you focused on as a company?

In Today's environment we are tasked with getting good results as a company...
my questions are: Are you using a good "process" to get there?
One may also ask: What are good results?

Some choose to get their results by luck, some manage by numbers, and most just stay in the daily reactive mode thinking they are going to get "there" one day.

So what defines a "good process" you ask?

A good process, in my opinion, has several essential elements to it. When a company decides to embrace change (shifting from traditional mind-sets); their way of thinking (the way we frame) must change too. I'm going to list a few elements below that I feel could change the way a company thinks/operates. I will say --It's simple its not easy>>> :o)
1. Does your company understand the purpose behind using a good process? (Why the need for change)?
2. Are you thinking in regard to your customer?
3. Do team members within your company have a "line of sight" (previous blog subject) to the company goals and values (Key Performance Indicators-KPI's)?
4. Does your company visualize problems for all team members to see? (not hide them).
5. Does your company have work/process standards in place to understand when there is a discrepancy from the current situation?
6. Does your company use a good problem solving process (PDCA) to identify, investigate, and solve problems?
7. Does your company use a good problem solving process (PDCA) to develop/challenge its team members through on the job development (OJD)?

I've listed only a few of the elements above(in my opinion) to implement a good process that will get you "continual and repeatable" results as a company, as well as a workforce that is encouraged to "think".
Some companies and their leadership will continue to "manage by numbers" turning their heads to their responsibility as coaches, and continue to give orders "because I say so", instead of offering development and wisdom as leaders should be.
For the short-term the practice of getting results by luck or numbers may keep them out of trouble with their bosses, but this is not the proven method for long-term growth, sustainability, or building mutual trust and respect with your team members. Just look at certain industries today that have managed this way. Do your results meet customer needs? Where do you wanna be as a company? Until next time
@tracey_san
Tracey Richardson

What is all the fuss about 5S anyway--Is it really important?

If an individual took a checklist with them and investigated all the different "versions" of the 5S's out there we would have about 10 or 20 different S's. In my experience I've seen different words used in the place of the "original" 4S approach (american culture added the 5th S by the way) established years ago in Japan. The "version" I like to use comes from the original TPS Handbook created by Toyota Motor Corporation (TMC).

I think if a company understands the intent behind 5S then the words chosen to represent the meaning are merely a guide to explain the process or tool. What I find is that companies will implement 5S but very few people really understand WHAT it is and WHY its an important step in Lean Implementation and TPS. (See previous blog posts explaining the WHAT and WHY.)

So what is 5S and Standardization have to do with one another?

5S supports Toyota concept of "abnormality management" by applying visual techniques (visualization) and controls that enable a team member to immediately recognize the standard and any deviation from it. We can also call this Problem Identification, which is the first step in Problem Solving. The 5S condition on the shop floor or in the office can effect our ability to manage those 4 Key Performance Indicators (KPI's) -- Quality, Safety, Productivity, and Cost.

Here is a helpful guide below to determine the different levels of knowledge when it comes to 5S "thinking".

Where is your understanding as a company or an individual in regard to 5S?
Take a look at this: (OJD=On the Job Development)

If a company is really trying to change their culture in regard to Lean and using TPS tools then 5S can be a way to develop team members as shown above.

So what are those S's.....let's take a look below:

Remember 5S is a "visualization and standardization" tool that used to implement Lean (TPS). It can also be used as a development tool for leadership as well as team members across all levels of the company. So the next time someone asks about 5S just know its more than the "flavor of the month".
Til next time
@tracey_san
Tracey Richardson