Lean Thinking - Respect For People

The foundation for Lean Transformation

Beginning the Journey and navigating this unknown (but common sense?) path requires a change in how Leaders and Managers relate with the employees.  This will be more than having a banner that states "Employees Are Our Most Important Assets!" in a 72 pt font or some kind of Employee Involvement committee that meets once a quarter whether they need to or not.  This is going to require you putting on your shoes and going to the place where the work happens.  And this should not be a one-time event, schedule the visits if you need to between your triple-booked meetings.

House of Lean with Respect for People as foundation

If this is your first time for your employees to see you on the floor, there may some staring and pointing, or some may even introduce themselves to you.  But I'm sure in this day of enlightened management techniques, you will not experience anything like this... right.  Employees will be open and honest if they are familiar with you and have some type of positive rapport.

You can also attend some of the team's meetings, listen to the comments they are making.  When was the last time you shared the company's strategy with them?  Do they make plans that align their Goals & Objectives with the direction of the company?  Do they understand how this Journey helps to improve the company's stability and long-term success?  Have you ever met anyone on the Board?  This Respect and Communication moves up and down the Leadership Chain.  Communication is not just Leadership making commands and the employees executing their wishes.

When we are developing and using our listening skills, we need to capture those comments that illustrate potential road-blocks to the implementation of the strategy.  These comments will need to be corroborated with your staff and seen in action.  The employees are looking for help when they need it, but we don't instantly implement suggestions just because they come from "the floor".  You will need to validate the problem's existence with measures.

We're not trying to make this a 12 month long six sigma project, sometimes the root causes are standing there and taunting us to make the first move.  Involve the Smart People in the measures, root cause identification and determining the solution.  The entire team owns the problem and the solution, this ownership will help facilitate the long-term solution that is followed and maintained.  Whatever the solution that is implemented, make certain that it is reflected in the standard work instructions.

When you have a measurable difference in the two methods, it's time celebrate success with the team.  Order some pizzas, make some certificates of appreciation, get them some gift cards, maybe it's time for a promotion, or some sort of positive reinforcement of the message that we are together on the Journey.  One instance of problem-solving does not make someone Lean, nor does it solve all the problems so someone "gets a belt".

If the problem is not validated, talk with the person who thinks it is there.  You may have missed something important, it may not align to the strategy, or there may be a deeper conversation to be had.  It is entirely possible that the Good Idea Fairy has been in the area having her way with unsuspecting employees.  Ideas have to be connected to a measured and validated problem statement.  If the decision is to not do anything about the problem yet, let the employees know why and when it may be addressed.

Improving is difficult enough, but having the team on board can make the Journey smoother.  Open and Honest communication can help make it happen.

Merry Christmas 2012!

Today is a good day to be with family and friends, and see if you can follow the Standard Work provided with many of the toys you may be constructing today.  The good one will have pictures to show what "right" looks like.  These are good examples to use around the office while you are creating or updating your own SOPs or Desk Guides.

Merry Christmas to all my friends and followers!  I hear that the Time of Resolutions is just around the corner!

When Is Enough, Enough?

A Long Time Ago In A Galaxy Far, Far Away...   

I was teaching the Statistical Process Control & Capability module during a Lean six sigma Green Belt class and one of the students asked, and I'm going to paraphrase, "When is enough, enough?"  I think this would be a normal question to ask while learning how to Make Value Flow.  The question came from one of my Quality friends, and I'm sure he was thinking about all the different processes he supported that needed improvement and certainly not when he could put his feet in the air and his "you-know-what" in the chair.

If you have been measuring your performance, then you should have some amount of data collected around the problem you are experiencing.  If you are having quality problems, you may have Defects Per Unit (DPU), or Defects Per Million Opportunities (DPMO).  If you are having delivery problems, you may have Cycle Time or Number of Days Early/Late.  If you are having cost problems, you may have Cost Per Unit or Weekly Printing Costs.  Either way, you need some data that represents your process.

We can see the performance is in control and the stable, but is the process meeting the customer's needs?  This is always the right question!

When we use SPC we are looking for  indicators that signify when to start asking questions about the process.  There are four that are the easiest to use and remember; 1) Any points outside of the control limits, 2) Six points consecutively going up or down, 3) Nine point consecutively above or below the center, and 4) 14 points consecutively going up and down.  Having a process that performs within these four parameters means that our process is in control and stable, which indicates the flow is predictable.

Here is your SPC warning!  Do not let any of you Quality Engineers catch you putting specification lines on your SPC chart.

What it does not tell us is are we meeting customer expectations.  This is where we take our Voice of the Customer specifications and lay them on top of a histogram of the data.  From here we can see our performance compared to customer specs of no more than 21 days (USL, LSL).

Current State

