About Walter McIntyre

I live in Buford, GA, with my wife. Please check out my website, leanmeanprocessimprovemnt.com. I am the author of "Lean and Mean Process Improvement".

Waste Reduction and 5-S

Posted on May 21, 2012 by Walter McIntyre

Waste can take many forms. There is waste of time, material, human resources, etc., all of which result in a waste of money for the business and its customers. Time and material is easy to understand, even if not always easy to see. The waste of human resources is more insidious.

Everything is interconnected and waste is usually found to be both the result of other waste and the cause of other waste. The ability to see both the big picture and the little picture at the same time is important. Fixing waste in one area that creates waste somewhere else is called sub-optimization and is counterproductive. Solid leadership and a shared vision will save the day in any waste reduction initiative.

There is a relationship between the eight wastes we have all heard about and the 5-S tool we have also heard about. In this brief post, I will try to explain how 5-S can address all seven wastes. Let’s start with a description of the seven wastes.

Seven Wastes:

Transport: Un-necessary movement of material for production.
Inventory: Raw material, work in progress, and finished product not being processed.
Motion: Un-necessary motion of people or equipment.
Waiting: Raw material, work in progress, and finished product not being processed waiting for the next process step.
Over Production: Production ahead of demand.
Over Processing: Poor process, tool or product design that creates activity that is not productive.
Defects: Inspecting for or correcting defects anywhere in the process.
Under Utilization of Human Resources: Under-trained or under-utilized employees

5-S is not just a tool to makes things look better. This tool will also make things work better and produce less waste. Like all tools it must be calibrated to the situation. If you understand the wastes being produced in your processes or business, 5-S can be made to target these wastes and wipe them out. So what are the 5-S’s?

5-S

Sort: Necessary vs. un-necessary material, data, equipment, etc. Prevention of cleanliness and mess producing problems. Addresses wastes 2, 5, 7
Set In Order: Place for everything and everything in its place. Addresses wastes 1,3, 4
Shine: Clean work space. Addresses wastes 2, 4, 6
Standardize: Rules to standardize the sort, set in order, and shine efforts across the work space. Housekeeping, inspections, and workplace arrangement are shared and used across the work place. Addresses wastes 1,2,3,4,5,6,7,8
Sustain: Culturalize the standards so as to eliminate the root causes of problems in the other 5-S categories. Addresses wastes 1,2,3,4,5,6,7,8

In order to use the 5-S tool correctly, the improvement team will calibrate it to the processes and areas where it is being applied. Applying 5-S to an office setting will have a completely different look and feel than applying the tool to a manufacturing floor. As the team looks for waste they also adjust the 5-S tool to directly address specific aspects of the work space.

As waste is reduced and the work space becomes more standardized, hidden waste producing activities become more visible. This is why the 5-S tool is considered cyclic. The new wastes are addressed as they are discovered by the initial 5-S iteration. At the same time, the team will document larger issues that will require a more focused Six Sigma team effort later.

The result is reduced cycle time, reduced inventory dollars, increased productivity, and increased utilization of resources. The business will see increase profit directly to the bottom line as a result of satisfied customers. This is because the customer’s perceived value of the product or service increases and the inherent value born by the producer decreases. When you plug these value changes into the profit formula below, good things happen.

Profit = Perceived value (customer) – Inherent value (cost to deliver).

See my book, “Lean and Mean Process Improvement”, for more information.

Cycle Time and Utilization

Posted on May 16, 2012 by Walter McIntyre

In order to improve my on-time delivery of service, do I add resources to my process, or do I try to improve my process cycle time? The first consideration is that increasing resources increases your cost of operation. Improving cycle time does not. Another way to look at this is to compare your process cycle time with percent utilization of resources.

There is a relationship between variability in cycle time and percent utilization of resources. The source of this variation can be found in quality, rework, employee issues, etc. When variation is high, the percent utilization of resources reflects that variability and can impact on-time delivery, cost, and knowing how to allocate capacity (hiring, capital equipment, etc.).

An example of how this relationship works is displayed in the graph below. As the percent utilization of your capacity increases, task cycle time also increases. The increase in cycle time is relatively flat at first, but eventually, the curve becomes steep.

