Retired course

This course has been retired and is no longer supported.

About this lesson

The Lean process analysis will reveal flow process flow problems. Lean techniques can be used to analyze flow at both a total process (macro) level or at a process step (micro) level.

Exercise files

Download this lesson’s related exercise files.

Lean Flow Analysis.docx
63.1 KB Lean Flow Analysis - Solution.docx
139.2 KB

Quick reference

Lean Flow Analysis

The Lean process analysis will reveal flow process flow problems. Lean techniques can be used to analyze flow at both a total process (macro) level or at a process step (micro) level.

When to use

This analysis is normally done during the Analyze phase. By that time the value stream map is complete including the data in the data boxes.

Instructions

Lean flow analysis focuses on identifying those areas of the process that create flow problems such as bottlenecks or flow constraints. There are both visual and numerical analyses that can be used.

Cycle Time Map

The cycle time map shows on a linear time scale where the process is spending value-added time and where it is not. The map often further refines that analysis but adding organizational swim lanes or swim lanes for major work stations. This visual analysis technique highlights the areas of non-value-added time that are often overlooked. If total cycle time reduction is a goal for the project, it is often much easier to reduce the non-value-added time than it is to change the value-added time.

Tangled Flow

Another visual analysis approach is to look for tangled flow. If the map that was created was a process map that showed all the branches and loops, the tangled flow is immediately obvious. If a value stream map was created, the value stream will always be a straight line with no tangled flow showing. However, in this case the indications of tangled flow can be seen by the effect that it is having on the data box values. At the point of constraint, there will often be large quantities of WIP inventory, large delays, and poor yield. Another effect that creates tangles is when item information becomes separated from the item during the process. Syncing those together again often creates a bottleneck.

TAKT

TAKT is the pulse rate of the process if it is well designed. In an ideal process, each step is completed within the allowed TAKT time and every item moves to the next step at the same time. This simplifies scheduling and can quickly identify when there is a quality issue or other performance problem because something doesn’t move when it should. The TAKT time can be calculated by diving the amount of time available for process work during a week by the number of items required from customer demand during a week. The resulting number is the TAKT time for each work station.

Hints & tips

  • Visual analysis tools are easier for operators and stakeholders to understand; so use them when appropriate.
  • A value stream map is very useful when working with a process that regularly produces similar items. But a process map is often better for the unusual process because it shows the tangled flow.
  • If a step is longer than TAKT and can’t be shortened because of the nature of the work at that step, then the resources to do the work at that step must be increased, so that they are working multiple units in parallel. I still run with TAKT, but now I have every other resource moving their item at the pulse point.