And as we can see from the fine specimen above, when our cycle times are 22-25 days we are not meeting customer expectations.  Our process is in control, but not performing to the wants and desires of the customer.  In fact it may be possible that our favorite customer is looking for a new supplier of their information needs as we speak and I think that immediate action is required.

At this point you should be constructing a charter, assigning one of your belts to lead the project, and kick-off the team.  Work your best as a Project Sponsor, Smart Person or Supplier/Customer and document the results in an A3.  When you have enough data with the new process you can see how the center and spread fit within the specifications.

If you have identified the root causes and adequately implemented a new process that has improved flow, then you are done with that process for now.  The biggest indicator is the edge of the distribution is some amount away from the specification.  For you math nerds, below is the formula and you want to get as close to 1.5 as you can.

Improved Process #1

Based on our results we can see that are delivering everything on time, and if we finish early we can hold the deliverable until the customer is ready.  Be wary of producing too much too fast.  That would make our work-in-process increase, which means the window between "doing work" and "getting paid" increases and this is detrimental to cash flow.

At the end of the day we want our products to flow without stopping though our value-added operations to meet customer demand.  Deliver too late and the customer must wait (Wait Time), but if we deliver too early the customer has to over-handle (Excess Processing) the product until they are ready to use it and this is "Inventory" they have to hold until they are paid.  If you have paid any attention over the last 5 years, this over-capitalization is one of the causes of the downfall of the American automobile industry.  Leadership is the decision-maker, but the following histogram represents one possible best fit.

Improved Process #2

Improving performance is not something that will automatically happen, learning curves are not absolute.  Market forces fluctuate and your ability to adjust with them could be one of your long-term indicators of success.

How do you use your data for improving flow?

Designing the Perfect Process

In all the work places we have been, do you remember ever asking how someone came up with this insane method to respond to a customer order?  Taking the order is easy, we receive an email from our website catalog system.  But everything else we do after that resembles a group of 5 year old Americans playing futbol (ok fine, soccer).

We would like to think the process was designed using the smartest people, using the best tools, and the most responsive and fair management techniques taught in the best MBA schools.  No such luck my friend.  Your current process was haphazardly put together using years of bad results from battling against lawyers, the least amount of communication possible, and it's certainly not documented or repeatable.  The last thing we also want is someone able to measure the process only to beat us up with the charts.

Does any of this sound familiar?

When do we start creating the new process?  The best situation would be during New Product Development or when you start to go after new customers.  Sometimes your current process does not meet the customer needs and small step improvement is not enough.

Let's start by defining a few characteristics of the perfect process and what it looks like:

1)  It has no review cycles, quality comes from the process
2)  There is no guessing
3)  There is no hunting and gathering
4)  The time from order to fulfillment is as short as possible
5)  The customer receives the order defect free and exactly when they want it

With this in mind, let's start....

You will need to collect any regulations that may impact your process or product, voice of the customer using surveys or direct interviews, and any business concerns that may exist.  We will put this on a House of Quality or Quality Function Deployment (QFD) (same thing... mostly, just don't say that to one of the Six Sigma guys).  Rate, prioritize, and score these to help determine the level of focus to be applied during the actual design of the flow.

Benchmark other organizations or companies dealing with the same type of product.  Be open and honest, those organizations getting good results will be very proud of their process and will happily show you their stuff.  There may be more information published on the internet, in trade magazines, or state/federal government survey data.

More time is used defining requirements so when it is time to document the new flow it almost creates itself.  Ok it's not that easy, you will need the smart people to help lay out the steps.  Lock everyone in a room, tape a long piece of butcher paper on the wall, break out the sharpies and sticky notes, and tell everyone to put their shoes on 'cause they're going to go do some work.

Start with the first signaling step and have the rest of the team fill out the remaining steps of the flow.  Keep a large copy of the QFD taped to the wall next to the flow so they don't forget about the customer's and other process stakeholder's needs.  Add the inputs and outputs to each step step to help the team focus on the thing going through the system.  Complete your Value Analysis and look for any of the 8-Wastes that can be eliminated before the process goes live.

When you have this completed and the team reaches consensus on the flow, put it in your SOP or Deskguide format.  Create the training to deploy the new process to the other team members who have not seen it and any new team members that come on board later.  Determine the measure points for Quality, Cost, Delivery, and any other Customer measure to finish the process.

If you have some sort of process automation, make sure you have separated the steps in the process to show which are performed by people and those performed by the computers.  Don't mix these as computers can't think critically and make decisions and people should not be creating information that no one will see.

Does the perfect process really exist?  Probably not, but can get very close.  All processes need to have learning steps so when quality or cycle time issues are identified they can be quickly eliminated from the process.  Update the Deskguide and document in an A3.

Everyone raise your right hand and repeat after me.  Go ahead, get that hand in the air.

1)  I will not accept poor quality from my external or internal suppliers.
2)  I will not pass on poor quality to my external or internal customers.

OK, put you hand down and share cool things your have seen in your processes!