Skip to content
LeanSuite
Open e-book "Why CI Programs Stall, and What the Ones That Last Do" showing its contents and a LeanSuite Tier 3 plant review
E-Book

Why CI Programs Stall, and What the Ones That Last Do

Continuous improvement programs often start with one excited CI lead and fade when the rest of the plant never picks them up. Angad Singh, Co-Founder of LeanSuite, on why that happens and what the programs that last do: someone pushing from inside, every open item tracked, problems fixed at the root, and one area at a time.

Read the full e-book on this page, or get the PDF with the form.

What You'll Learn

Why CI programs drop off once they reach the wider plant

Why someone has to push from inside, and where leadership comes in

How actions on notepads, whiteboards and registers slip through the cracks

How to tell a band-aid from a fix at the root cause

How to start with one area and lock in the gain with SOPs

The warning signs and questions to check every week

Download Free Guide Now

Fill out the form below to get instant access to "Why CI Programs Stall, and What the Ones That Last Do"

Phone

By submitting this form, you agree to our Terms of Service and Privacy Policy.

Read it online

The full text of the e-book. The PDF has the same content, laid out to print.

Chapter 1

It starts with one person

When it comes to the first entry point, whether it's the continuous improvement manager or continuous improvement director, they love it. They see it solving their problem and everything. But as soon as it gets to, okay, let's take this to a broader team, that's where it kind of drops off. Maybe there's tons of other projects, and other projects take priority, and it's like, we'll do this later on.

It's always like, this is great, but then that great doesn't go anywhere.

It has actually happened once with us, where somebody had bought, and it's not even that they had bought something really big. They were excited about it. So they got it for all of their seven facilities, but then at the end they ended up not using it properly, because I think the person who bought it, his vision was that it's kind of going to work automatically. But you need that push from inside.

A lot of times projects fail because the same people get assigned more and more and more projects. Usually what we as humans tend to do is, oh, let's give it to this person, he will do it. But it's possible that the project fails. It's not that person's fault. There's no time.

A lot of these engagements are one time engagements. If they truly understand the concept, then they should rather be doing it themselves. That's how they can sustain it. Otherwise they can never sustain it.

Chapter 2

Paying for it is not the same as wanting it

Putting money at something is one thing, but then really wanting it is another thing.

What we found in the past with our successful implementations is one thing: there was always a champion who we were talking to all the time, and that champion was actually selling inside the company.

It really comes down to building that cadence. All the companies that we worked with, they do have a champion within the facility. It's not like that's their sole job.

Is it different for smaller companies versus bigger companies? It doesn't matter. It depends on the leadership. Actually, it all comes down to leadership's mindset.

It actually does start from the leadership, so that if anything does come their way as a suggestion, they need to be looking at it with a very open mind. Because at the end of the day, I believe nobody out there wants to do bad. Everybody is trying to do the best of what they can.

If we look at lean and how it's applied, it's so natural. It's so common sense. It doesn't need to have the big names. I think people forget while they're in the jobs: if it was their own business, how would they treat it? I think the very first instinct would be, okay, let's go check the shop floor.

Chapter 3

Work on the process with the people, not on them

It's all about culture building. It's all about people, and then working on the process with the people, rather than on the people.

Culturally, maybe now it's taking a shift, because before it was, okay, whatever the leadership has said, you have to go with that. But to make true progress and to build long, 100 year businesses, you have to start involving people from the shop floor and build that culture.

At the end of the day, continuous improvement is everybody. Operators or hourly folks have their own onus in contributing to the entire company's initiative, and managers have their own onus in terms of how you take those initiatives and move them forward.

It's totally dependent on people. What I've seen in my experience is that people on the shop floor are always willing, because they're looking for some kind of direction.

People tend to generally get afraid when they hear that you're applying lean methodology and you're applying continuous improvement. They tend to get afraid: oh, what will happen to our jobs? But it's not always job cutting. Sometimes I've seen people that are completely opposite of lean just because it hasn't been shown to them the right way. But when they actually see it, they become the biggest advocate.

