Jan 2 2014
Lean and Management Processes
An online sparring partner of 15 years, Bill Waddell, concluded our latest exchange with the following:
“Lean is comprised of three elements: Culture, management processes and tools. While you obviously have a keen awareness of the culture and tools, you continually under-appreciate the management processes, Michael.”
It is a 3-step progression: first, Bill makes a general statement of what Lean is, then he points out a serious shortcoming in my thinking, and finally he misspells my name.
As I am not trying to go global cosmic with Lean but instead remain focused on Manufacturing, rather than Bill’s three elements, I see Lean as having the four dimensions identified by Crispin Vincenti-Brown. Whatever you do has some content in each of the following:
- Engineering, in the design, implementation, and troubleshooting of production lines.
- Logistics and Production Control, covering both physical distribution and the processing of all information related to types and quantities of materials and good.
- Organization and People, covering the structure, sizing, responsibilities and modes of interaction of departments in production and support, to run daily operations, respond to emergencies, and improve.
- Metrics and Accountability. How results are measured and how these measurements are used.
Attention must be appropriately balanced in all of these dimensions and, if one is under-appreciated in the US, it is Engineering, not Management. Metrics and organization issues hog the attention; what little is left over goes towards Logistics and Production Control, and Engineering is taken for granted. The tail is wagging the dog, and reality bites back in the form of implementation failures.
What is a management process, and how does it differ from a tool? The term sounds like standard management speak, but, if you google it, the only unqualified reference to it that comes up is in Wikipedia, where it is defined as “a process of planning and controlling the organizing and leading execution of any type of activity.”
Since Henri Fayol, however, we have all been taught that the job of all managers is to plan, organize, control, and lead. In those terms, there doesn’t seem to be any difference between a “management process” and just “management.” All other Google responses are for the processes of managing different functions, like the “Project Management Process,” “Performance Management Process,” “Change Management Process,” or the “A3 Management Process.” The corresponding images are a variety of box-and-arrow diagrams, pyramids, wheel charts, dish charts, and waterfalls/swim lanes, as in the following examples:
A manufacturing process is the network of tasks to make a product from materials — with routes that merge, branch, and sometimes even loop. A business process, likewise, is a network of tasks to turn inputs into outputs, like the order fulfillment process that turns customer orders into deliveries. A political process is also a network of tasks leading to a particular result, like the election of a president or the approval of a budget. So, what about a management process? And what is the level of appreciation that it deserves?
Bill is the one who should really explain it, but, if I were to use this term, at the most basic level it would be for what I have been calling protocols, by which I mean the part of management work that is done by applying sets of rules or procedures rather than making judgement calls. They are pre-planned responses to events that might occur but are not part of routine operations. It can be the arrival of a new member into a team, the failure of a truck to show up, or a quality emergency.
This is the spirit of Toyota’s Change Point Management (CPM), in which the pre-planned responses are prepared by the teams that are potentially affected by the events and posted in the team’s work place. When the event occurs. all you have to do is retrieve the plan and you know what to do. And it is usually a better plan than what you would have improvised in the heat of the moment.
At a higher level, I would call process a protocol used to organize the way you make judgment calls. You can’t set the strategy of a company by applying rules, but you can use Hoshin Planning to organize the way you do it. A process like Hoshin Planning is akin to the rules of a game; it doesn’t determine how well the managers play. If they just comply with a mandate and go through the motions, they will produce a certain result. If, on the other hand, they understand what they are doing, connect it to their own work, and see the value in it, then they will produce a different result.
A good process does not guarantee a good outcome, and great teams have been able to coax performance out of dysfunctional processes. What is the proper level of appreciation for these management processes? Clearly, there is more to management than processes, and the best managers are those who excel at endeavors for which there is no script.
I learned to appreciate the relationship between management and engineering in Manufacturing from working with my mentor, Kei Abe. When he took me on as a junior partner in 1987, one of the first things I learned from him was to approach problems in a holistic manner, simultaneously at the technical and the managerial levels. I saw him coach a shop floor team on the details of SMED in the morning, and the board of directors on company strategy in the afternoon. It’s not a common mix of skills, but I believe it is what a manufacturing consultant should have.
Jan 7 2014
Using videos to improve operations | Part 7 – Detailed review of process segments
This post was co-written with Asenta’s Roberto Cortés and Juan Ortega, based on a joint project in Spain in October, 2013. A detailed analysis of the video recordings on two operations was key to generating improvement ideas that the plant has implemented since. The company had shot some videos of operations before, but not used them this way before, and it was a learn-by-doing experience for the participants.
The demand for the company’s products is growing, and it is struggling to keep up. Its core technology is a fabrication process, and engineering has focused its attention on it to increase capacity. After fabrication, however, the product needs several assembly operations. From direct observation, it was clear that the operators were working at a pace that could not be sustained for a whole shift. The manager confirmed that the pace slackened and the quality dropped towards the end of the shift.
The challenge was therefore to change the assembly process so that the operator could complete the tasks within the takt time of about 60 seconds, at a steady, sustainable pace, without running ragged or getting exhausted. While on site, we focused on two operations, shot videos as recommended in earlier posts — from an elevated position and focusing on the operator’s hands — and coached the plant team on reviewing the videos, with the goal of enabling them to do it on their own for the other operations.
Preparation
The detailed review breaks the operation down into its smallest identifiable steps to discover improvement opportunities for each. If you are going to do this on a regular basis, you should probably invest in software to collect timestamps from videos, categorize the steps, and record improvement ideas, like Timer Pro or Dartfish. Timer Pro was developed specifically for Manufacturing; Dartfish, for sports, but it has also been used in Manufacturing.
For the first time, it is best to do it on short operations, and you can make do with an Excel spreadsheet on which you manually record the timestamps. It needs the following columns:
Sufficient time has to be allowed for the detailed review. It is customary to allow between 3 and 5 times the length of the recording and even more if the recording is very short. It is recommended to have a sample of the product and components at hand where the review is being held.
Review
The video is analysed and the spreadsheet completed step by step. For short steps, you can play the video in slow motion to give time to observe details. Because you are going to be adding times, you need record the timestamps at a higher precision than you are really interested in. For example, to analyze time in second, you need to record the timestamps to one tenth of a second. The video and the form are shown on the screen at the same time.
While conducting the analysis, do the following:
You can generate your own categories as you go along and standardize them as you reach conclusions. There must not be too many (5 better than 10) and they are usually of the following type:
If there are large differences in how different operators perform the operation, several videos can be screened at the same time, with the same task carried out by different operators. It is essential to carry out this detailed review with the operators in the videos. They know things that nobody else knows, and have ideas that you want to use.
Conclusions
When you analyze operations for the first time, it is common to discover that about 40% of the time is spent on activities other than assembly or test. This is due to a combination of wrong sequencing, redundant steps, multiple handling, inadequate fixtures, inconveniently located tools or parts, etc.
Of course, not all of these can be eliminated easily. Some can be, by redesigning or retrofitting the work station; others can be taken out of the assembly flow and performed in parallel so that, for example, the operator does not have to prepare a part while the product waits. The net productivity increase that can usually be accomplished is on the order of 30%, without overburdening the operator. In our client’s case, this means making the assembly jobs sustainable while absorbing a higher demand.
Once the summary of times by category has shown the “gold in the mine” — that is, the improvement potential, the team fleshes out the ideas generated during the review of the video, tries them out as much as possible immediately, and turns them into proposals. The following pictures shows the flip chart with sketches of the proposals generated in our sessions, and a snapshot of try-storming.
The team then turns the improvement proposals into a detailed action plan for the short, medium-, and long term.
Once the improvements are implemented, the team shoots another video of the operation, for the following purposes:
Share this:
Like this:
By Michel Baudin • Technology 2 • Tags: Assembly, Excel, industrial engineering, Lean manufacturing, Productivity, Spreadsheet, Video