Login to download
  • 00:05 Hi, I'm Ray Sheen.
  • 00:06 And we've been focusing on some of the quality problem solving analysis.
  • 00:11 Well now, I want to shift gears to the Lean analysis and
  • 00:14 we'll start by looking at Lean flow.
  • 00:17 I'll start with an analysis at the total process perspective and
  • 00:21 end at the step level.
  • 00:23 So let's take a look at total process flow.
  • 00:25 In the Measure stage, we talked about measuring total time and
  • 00:28 measuring value added time.
  • 00:30 I even talked about calculating the ratio of value-added time over total time.
  • 00:35 Now we wanna analyze all of that to find problems.
  • 00:38 In my opinion, the best tool for that is the Cycle Time Map.
  • 00:42 On this map, we create swim lanes for organizations or major work cells.
  • 00:47 The horizontal access is the timeline
  • 00:49 with a duration of process start to process finish.
  • 00:53 Then within each lane, we show a bar for each step.
  • 00:55 The length of the bar is the amount of value-added time at that step.
  • 00:59 If there is no value-added time, the length of that bar is therefore zero.
  • 01:04 Between each of this step bars,
  • 01:06 we have a bar that is the length of the non-value-added time.
  • 01:09 I find it easier to read this map, if I make the colors of the bars for
  • 01:13 value-added time different from the color for a non-value-added time.
  • 01:18 Of course, you can get the value-added time and
  • 01:20 non-value-added time from the data box or time ladder on your Value Stream Map.
  • 01:25 Make certain when drawing this map that you're using times based upon
  • 01:29 a full 24-hour clock and 7-day work week.
  • 01:33 This is what the customer feels, so that is what we wanna use.
  • 01:37 We talked about that back when we discussed the measurements
  • 01:40 in the previous module.
  • 01:41 Now you can focus your analysis and identify improvement opportunities in
  • 01:45 the areas where there are large blocks of non-value-added time.
  • 01:49 I've often found when discussing how Lean analysis can
  • 01:52 reduce the amount of time in a process but there is resistance.
  • 01:56 People saying that they already are working as fast as they can.
  • 01:59 Then we collect the data and draw all the cycle time map.
  • 02:02 I explained that I am not trying to remove any time from the value-added activities.
  • 02:07 In fact, we often even add time to those activities to improve the quality.
  • 02:11 What we want to find and reduce are the non-value-added activities and
  • 02:15 this map shows that there are some big chunks of that time buried in the process.
  • 02:20 The next thing to analyze in your value stream map or process map is looking for
  • 02:24 tangled flow.
  • 02:25 The value stream map should only show the straight line flow of the process leading
  • 02:30 to the customer.
  • 02:31 If you're using a process map, you maybe showing lots of branches and loops.
  • 02:36 In a Value Stream Map, these were ignored because they don't represent
  • 02:39 first passed successful yield of that step moving towards the customer.
  • 02:43 One of the best ways to find tangled flow is to look for
  • 02:46 areas in the process where items are getting slowed down and stacked up.
  • 02:50 There's a bottleneck at that point which is constraining the flow.
  • 02:53 Investigate the constraint or
  • 02:55 bottleneck, determine what can be done to allow the majority of the processed items
  • 02:58 to continue to flow smoothly through that point.
  • 03:02 Another thing that will slow a process down is if there are decisions that must
  • 03:05 be made in the process by individuals who are not the primary process operators.
  • 03:10 These decisions will slow the process and create bottlenecks.
  • 03:14 That is the because the item must wait until the decision maker has time to do
  • 03:18 their review and analysis and made a decision.
  • 03:20 All of that is non-value-added time.
  • 03:23 In addition, there is the likelihood that the decision maker will sometimes make
  • 03:26 the wrong decision and reject a good item, or
  • 03:29 send an inaccurate item to the next step.
  • 03:32 As much as possible, we want to remove these external decisions and
  • 03:36 design the process and train the operators so that they know they have a good process
  • 03:40 item and can move it on without any external reviews.
  • 03:44 A final thing to watch for in the flow is when information about a process item
  • 03:48 gets separated from the item itself.
  • 03:51 This may be paper records or electronic records, but
  • 03:54 they start to follow a different flow for a portion of the process.
  • 03:58 And then, they must sync back up and get reconnected.
  • 04:00 Inevitably, one of the flows, the item or the information goes faster than the other
  • 04:07 and then we have something in the process waiting for the other one to catch up.
  • 04:11 Not to mention that sometimes an item or information is lost, or rejected while
  • 04:15 separated or the items or information change sequencing in one of the flows.
  • 04:20 Now, the resinking of data and
  • 04:22 items becomes difficult causing further delays and confusion.
  • 04:26 Try to avoid separating the item and
  • 04:28 the information about the data item until the end of the Value Stream Map.
  • 04:33 The final analysis for this module is the analysis of the flow at the step level.
  • 04:38 In a well designed Lean process,
  • 04:40 every item moves to the next step in the process at the same time.
  • 04:44 The process takes on a pulse rate or
  • 04:46 cadence of everything moving, one position forward.
  • 04:50 This cadence is called the TAKT time from a German word for
  • 04:53 orchestra conductor baton that taps out the beat for the orchestra.
  • 04:58 For this to work, each step must be designed so
  • 05:00 that it can be completed within the TAKT time interval for the process.
  • 05:04 The great thing about using this approach is that the problems and
  • 05:08 the process are immediately visible, the item did not move.
  • 05:12 Now when you are initially analyzing the process,
  • 05:15 if you find steps that are longer than the TAKT time,
  • 05:18 those will require additional resources often placed in parallel
  • 05:23 in order to keep up with the rest of the process and this step will hide problems.
  • 05:27 This is because we don't expect the item to move at the same speed
  • 05:30 as everything else when it is in that step, so
  • 05:33 we don't recognize a problem when it first occurs within that step.
  • 05:37 It's only when the delay becomes excessive that we finally realize what is happening.
  • 05:42 I've also seen a poorly designed process slow all the other steps to wait for
  • 05:46 the process step that has the longest time and treat that as the TAKT.
  • 05:50 This leads to missed deliveries and angry customers and stakeholders.
  • 05:55 To calculate the TAKT time is quite easy, it is the number of work hours for
  • 05:59 that process in a week or a day, divided by the demand for
  • 06:03 completed units through that process in a week or a day.
  • 06:06 So for example, if we have a 40 hour work week, We have 2400 work minutes.
  • 06:12 If we need to ship 200 units in a week,
  • 06:15 then we need to complete the unit every 12 minutes, that is the TAKT time.
  • 06:20 The work of every work station should be analysed to see if it can complete in 12
  • 06:24 minutes and the unit can be moved at the process pulse rate, the TAKT time.
  • 06:29 Lean analysis is normally focused on flow analysis.
  • 06:33 The Cycle Time Map, TAKT time, and even a review looking for
  • 06:37 tangled flow, are the tools to conduct your Lean Flow Analysis.

Lesson notes are only available for subscribers.

PMI, PMP, CAPM and PMBOK are registered marks of the Project Management Institute, Inc.

Gift this course