While we all understand how powerful value stream mapping can be, selecting a value stream to begin with can sometimes be a daunting and task.  Along with exhausting brainstorming sessions, the effects of product flow can be quite deadly if the "spray and pray" approach is used.  Here is a three-step approach for selecting a value stream to map that will put you in a much better position to establish a flow down the line.  

  A few months back I received a phone call from an old friend.  After we had finished catching up for a bit he began describing to me how he had his employees calculate the yield of his pizza's.  each day the employees would mark how much came out and how much was put in.  The employee would then divide the out number by the in number giving him the yield percentage.  Sound familiar?  The method that was being used to calculate yield is known as traditional yield calculation.  Out of curiosity I asked him, "what is your yield percentage?"  He then shared with me that his yield for each day was always right about 96%.  So what was the issue?  96% production rate is not the best, but it's not the worst either.  That's when he mentioned that things didn't seem to add up.  

  Ever since the dawn of time man seeks to make woman happy and keep cave in 5S condition.  Bows nice and tidy, dirt floor swept and sanitary with a place in the tunnel to scratch each internal audit. The benefits are almost immediate and the system seems to have a way of energizing the other "tribes."  But even with success that dates back to prehistoric times why is it that 5S seems to have become the "beginners" project?

  Endless hours of training go by every week on track fields around the world.  The teammates are focused on only one thing getting better for competition; Call it passion, maybe desire or even just the want to claim a gold medal most athletes understand that with every event they must continuously improve to become better.  

  Ever had an annoying fly buzzing around you?  You swat and swipe and you just can't get it away from you until you grab the right tool.  I certainly have.  Much like a fly swatter is the right tool for getting that pesky fly the swot analysis is often times the right tool to help you identify four very important elements of business, projects or venture objectives.

  Almost every organization in the world knows by now that the 5S system is an efficient, low maintenance and high impact means of driving continuous improvement.  The system itself can be used in offices, shop floors and software systems.  So why is it that many who have tried this powerful tool only yield small returns or feel as though something is hiding?

  Whether you celebrate Thanksgiving or you're just getting ready for a hearty dinner, planning for the big meal can be quite the task especially if you have lots of guests to provide for.  Hours of cooking, ordering and booking travel plans.  It's no wonder turkey makes you tired.  Allow us if you will to share 5 principles that will keep you lean this thanksgiving.

​  Many companies wonder, where should I start with my continuous improvement journey?  And while the answer varies for everyone, in this post from our soon to be released Just in Time Course we will answer a key question that all organizations must consider, what is the foundation for continuously improving?

  All year long we strive for improvements.  Squeezing waste from every corner of organizations,  Posting new videos, or trying to eliminate that pesky root cause.  Whatever it is you do, labor day is for each and everyone of us.  Here are some important things to keep in mind on your day off:

  From Each and Everyone of Us at Lean Strategies International LLC, we wish you a happy, safe and prosperous fourth of July.  May we ever live with gratitude of the great freedoms we have.  ​Celebrate the Fourth of July With Lean Strategies International LLC. with this beautiful medley of patriotic songs.

  So you have planned out some improvement for an existing process, product or service but you want to ensure that it is a success.  One of the best ways to make sure improvement goals are a success is to plan for possible failures.  FMEA or failure mode effects analysis will do just that for you.  FMEA is a method of identifying possible failures in a process.  As the name implies "failure modes" hints that it will help us to understand the possibilities of failure.  Sound like a valuable activity?  It certainly is,  so how is it performed?
  Before we get started with an overview of FMEA you need to know that there are a few different FMEA methods.  One is for process oriented analysis.  You may have heard it referred to as PFMEA.  The other type is used in the design or redesign of a process, product or service this type of FMEA is referred to as DFMEA.  Today we will not focus on either one specifically.  Remember you can find templates here.
How to Perform FMEA