The two curves in the graph above represent a 3 sigma level process (high variation) and a 5 sigma level process (low variation). If a customer’s time to delivery requires process cycle time to be less than 4000 seconds, the 3 sigma curve fails to meet that criterion at about 65% of resource utilization. The 5 sigma curve, on the other hand stays capable of meeting the criterion all the way up to 100% of resource utilization.

A business with a high variability in cycle time will have to add capability much sooner (lower utilization). This is not good for bottom line costs. This clearly demonstrates why lowering the standard deviation in cycle time of the process becomes important.

An additional take away from this chart is that as cycle time or utilization increases, so does the probability of failing to meet on-time delivery targets. Again, the lower standard deviation (higher sigma level) process has the lowest probability of failing to meet on-time delivery requirements at any utilization percentage.

What this means is that is better to focus first on cycle time in order to improve on-time delivery, as opposed to simply adding resources to a bad process. This is where Six Sigma comes in. A six Sigma process improvement team will address the root causes of variation in the process; thereby improving the utilization of existing resources. This is akin to giving your car a tune up to improve its fuel economy.

Lean Marketing

Posted on May 11, 2012 by Walter McIntyre

Lean principles apply to any process based operation. I cannot think of any process that does not have non-value added components in it that create the opportunity for waste production. In fact, by definition, a non-value added component in a process is waste.

Let’s take marketing for example and do something called lean marketing. Please remember that in a post of this size, I am leaving a lot to the imagination. Some businesses have marketing programs that start with the product/service and move outward to the customer. They call this customer focused because they do eventually think about the customer. This is not all bad because the customer is a part of the equation. The problem with this approach is that it is self-limiting. In effect, it allows the product/service to define the target customers and, as a result, becomes growth limited by this boundary. This is the waste of missed opportunity

To balance the marketing equation, the business needs to also think in the opposite direction. That is, starting with potential customers and moving to the product/service. In this approach the potential customers defines the product/service and, as a result, is not limited by an artificial customer segment boundary.

In more detailed terms, in the product first scenario, the business defines the product/service, the price, and how it will be delivered. Once these definitions are made, the business promotes the product or service to a targeted customer segment. As you can see, the product/service is defining the targeted customer. In a lean marketing program this is phase two, not phase one.

In the customer first scenario, the business connects with potential customers across multiple segments and establishes what the customer’s value (are willing to pay for), customer cost (price they are willing to pay), and how they expect the product/service to be delivered. Here the potential customer is defining the product. In lean marketing, we would now go the product/service side of the equation and build out to the customer.

Additionally, every business needs to realize that with the internet and social media, potential customers can easily compare products and services across multiple suppliers. This means that they can easily find the product or service that best fits their wants/needs. By using the product/service to define the customer, the business self-eliminates from non-targeted potential customers.

If instead, the business first allows potential customers to define the product/service (phase one), the product/service can be tailored to fit different customer segments (phase two). This in turn allows the marketing program to be tailored to target multiple customer segments. This tailoring takes advantage of the internet and social media by addressing the specific needs of different customer segments.

I look at this as an application of Deming’s “Plan-Do-Check-Adjust” cycle. Define the potential customer’s needs, apply what you learned to the product/service, evaluate market effectiveness, and use the evaluation to find improvement ideas. This process is like a wheel that continually turns over and over again throughout a product/service life cycle. The result is better performance and a longer product/service life cycle by way of waste reduction.

As a final note, this same approach can be applied to a development process. The PDCA cycle, focusing on the customer first, will help to prevent misunderstandings (waste) and missed targets (waste) because the customer becomes a key part of the development process. The more times the PDCA wheel is turned in a development project, the more input the customer will have, the less likely the development team will miss the target. The target in this case is the right product/service being delivered to the customer at the targeted project cost and profit margin.

Those We Love

Posted on May 3, 2012 by Walter McIntyre

Moving through life is a process. We grow physically (sometimes not so good a thing) and mentally (always a good thing). Relationships are cultivated for better or worse and we simply move from birth to death.

