2-Phase Adoption: Implementing SPC for Manufacturing Quality Control
Get advance buy-in for a positive experience for all stakeholders.
Two masks symbolize modern theater: the Comedy and Tragedy masks that were worn in ancient Greece during the golden age, around 500-300 B.C. They appear together to show the extremes of the human condition. The perfect metaphor for theater, they demonstrate that any play is complex, touching more than one facet of our experience.
Likewise, implementing statistical process control (SPC) in manufacturing is a multifaceted project; it affects more than one layer of your organization, and more than one aspect of your teams’ experience. To cope with this complexity, it’s important to address your implementation in two phases, addressing two critical elements:
- the psychological element
- the functional element
These two elements encompass the facets of an SPC implementation: difficulty and ease, buy-in and practical installation, and—most important—failure or success.
Implementing SPC in Manufacturing: the Psychological Phase
The psychological phase is the toughest part of your implementation and arguably the most important. You want to get buy-in from the people who will be implementing your SPC system. Usually this means the IT team, but equally important are the people who will be using your system—the shop floor operators. These two groups are crucial to the success of the psychological phase of your SPC implementation, so you need them to be fully on board with the program.
The most obvious reason for wanting their buy-in is that if they want to do this—if they see the benefits of the SPC system you want to implement—they can make things go more smoothly, even help ensure success, not only for the initial implementation but also for continued utilization of the program to provide much-needed data.
The psychological phase can be difficult because you are asking people to commit to your implementation. This is the tragedy face in the drama-mask duo. But even though it’s a challenge, it doesn’t have to have a sad ending.
The first thing you must do with both the IT team and operators is get them involved right at the beginning. When you’re included in something—anything—you feel valuable and important. Your feedback has relevance. You are part of something bigger than yourself.
Sometimes it’s as simple as letting them know you are interested in an SPC solution, showing them the options (you may have two or three you’re trying to decide between), and getting their input.
Part of this discussion has to be saying, “Here’s what an SPC solution can do for you. This is what we’re planning.” Then ask:
- What do you think?
- Are there specific functions that you need?
- Are we missing anything?
- Will this help make your job easier and allow you to do it better?
Early involvement of the people who will be implementing and using the system is critical. If they are not part of the solution, you can pretty much count on them fighting you at every opportunity, with the goal of making your life just plain miserable. Their resistance can put at risk the success of the project—not to mention your job.
If you dictate terms by saying something like, “We’re putting in a new SPC system; it’s coming in the next few weeks. Get ready,” you will get pushback. The parties involved will not help your implementation go smoothly. You’re probably going to hear comments like “I have too much going on already. I can’t tackle another big project. You’re asking me to do extra work; am I going to get a raise for this?”
However, the positive results can be dramatic. The implementation can go much more quickly when everyone is involved. Part of human nature says that if I’m involved, if I really want something to happen, I will help make it happen. Make sense?
So, get buy-in. Get people involved. Make them part of the improvement process, including the implementation. Build that teamwork atmosphere and you will reap the rewards: a smoother, faster implementation, and then a smooth-running SPC solution.
Implementing SPC in Manufacturing: the Functional Phase
The functional phase is the comedy face in the drama-masks duo because the toughest work is done: people are committed and have bought into your SPC implementation plans. You’re all in this together. Presumably, they will now try to make this a success. They are looking forward to what this new SPC system can do for them. The rest—the functional implementation—is icing on the cake, right?
Well, not so fast! Now come the meat and potatoes, where the rubber meets the road (and other metaphors).
So, what is the functional phase of the implementation? It’s the engineers coming in and setting up and configuring the SPC solution. Again, this is going to go more smoothly if they are consulted at the beginning of the process.
Then, when the time comes to perform the functional SPC implementation, there are fewer surprises. They were consulted at the beginning, they’re in contact with the users (operators) of the system and know what they need, so configuring the system should go quickly and smoothly.
Marry Form and Function
Frank Lloyd Wright once said, “Form follows function—that has been misunderstood. Form and function should be one, joined in a spiritual union.”
That’s particularly true in the case of an SPC implementation. The form of your psychological implementation—the buy-in you earn from your IT staff and operators—joined with the functional setup and configuration of your system can, and should be, a seamless endeavor. Your SPC implementation will be a much better experience for your entire organization if it is, and you’ll reap the quality manufacturing benefits.
To learn more about the shift to a truly modern SPC software solution and the opportunities it can bring to your manufacturing organization, download our free white paper Enlightened SPC for Modern Manufacturing.