1. As with almost any other project or initiative you need to define the details of the project.  This would include such elements as the objective of the activity, estimated timeline, history, resources you might need and why exactly you are undertaking the initiative.  A project charter can be used to lay out and define the the initiative.
2. Now that you have defined your project and assembled together a cross-functional team of SME's we can begin gathering measurements and understanding the current state of the process.  While there are a few different methods of understanding the current state or as is process or product the absolute best method is usually to map the process out.  However if there is no process in place using a quality function deployment approach may be helpful.  Tools like the house of quality can help you to ensure you are aligning your abilities with the needs of the customer.  
3. After the team has gained a good understanding of what is needed or what exactly is going on you will be ready to begin identifying potential modes of failure for each step in the process.  The current state map should have identified initial issues for you to focus on.  These potential failures should be listed next to the appropriate process step in your template. Once you have your potential failures link them up with how they will impact the customer. Try to keep in mind answering the question "what goes wrong when the failure occurs and how severe is it?"  This answer combined with the impact on customer requirements will give you your first score which is the severity rating of the potential failure.
4. Having now listed potential modes of failure and established an agreed upon severity score the team can now turn its focus to the actual causes or root causes of the failures.  
5. The next step in our FMEA method is to identify and rate the frequency of the potential failures occurrence.  This is an important part of the fmea process because it helps us to understand where we will focus our corrective activities.  The risk priority number that fmea establishes is based on severity, frequency and the level of detection or how well we can detect and prevent failures prior to reaching the next customer (internal or external).  One very effective way of seeing level of occurrence or frequency is through the use of check sheets and pareto analysis.
6. After a frequency score has been documented we need to document the current controls that are in place.   These controls are placed in the tab labeled "current controls."  These could be any realm of activities that the department or organization currently uses to prevent failure from happening or risk from escalating.  One thing to note is that some process steps may not have any control in place, these boxes remain blank.
7. Once the current methods of control are documented we will again attach a score to the control methods.  Although criteria varies from organization to organization ultimately you will be scoring detection based on how well the existing controls either prevent the failure from occurring or detect it.  
8. The next step is to calculate your RPN or risk priority number.  If you are using a template (hopefully) the number should populate automatically, but if you are not you will need to multiply your severity score by your occurrence or frequency score and by your detection score (S x O x D = RPN).
9. Finally we are ready to recommend actions that will reduce the possible failures severity, occurrence and improve your ability to detect or prevent the possible failure.  These recommendations should have an owner attached to the activity and should provide status as to what is happening with the recommendation.
10. Once the team agrees on the action plan move forward by implementing the agreed upon activities.
11. Last but not least calculate the results of your action plan with the RPN.  One best practice is to continue to set improvement goals targeting improvements or reductions in the potential failures.

  Keep in mind that fmea is meant to identify and completely understand a product or processes potential failure modes along with how they impact the customer.   FMEA will also establish a level of risk associated with the identified failure modes, effects and causes and will assist in prioritizing solutions and narrowing down a seemingly long list of actions.  But like any other improvement project you will need a team of experienced and skilled professionals to properly gather "failure modes" and "analyse the effects."    

  In the first three phases of the REDUCE methodology, required data is established, the value stream is engaged for a deeper understanding and internal and external activities are differentiated or separated as defined in the SMED system.  The first two phases are largely gathering information and analysis while the second begins to separate tasks and define what can be done while the machine is running and what can be done while the machine is stopped.

​  Of all the steps in a setup or changeover reduction, separating internal and external activities may in fact be the most important as well as the simplest steps you can take.  In the most general sense, performing activities like preparing tools, kits and materials as well as transporting items while your line is running can reduce setup time by as much as 50%.

In this lecture we will discuss the difference between lean thinking and traditional thinking.  Let’s recall two of the types of work.  Those work activities that add value and those that do not.  In the video above we see an activity that is adding value.  Value added work has three characteristics to it: 

1. Somebody is willing to pay for the activity.
2. Transformation that moves the process closer to the end objective occurs.
3. The activity is performed correctly the first time through occurs.

Before improving anything in a setup, we must first consider the current state or common problem areas of what we are improving.  In the case of setups, changeovers or turnarounds there are traditionally 4 basic steps where problems and opportunities fall.  Those steps are:

1. Preparation.
2. Removing and Mounting Tools and Parts
3. Calibration.
4. First Articles, Trial Runs and Adjustments.

  Memorial Day is a special holiday that is celebrated every year.  Though many of us may think of those we have lost every single day, for one day an entire country stops to celebrate the lives of fallen soldiers.  These brave soldiers are the essence of improvement. 

  If you travel into any machine shop, office or hospital facility in the world guaranteed you have seen a changeover before.  The changeover occurs in between the last good part or service until the next good part or service.  Some examples would be:

1. Changing tooling.
2. Patients service completion.
3. Changing paper in a printer.
4. Taking one batch of cookies out of the oven in order to start a new batch.  

This "in-between" time is usually spent performing wasteful activities which often result in long changeovers that inevitably eat up value added time.

  Almost every project will include brainstorming of some kind at some point in the project lifecycle.  Brainstorming sessions can be a powerful gateway to unlock solutions, make issues visible, prioritize actions and bring experienced minds together.  When individuals come together as a team, innovative ideas can be born.  One of the struggles of being a part of a powerful and productive brainstorming session is that they generate many great ideas and often reveal a large amount of issues.  This can leave a group feeling overwhelmed.  Often times, the wide array of ideas can be hard to organize, understand, validate and act on.  Worse yet, many members of a team might leave feeling invalidated, unheard or completely shut down. 
  

  The fishbone diagram, cause and effect, or ishikawa diagram is one of the most common quality tools used today.  Best known by its resemblance to a fish's body the fishbone diagram is used to show the many possible causes for an effect. The tool is used to help coordinating brainstorming in an effort to discover root causes.

  In a world full of opportunities to improve, trials, countermeasures solutions and yes, waste, we all have much to be grateful for.  Whatever position you are in, whatever place you are at, gratitude can be a powerful tool if harnessed and used regularly.  Studies all around the world have shared the benefits of gratitude in the workplace, homes and in daily practice.  In this, the spirit of gratitude and before you share in the comments section below what you are grateful for, we would like to say, thank you.  Thank you to each of you who work your hardest everyday.  Thank you, to each of you who come home happy and ready to serve those you love.  Thank you, to each of you who have indeed IMPROVED the world through gratitude.

​  The first day on the job is always an exciting experience for any new employee.  A new chance to show your skills, meet new people and grow in a new organization.  Excited to learn something new in training you get thrown to the wolves and here the phrase "you will figure it out."  That can be a bit scary to say the least.  Surprisingly as you start figuring out everything has procedures connected to it.  Three days later and you have mastered erp, assembly and every office function in the organization.  A bit surprised by this you're off to a great start!