All the while, what you are really doing is writing the story of your life. What kind of story will it be? What is in the wake of your life?

These are important things to consider everyday, but there is something more. We must be aware that things change. Sometimes permanently. One of these permanent changes is the loss of loved ones. This is what I want to address in the next several words.

I was fortunate in that during the last weeks of my father’s life I was able to spend many quality hours with him talking about things important to us. We left nothing unsaid. I take great comfort in this, even in the emptiness I sometimes feel since he passed.

Here is the point, don’t be so busy with writing your story that you forget loved ones. Since my father passed, there is nothing more I can give to him and there is nothing more he can give to me. The same will be true for you. So, embrace your loved ones while you can. Put aside the differences and make sure that they are written into your story.

Value Stream Analysis Case Study

Posted on April 29, 2012 by Walter McIntyre

Value stream analysis is an examination of the sequence of activities required to design, produce and deliver a product or service. It involves an analysis of way pieces of the value stream interact with each other. Some of these pieces are:

– The people who perform the tasks and their knowledge and skills

– Tools and technology used to perform and support the value stream tasks

– Physical facilities and environment in which the value stream resides

– Organization and culture of the enterprises which owns the value stream

– Values and beliefs that dictate the corporate culture and behaviors of the owners of the value stream

– Communications channels and the way in which information is disseminated

A current project that I have been working on involves the development of firmware for a communication interface device. We were moving too slowly and costs were piling up due to delays. Since there were three companies involved in the project (owner, firmware development, server/deployment development) the assumption was that finding improvements would be difficult. That is where I came in.

There are three ways for the businesses involved to shorten the value stream and get to market quicker.

Hire or move additional programmers into the development team.
Change the management of the development stream.
Improve the processes in the value stream.

In this case, adding resources is the easiest to do, the most costly, and least effective means of getting the project done faster. Changing the management structure of the project will only work if the new management would change the development process. The last option, process improvement, is the least costly, maybe the most difficult to implement, but also the most effective solution to the time line and cost problems.

As it turned out, two of the possible changes were made. There was a change in management of the project and the new leadership set out to improve the development process. The chart below shows two value streams.

The top map describes how the development project worked at the time of the changes. The bottom map describes the new process.

In the former process, there were two review steps to quality check the work done by Tech 1. The wait time between steps was not much of a problem, but the second review step created a huge hidden factory. There are 60 iterations of this process flow required to complete the 60 different communications functions. Each of the iterations could take as much as 215 hours of time to complete. That would be 537 work days needed to get to completion. If additional resources were to be brought in, the time lie would shorten, but the overall cost of the project would not change.

The new management team elected to make the following changes:

Reassign some of the tasks from the firmware developer to the device owner’s engineering team. Specifically the analysis steps. This is really nothing more that researching each of the functions ahead of time instead of just prior to the development activities. It also lowered the cost of the project to the device owner through the use of their inside engineers.
Combine Tech 1’s coding with the review step involving Tech 3. This moved Tech 3 from a part time asset to a full time asset on the project and had them working simultaneously instead of sequentially.
Testing the new code would be done on a local server instead of the production server. This eliminated Tech 4 from the process until the developed code was finished and tested locally.

The result was the empowerment of Techs 1 and 3 to write and review code without the involvement of the deployment team. Coding errors and other unforeseen issues were caught earlier. This made these problems quicker, easier and cheaper to fix.

Another result was the device owner getting out front of the development with research on each of the 60 functions weeks before the project reached those milestones. This effectively moved 8 hours of cost and time from each of the 60 iterations.

Overall, the new process uses 105 hours for each of the 60 functions. The new time line became 262 work days. Between the use of internal engineers and the reduction in work hours, the cost savings was $800,442 dollars.

Old New

Work Days 537 262

Cost $1,565,892 $765,450

I will not say that everyone is happy. Delays and finger pointing have damaged the relationships between the owners and the developers. This will not be changed easily. On the other hand, getting the device into a commercially viable state will make everyone happy. The sooner the better in this case.

One major take away from this exercise is that even a simple application of value stream mapping can make a difference. Never assume that there is no opportunity for improvement.

