Sometimes the Right Choice isn’t the Convenient One

I was the operations manager at the St. Helens Oregon ceiling tile plant. I was responsible for the board forming and the fabrication units. It was here that I made a major rookie mistake that would stick with me throughout my career. Here’s the story.

The board forming unit consisted of a mixing, forming, drying, and board cutting and stacking operation. The fabrication unit consisted of all equipment that converted 4 by 8-foot boards into 2 by 2- foot and 2 by 4-foot painted tiles packaged and ready for shipment.

The board forming unit had an eight-level dryer that was approximately 400 feet long. A slurry would enter the dryer at extremely high moisture levels and exit it fully dried and ready for processing. Boards would travel at slow speeds through the dryer on their way to be cut at a large panel saw, called the Dry Saw. If there was a problem at the Dry Saw, things could be slowed down in the dryer for a short period of time, but eventually all  boards in the dryer had to be offloaded, or there could be major damage to product, or worse, a fire.

One day, we were experiencing significant downtime in our fabrication unit. With low maintenance staffing, I requested all mechanical help in fabrication, and they came and deployed to the equipment that was having trouble. They were working beneath a conveyer, deeply involved in repairing a critical problem. It looked like they had about 45 minutes of work left to do when I got the call that we were having a problem at the Dry Saw and that boards were backing up in the dryer.

I told my team manager to monitor the situation, but I decided to have the mechanics continue working on their repairs in the fabrication unit. This was a bad choice. After 20 minutes, things got worse in the board dryer and a major jam occurred. And then, a fire. Everyone in all departments stopped what they were doing and came to contain the fire and dig out smoldering boards in the dryer. Taking a 14-foot rake, I helped pull wet boards out of the dryer while others doused the fire and helped clean up a huge mess. After 16 hours, we had everything cleaned up and were able to safely start operations back up.

It was a huge mistake on my part. I realized I should have responded to the board forming unit issues immediately, even if it would force our fabrication unit to stay down longer. My boss wasn’t happy about my choice, but was understanding. He told me, “All new production managers make this mistake. But, only once! Always pick the board forming unit issues first, then fabrication. Unless there’s a major safety or health incident in fabrication.” I heeded his advice from then on.

The Five Whys

The Five Whys is a method that can be used to understand why a change isn’t being followed. It helps you get to the root cause of any resistance or problem you observe. If you find someone doing something in a non-standard manner, ask why until you get to their motivation for doing it differently. It may take five or more whys. It could take less. Here’s a sample conversation:

Sue (Joe’s manager): “I notice you’re adjusting the equipment differently than the new procedure. Can you tell me why you are doing it this way?”

Joe: “From my many years of experience, I have found that it’s better to adjust the equipment in the order I’m doing it.”

Sue: “I know you think it’s better. Can you tell me why you think it is?”

Joe: “It’s the most comfortable and stress-free approach I know.”

Sue: “It can be uncomfortable doing something differently and it takes time to get used to something new. Can you tell me why you’re more comfortable doing it the old way?”

Joe: “It doesn’t make sense to do step 3 after step 2. Step 3 should come after step 4.”

Sue: “Why do you think step 3 should follow step 4?”

Joe: “If I do it my way, I don’t have to search for the wrench when I get to step 3. I took it out of my tool box and used it when I did step 4. Then I can carry it to do step 3.”

Sue: “Are you aware the team mounted required tools at each step? You don’t have to carry them with you anymore.”

Joe: “I didn’t know that. I guess I forgot.”

Sue: “Let me show you. See, the tools are right where you need them for each step.”

Joe: “I can’t believe I missed that. Thanks for showing me.”

Sue: “You’re welcome. Now that you know, I need you to follow the prescribed order. When you do, please let me know what you think.”

Joe: “I’ll give it a try and let you know how it goes.”

In this case, it took four whys to uncover the root cause of the issue. What else happened? Sue listened to Joe. She helped him understand the proper procedure. She reinforced the requirement to follow it, identified the benefits, and made the commitment to get his feedback.

Sue demonstrated Accountability. Joe is likely to do the right thing from now on and may communicate what happened to his co-workers. Holding yourself accountable is not always easy and can be time consuming, but the benefits outweigh the effort.

