One way we can keep ourselves from falling into this trap is by having a formal (SPS) process in place.
Let’s fix it and make this problem go away.” However, if we rush to fix the problem too quickly, we may end up implementing a “solution” or “quick fix” that doesn’t solve anything because we didn’t take the time to truly identify and understand the root cause of the problem itself.
And it is often a solution that is short-lived or creates numerous other problems within the organization.
The Problem Solving Model provides you a road map to continuous improvement.
This is a ten-step model to guide you (and your team) through a structured problem solving process.
All too often, people jump from a problem to a solution.
In our hardmask example, we would collect batch data to identify the specific batches with the elevated defects and then study this data to see what they have in common.
Were they all made in a particular manufacturing location or on the same equipment set?
This could mean updating specifications, writing new training materials, updating training packages or updating the FMEA.
In the case of our hardmask example, we would need to create specifications and appropriate testing methods that will alert us that a batch of raw material is bad before we use it. Monitor for Success After the solution has been implemented, test data can then be created to find which solutions offer the best improvements.