Listening to employee suggestions and listening to employee ideas is very important. They are day in, day out working on the shop floor. You have to take out time every single day to go and talk to people, which is also very needed. But you can't touch base with everybody in the factory every single day.

Quality is always thought to be this separate department, but it should be part of your operations. It can never be separate. I think we've been able to do a better job with safety. With safety, people have come to the point where operations takes ownership, because there's people's life dependent on it. Mindset needs to be there for quality as well. It's not the quality manager's job, or the quality supervisor's, to come in and check it.

Chapter 4

If it isn't tracked, it didn't happen

They should be updating the system, because then there's visibility. If someone says that I worked on it and it's not in the system, then that means they didn't work on it.

It's very important to capture each and everything, so that you can then work on it. If something is being tracked, you're sure that it's going to get worked on. If something is put on a register or somewhere else, then it just slips through the cracks and never gets worked on.

Usually what happens is people go on gemba walks, they find issues, and then everybody forgets about them. If you're going on a walk, usually people take a notepad or something, and then once they come back, it either stays on the notepad, or they let somebody know and rip out the paper. But there's no tracking for it.

The Japanese work slightly differently, because they would want to fix it right away and get it done. American culture is: okay, I'll make a note. I'll give it to the supervisor. The supervisor will give it to somebody else.

A whiteboard, once someone erases it, it's gone. There's no visibility into it. If someone a week ago said, okay, I will do this, and a week after it's still not done, there's no way to say that, oh, we did talk about this.

Those alerts, and even phone calls, they could pretty much go missing. If someone forgets about them, then you could lose a day or two in getting back into the conversation.

A lot of it is being done on paper. It seems to be that there's no conversion of it into action items. Being on paper, you require somebody to put them in the system to analyze the data, but if the data isn't even there, then there aren't any action items against them that you can track.

Let's say there's something that happens on paper on the shop floor, and someone else is putting that into Excel, and somebody else is building reports. That's the biggest non value added activity that we see in applying TPM and all these methodologies today. You just cut all that. But other than that, it comes down to how you're using that data now, and taking decisions out of that data.

They're just used to doing things manually. They find it easier to do it on paper or spreadsheet versus having a systematic approach. A systematic approach initially, yes, it would seem that it's costing you more, but in the long term it's much more beneficial, because you're able to pull trends, you're able to pull information or insight that you're not able to with pen and paper. You can never do that with pen and paper.

If something is assigned to you, then the question comes: why isn't it done? If someone can't do it, where's the comment? You didn't let us know right then.

Chapter 5

Band-aid or kill?

Once you start capturing those problems in one place, you should also start capturing what you're doing for those in one place, so that in one place you can see, okay, problem number one, this is our biggest problem for the last two weeks. Let's start tracking things, but let's also start seeing how soon are we getting to the root cause of that problem that we've already entered two weeks ago, and have we actually killed it or not? Did we put just a band aid at that time because we needed volume, or is it that we actually solved the problem so it will never happen again?

It could be for breakdown. It could be that a safety incident happened, but you want to record it quickly and then get to the root cause later. Or there was a quality incident that happened. It's kind of like you put a band aid right now, then you still want to close the loop by getting to the root cause later on.

How are you actually making sure that those things are captured, and you're getting to the root cause of each problem and making sure that this will never happen again? There's different parts to it. One is that you've identified the problem, which is just the problem. Second is you've identified why it actually happened. So you get to the cause, and capturing that root cause and fixing the root cause. Because once you fix it, you know it won't happen. But now also communicating it to the entire team.

Band-aid now, kill it later

  1. 1Now

    Identify the problem and record it quickly

    A breakdown, a safety incident or a quality incident.
  2. 2

    Identify why it actually happened

    Get to the root cause and capture it.
  3. 3

    Fix the root cause

    Once you fix it, you know it won't happen again.
  4. 4

    Communicate it to the entire team

A band-aid buys time when you need volume. The problem is killed only when the root cause is fixed and the team knows.

If I'm getting defects, why am I getting defects? Let's just fix it and make sure that this never happens again. Let's make it process.