Sometimes It’s a Financial Question

A global ceilings manufacturer was building a plant in China. Things were going pretty well until they realized they were going to be two months late starting up. The team wasn’t sure what they could do to get back on schedule, so I was invited to join them and use Lean thinking to help solve the problem.

I had been to China before, helping the team with Kaizens during different stages of plant development. These Kaizens were more challenging than most, as they required an interpreter, so the team and I would understand each other.  As a result, I had to communicate more slowly than I was used to, making sure I didn’t use any slang or other terms unfamiliar to Chinese team members.

As I boarded my flight to meet them, I wondered what I could do to help the team. After all, they had been working and solving problems as they came up all along the way. They had their best engineers and scientists on the team who had come up with many breakthroughs. Why couldn’t they solve this problem? Why was this problem stumping them to the point they required my help? I always sleep well on airplanes, but during this 15-hour flight to China, I was more restless than usual.

I met my interpreter on Monday and we reviewed the approach for the Kaizen. I would help the team look at their problem from many angles, trying to uncover opportunities they hadn’t thought of and brainstorm as many potential solutions as possible.  My interpreter reminded me in the Chinese culture, people don’t like to make a suggestion or offer an idea unless they are completely sure it is correct. In a Kaizen we want people to bring out ideas that aren’t fully formed or guaranteed to work, so others can build from them. I knew I had to make the team comfortable to say anything at any time. To do that, I would use sticky notes and pens and ask all team members to write their ideas down and share them, one person at a time, one idea at a time. This technique tends to make people comfortable saying whatever they are thinking, regardless of the country or culture.

The goal of our Kaizen was to have the plant start up on time. Our objective was to develop contingency plans to take two months out of the schedule and meet the initial commitments to the Board of Directors and the customers in China.  I knew very little about why the plant wasn’t on schedule, so I had the team brainstorm possible reasons why they were behind schedule. Using the sticky note technique, more than 100 ideas were written down, some in Chinese, some in English. Knowing we couldn’t solve all 100, I asked the team to prioritize the most critical reasons for the delay. I used a technique called “multi-voting”. Each team member placed a dot or a mark on the sticky notes that contained the top five ideas or reasons for the delay from their perspective. The sticky note with the most dots was the idea the team felt was the most likely reason for the delay.

There were 15 team members and 14 dots on a sticky note that said, “Two month wait for government testing.” Intrigued, I asked for an explanation. They told me the Chinese government must qualify and approve the first ceiling tile produced by the plant before they were allowed to produce more and sell to customers.  It took two months from the time a test was requested to the time a tile could be submitted for testing, and then another week to get results. The team wouldn’t produce tiles that weren’t officially approved, so they were going to wait those two months for approval before starting full production. The plant had scheduled production of the first acceptable tile around April 1st, 15 days before the original start-up date commitment, and then would have to wait two more months before gaining approval to produce tiles for sale, thus creating a two-month delay. It was then I knew there was an answer, but the team had to come to the right conclusion. It was time to ask some questions and facilitate them to an answer.

Question one was, “How much does it cost to submit a tile for a test with the Chinese government?” The answer was $10,000.

Question two was, “How long does it take from the time a test is requested until test results or approval is given?” The answer was two months.

Question three was, “When do you believe you will be able to produce tiles?” The answer was around April 1st.

Question four was, “What is the cost of the plant starting up after April 15?” The answer was $60,000 per day, as defined in the original project investment request.

Question five was, “Do you currently believe that the tiles you will produce on or about April 1st will meet the Chinese government requirements?” The answer through internal testing and quality control was “highly probable”.

Question six was, “Are you willing to risk $10,000 by submitting a test request to the government two months in advance of producing your first production tile, in order to save $60,000 per day for the next two months?”

At that point, the team knew what it had to do. The rest of the Kaizen was spent developing plans to ensure a successful test by the Chinese government on April 1, two weeks ahead of schedule. In the end, the plant started up on March 28, and the team saved over $2.5 million for the company. The lesson here is that when you frame a problem on a financial or factual level, rather than an emotional level, the answer becomes obvious.