Value Stream Analysis

Posted on April 27, 2012 by Walter McIntyre

I have been working on a value stream analysis case study. I believe that you will find it useful and thought provoking. We used the VSA to define weaknesses in a process’s work flow, made changes, and documented the improvement that resulted. Cycle time was the metric we were pursuing.

Unfortunately, due to a death in the family, I will not get it finished this week. I apologize, but family does come first. We’ll take more next week.

Words You Never Use In Sales

Posted on April 18, 2012 by Walter McIntyre

Words have power. And while many words have the power to help you make the sale, some words have the power to sabotage it. If you want to increase your sales, here are nine words you should avoid using with prospects and customers.

1. “No”
People hate to hear no. They love to hear yes. So whenever you’re tempted to say no to someone, stop and think how you might be able to yes to their request. This is not to say you should give away the store. Rather, look for ways to make things happen instead of automatically justifying why you can’t. If you cannot find a way to accommodate their request, instead of saying “no”, tell them what you can do.

2. “Can’t”
Speaking of “can’t,” this is another word that can anger and frustrate prospects and customers. Instead of dwelling on what you can’t do, focus on what you can do. Provide options and alternatives. Remember, you’re there to assist and serve your customers.

3. “Policy”
Here’s a news flash: I don’t care what your policy is. I only care about what I want and need. If you can deliver that, you’ve got me as a customer. If you quote “policy” as the reason you “can’t” do something, you’ve lost me. Probably forever.

4. “Don’t”
The human brain can only process a negative by thinking of the positive. Which means, when you tell your prospect “Don’t judge a product by price alone,” what they really hear (on a sub-conscious level) is “Judge a product by price alone.” When you say “Don’t worry,” they hear “Worry.” Tell your prospect or customer what you want them to do, not what you don’t want them to do.

5. “But”
The word “but” negates whatever came before it. (“You did a good job, but…”) Replace it with either a simple pause or the word “and.”

6. “Why”
Questions that start with “why” sound accusatory and judgmental. (“Why did you do that?”, “Why do you think that?”, “Why is that important to you?”) As a result, they cause prospects and customers to raise their defenses. Instead, rephrase “why” questions into “what” or “how” questions. (“What caused you to do that?”, “How did you come to think that?”, “What’s the reason that’s important to you?”)

7. “Honestly”
Whenever you use the word “honestly,” you imply that some or all of the other things you’ve said have not been honest. Strike the word from your vocabulary. The same goes for words like “truthfully” and “frankly.”

8. Any Term of Endearment
While words like “buddy,” “pal,” “baby” and “sweetheart” are fine with your close friends, they’re not okay to use with prospects or customer. You should always be polite, courteous and respectful. The best thing you can call a customer is their name.

9. Profanity
I shouldn’t even have to mention this. If you’re looking for a sure-fire way to offend a current or potential customer, this is it. Never chance it. You’re not a stand-up comic in a nightclub. You’re a sales professional. Speak accordingly. Even if your prospect or customer uses profanity, you do not.

Finding Sources of Variation

Posted on April 11, 2012 by Walter McIntyre

Typically, the most suspect processes or process steps for introducing variation are manual or judgment oriented in nature. For example, if an individual applies personal judgment within a process you would expect to see bias or higher variation in the process output. Automated processes will typically have more consistent performance and lower variation.

One of the best ways to find these manual or judgment steps in a process is through the use of a process map. As a process is mapped, decision points are represented as diamonds. This becomes the first place to look for variation.

When mapping a process, information from both the process owners and the Six Sigma team’s observations are used. There are situations where the process as described by the process owners is really from the “as we think it is” or “as it should be” world. The Six Sigma team that falls into this trap is doomed. In these cases, the process owners may know the standardized process, but chose to not follow it.

On a project I worked a few years back, there was too much variation in the concentration of petcoke being blended with the coal burned in a business’s boilers. The result was either too much petcoke, resulting in a violation of environmental parameters, or too little petcoke which increased the cost of operation.