Let's say there's a leak that is happening somewhere here, and next week again you have a leak somewhere here, and then the third week again you have a leak. You would want to know where your concentrated problem areas are, so that you can see: why am I having issues over here all the time? So that you can fix it once and for all. Again, that lean mindset.

Chapter 6

Start with one thing, and lock it in

It's like continuous improvement. You won't be able to do everything all at once. But you would want to start with something small and then build on it.

Pick one pilot area and pick one very specific pain point and start there, and then grow your team and do the train the trainer and expand it throughout the facility. That gives you a very solid structure to begin with.

Start with one thing, then lock it in

  1. 1

    Pick one pilot area

    The worst area, the one you feel isn't doing well.
  2. 2

    Pick one very specific pain point

    Start with tags, suggestions or kaizens, whichever group is most comfortable.
  3. 3

    Show success

    When you flip that area around, the people on the fence want to be part of it.
  4. 4

    Lock it in

    Build SOPs and activities around it, so they're done autonomously.
  5. 5

    Grow the team and expand

    Train the trainer and expand it throughout the facility.

Once you hit one bottleneck, you go to the next one. It keeps moving.

You won't be able to do everything all at once. Start with something small and build on it.

The idea is to bring that ownership down to the people on the shop floor, and they start working on those smaller initiatives and keep getting pride in doing those things by getting awarded and taking that initiative, so that everybody eventually gets into the culture. The way we encourage you to do that is by taking one small area, and you pick the worst area that you feel isn't doing well. And when you flip that around, then it's everybody else who's on the fence, they also want to be part of it.

Maybe some production folks that you feel will be the right people to be part of that training: maybe a supervisor, maybe a couple of operators that are the ones that are willing to change and make a change. Then definitely they become advocates later on, on the shop floor, that bring people that are on the fence inwards.

Start small, where you either start with tags, you either start with suggestions, or you just start with kaizens, depending on which group is most comfortable. Then show success with that, and then move on to the next one.

It's important that you went into your first machine and did all the work. But now you want to maintain it. You don't want to lose all of that. You want to build SOPs around it, activities around it, so that they're being done autonomously.

It's an ongoing process. Once you hit one bottleneck, you basically go to the next one and see opportunity. It keeps moving.

Chapter 7

The early warning signs

What is the open versus close? What is the average days of closure? What's your trend looking like? If things are opening more and more and they're not closing with the same gap, and the gap is increasing, that means there's a problem. Either we need more workforce, or people aren't closing those tickets on time.

If your cumulative chart is getting closer in line, that means things are moving good. If it's moving apart, that means something needs attention.

One of the customers had a problem where they said, okay, our tags are getting assigned way too many times. Let's say a tag came to me and I'm a safety supervisor, but I don't like my operations supervisor. I will reassign that tag back: no, this is not my task, operations need to take care of this. If you leave it like this, it's not going to get closed.

When you get to November, December, I'm assuming you would build your budget for next year and your savings target for next year. So come January you would then know that there's not enough projects in the pipeline, because the gap is huge. But if we leave it arbitrary and there's no tracking for it, then we always tend to miss on those savings targets.

If it says red, then you could be like, why wasn't this audit done? The conversation changes. We're not going to spend more than five minutes on any meeting, on the shift handover. If it's red, then let's just talk about that. If it's green, then we don't need to talk about anything. And if it's red, where is that open item? Last time we spoke about, we needed this part. Where is this part?

Chapter 8

Questions to ask every week

Five questions to bring to your weekly review.

  • If there's five or six different managers for different areas, who are the ones that are getting back to their people right on time? Who are the ones that are not getting back to their people on time?
  • What is the open versus close? What's your trend looking like?
  • How soon are we getting to the root cause of that problem, and have we actually killed it or not?
  • Why isn't it done? If someone can't do it, where's the comment?
  • If it was their own business, how would they treat it?

That's how you build a culture of continuous improvement.

Keep a copy

Download the PDF to print it or share it with your team.

Get the PDF