A Simple Way to Think about a Problem You Want to Solve

Many years ago, I was having difficulty getting my mind straight about a problem that I wanted to solve. A co-worker of mine introduced me to a thing he called a “Task Cycle”. Once I understood it, I had a simple way to go about solving problems and executing tasks.

The Task Cycle was developed in the early 1990’s by Paul Boulian and revised by Marlyn Rabenold eight years later. I had the good fortune of meeting Marlyn and was amazed at the simplicity of thinking that can be used to help solve the most complex problems. Now, I want to share it with you.

The Task Cycle has 4 components: Purpose, Products, Process, and Functional Capabilities. It is truly a cycle and can be visualized in this way:

When you are planning a task (or planning to solve a problem), you follow the cycle counter-clockwise, from Purpose to Products, Process, and then Functional Capabilities. When Executing a task, you follow the cycle clockwise and start at the Functional Capabilities and end at Purpose.

Purpose

This is the reason that we are trying to do something, or the problem that we are trying to solve. That seems simple, and it is, but building a clear purpose statement is critical, and should not be taken lightly. As is said, the first step in solving a problem is know that you have one in the first place. When building a clear Purpose statement, consider and communicate why you want to do something, as much or more than what the specific task is. Consider these components of the Purpose statement with this recommended format:

“TO” – describe the task to be done or the problem to be solved

“IN A WAY THAT” – describe the benefit to be realized by the accomplishment of the task. Think in terms of the customer of the task.

“SO THAT” – describe the impact or result the task will have on the organization

Using the experience of writing this article, here’s an example of a Purpose statement:

To write a description of the Task Cycle, in a way that:

-          Exposes the reader to a new way of thinking about a task

-          Provides a simple construct for dealing with a complex problem or effort

-          Engages the reader’s interest

So that this knowledge will help readers in their efforts to solve problems in the future.

Clarity of purpose helps us gain alignment and support from those who will either help us with our task or those who have assigned the task to us.

Now that Purpose has been established, it’s time to move on to Products.

Products

Products are the output or results that we are trying to create when we accomplish the task or solve the problem. A good question to ask is, “If we accomplish the task or solve the problem, what would we see or know that reinforces that the task is complete or the problem is solved?” We aren’t always looking for a physical product, but also non-physical or virtual products. These can be timing, a new way of doing things, or other similar results. Products of the prior example could be:

1.       Ten or more responses or inquiries about the article

2.       Three shares of the article

3.       A phone call to discuss more in detail about the article

Now that the Purpose and Products have been identified, it’s time to move on to Process.

Process

How are we going to get the products that tell us that we have achieved our purpose? What is the methodology or approach that we will use to do this? We can now design a process to specifically accomplish the purpose and deliver the products as stated. Whether we use existing tools and methodologies that we are familiar with, or do research and ask others for their input, we can now test our thinking and approach and see if it delivers the desired results. We want to think through the series of steps and actions that we will take in order to get where we want to go. Because we are clear on purpose and products, we can now design process in a way that has the least amount of effort and waste associated with it.

For the prior example, the process being used is to research the original thinking and documentation on the Task Cycle, consider my personal experiences with it, and try to describe it in a way that the reader can utilize practically. Time will tell if my process was properly thought out.

Functional Capabilities

Do you need people to help you accomplish your task or solve the problem? Do you need tools for this? Are there skills that need to be acquired? What else do you need to solve the problem or complete the task? These are the questions that should be answered in order to identify the functional capabilities needed.

When all four components of the Task Cycle are put together, they should be the foundation for the effort. You should share your thinking with others to see if you have missed any vital elements, always improving as you go. You might even need funding, and that is why it is critical to have alignment around your task cycle.

Earlier in the article, I stated that when you are executing a task or solving a problem, you now go through the task cycle in the opposite direction. What I mean is that you use the functional capabilities to follow the process, which delivers the products and ultimately achieves the purpose.

Although this is not new thinking, I believe that many have forgotten about the Task Cycle and are missing out on this simple way of solving problems and accomplishing critical tasks. I will be interested to see if I accomplished my task in providing you with information that you can use. Your feedback will let me know if I have done so.