The fuel feed system was comprised of 2 conveyer belts that fed a third conveyer belt. One of the feeder belts fed coal and the other fed petcoke. The third belt, called the silo belt, fed the boilers. The concentration of petcoke loaded to the boilers was controlled by the belt speed of each of the first two belts.

Additionally, the silo feed belt was designed to start empty and, as a result, was the last belt to be shut off so that it would be empty when stopped. The two feed belts were designed to be started empty or full.

The process of starting up the fuel feed system was to start the silo feed belt first, the coal feed belt second and the petcoke feed belt last. All belts were to be empty when started. The shutdown process required that the petcoke belt be shut down first, after it was empty. The Coal feed belt was to be shut down second, when it was empty. The silo feed belt was to shut down last when it was empty.

The first step in the team’s analysis of the variation issues was to compare each shift’s start-up and shutdown processes. The Six Sigma Team did not take for granted that all shifts were compliant with the standardized start-up and shutdown processes, since the computer systems allowed them to change the order of startup and shut down.

What we found was that one of the four shifts shut down the coal and petcoke belts full, and then shut down the silo feed belt when empty. When starting the system up again, this shift would start the silo feed belt first and then both the coal and petcoke belts simultaneously. This shift had a low variation in petcoke concentration (within variation). Much lower, in fact, than all the shifts put together (between variation).

Another of the shifts would first shut down the petcoke feed belt full, then the coal belt full, then the silo belt when empty. On start-up they would start the silo feed belt first, then coal feed belt, then the petcoke feed. This group had the highest within variation in petcoke concentration, but still lower than the between variation of all the shifts put together.

The other two shifts followed the standardized process of start-up and shutdown. Their within variation in petcoke concentration was higher than the first shift, but lower than the second shift.

What the team had found, so far, was that two of the four shifts did not follow the standardized process of operation. Even so, the variation within each shift was within tolerance. The team then matched up emissions logs with the petcoke feed logs over a three week period. What they found was that the interaction of the different shifts created significant swings in petcoke concentration. This “between” variation turned out to be the root cause of the variation problem.

The solution was to get all sifts to follow the same process. A team meeting with representatives of each shift resulted in an agreement to follow the first shift’s start-up and shutdown processes. This became the standardized process for the plant’s fuel feed.

The Six Sigma team monitored the fuel feed process for four weeks after the agreement to measure the results. They found all shifts in compliance with the standardized process and a very low variation in petcoke concentration. The low variation allowed the plant Operations group to incrementally increase the petcoke concentration and thereby reduce the plant’s operating cost.

One conclusion that the Six Sigma team made was that compliance with standardized processes is higher when the process owners were part of the dialog that creates the standardization. Processes are processes, but people are people. Processes are developed to serve the process owners (people) not the other way around.

Another conclusion was that communication between groups needed to be improved. The different groups need to understand why standardization is necessary and they need to know how to recover from unforeseen process upsets. In this case, what is the standardized process for start-up and shutdown when system maintenance required a different shutdown condition than normal? This latter situation required an expansion of the process management plan to include all pre start-up and per shutdown scenarios.

Have an Opinion?

Posted on April 6, 2012 by Walter McIntyre

Everyone has something to say. Diversity of opinion and perspective is a good thing. In the age of the internet, there is no excuse for not having a venue to express yourself. Leanmeanprocessimprovement.com is a place to post your ideas and perspectives on Six Sigma, Lean, Business Management, and Personal Development.

If you want to contribute comments to existing posts on this website, please register as a user.

If you want to author posts on this website, register as a user and contact me at walt.m@att.net, to get access to author status. You will get full credit for your posts, networking opportunities, and my appreciation.

Lean and Mean Process Improvement CD and Audio Book

Posted on April 5, 2012 by Walter McIntyre

Lean and Mean Process Improvement is now available on CD as a PDF along with an assortment of Six Sigma Tools. Email me at walt.m@att.net for details on how to purchase this CD.

Work started last week on converting Lean and Mean Process Improvement to an audio book. This work is in progress. I will post notification about availability as soon as it is ready. If you email me at walt.m@att.net, I will notify you when it is ready for distribution.

Walter McIntyre Lean Six Sigma