In many companies, problems arise in several places at once. In one area, defect rates increase; in another, deadlines are missed; elsewhere, customer complaints keep repeating; and in another part of the business, corrective actions remain open for too long. In such situations, managers naturally want to solve everything at once. But in practice, this often leads to the opposite result: the team becomes overstretched, causes are not analyzed deeply enough, and the same problems come back again.
That is why, in a mature quality management system, the step-by-step problem-solving method is especially useful. This approach means that the organization selects one priority problem, investigates it thoroughly, removes the root cause, standardizes the solution, and only then moves on to the next issue.
This method aligns well with the logic of ISO 9001, because the standard expects organizations not only to record nonconformities, but also to analyze causes, take effective actions, and achieve lasting process improvement. In other words, a step-by-step method helps replace chaotic “firefighting” with a systematic way of dealing with problems.
What It Is
The step-by-step problem-solving method is an approach in which an organization does not try to deeply resolve all issues at the same time, but instead focuses on one significant problem, completes the full cycle of analysis and solution for that issue, and only then moves on to the next one.
The core idea here is discipline. Problems are not ignored, but they are also not mixed together into one vague and unmanageable mass. First, a priority problem is selected. Then possible causes are formulated as hypotheses, those hypotheses are tested, a countermeasure is implemented, the result is checked, and a new working standard is established.
This method is especially useful where:
- problems keep recurring
- causes are not obvious
- the team is used to treating symptoms instead of causes
- corrective actions are closed only formally
- resources are limited and focus is essential.
In essence, this is not just a way to “deal with one issue,” but a management habit of structured, sequential improvement.
Requirements of the Standard
There is no separate requirement in ISO 9001 called “step-by-step problem solving,” but the logic of the standard is very close to this approach.
In practice, the method supports requirements related to:
- nonconformity management
- corrective action
- cause analysis
- monitoring and evaluation of effectiveness
- continual improvement
- risk-based thinking.
In simple terms, the standard expects the organization to:
- notice problems
- respond to them
- look for causes rather than just remove effects
- check whether the solution worked
- draw conclusions and improve the system.
That is exactly why the step-by-step problem-solving method fits so well into QMS implementation and ongoing work under ISO 9001.
How It Works in Practice
In practice, the method usually follows a simple six-step logic.
1. Describe the problem
The problem must be formulated clearly.
Poor example:
“We have quality problems.”
Better example:
“During the last quarter, the number of complaints about incorrect order picking increased from 4 to 11 cases.”
The more precise the problem statement, the easier it is to move forward.
2. Select one priority problem
If a team tries to deeply investigate five different issues at once, the quality of analysis usually drops.
Priority can be chosen based on criteria such as:
- impact on the customer
- frequency of recurrence
- financial loss
- impact on delivery performance
- impact on process stability.
3. Find the root cause
At this stage, tools such as the following may be used:
- 5 Whys
- Ishikawa diagram
- fact-based observation at the place where the problem occurs
- testing hypotheses through observation and experiment.
It is important not to stop at the first convenient explanation. Statements such as “human factor” or “lack of attention” are rarely the real root cause.
4. Choose and implement a countermeasure
Once the cause is confirmed, the team defines a solution aimed specifically at that cause.
For example, if employees confuse similar components in the warehouse, the solution should not simply be “hold a conversation with staff,” but rather:
- introduce color coding
- separate storage locations
- improve visual identification
- add a control point during picking or release.
5. Check the result
After the countermeasure is implemented, it is important to confirm that the problem has actually decreased or disappeared.
This means comparing data such as:
- did the number of defects go down
- did complaints decrease
- did recurrence stop
- did the process become more stable.
6. Create or update the standard
If the solution proves effective, it should be embedded into the system:
- in the instruction
- in the work standard
- in personnel training
- in the checklist
- in the process map.
This is the step that turns a local fix into a real element of the quality management system.
Practical Example
Let us imagine a manufacturing company where oil leakage occasionally appears in an assembled product.
At first, the team assumes that the problem is caused by incorrect tightening torque at a connection point. A check shows that the torque is within specification.
Next, they verify compliance with the production process. Again, no deviation is found.
Then a new hypothesis appears: perhaps the wrong component is being used. This check confirms that some units were indeed assembled with a similar-looking but different part.
The team then identifies the root cause: in the warehouse, visually similar parts were stored too close to each other, and the labeling was not clear enough.
Countermeasures include:
- separating storage locations
- introducing color coding
- updating visual instructions
- strengthening control during material release.
After implementation, the problem stops recurring. The new arrangement is then incorporated into the working standard. Only after that does the team move on to the next problem.
That is the essence of the step-by-step approach: one problem, one full cycle, one lasting improvement.
Common Mistakes
The most common mistake is trying to solve everything at once. This almost always leads to superficial solutions.
The second mistake is jumping straight to actions without analyzing causes. In that case, the organization removes a symptom, but not the source of the issue.
The third mistake is failing to test hypotheses. The team may choose an explanation that sounds reasonable, but is not supported by facts.
The fourth mistake is failing to standardize the solution. In that case, even a good countermeasure may disappear over time, and the problem will return.
The fifth mistake is looking for someone to blame instead of identifying the weakness in the process. For ISO 9001 and for a mature QMS, improving the system is far more important than simply finding a person to hold responsible.
Practical Tips
Start with one genuinely important problem, not just the one that feels most urgent emotionally.
Always collect facts before starting the analysis. The fewer assumptions, the better the final solution.
Document the full course of the work: the problem description, the hypotheses, the tests, the chosen solution, and the results. This is useful for management, for the internal audit, and for future learning.
Check the problem where it actually occurs. The best conclusions are usually reached not in a meeting room, but at the workplace itself.
Most importantly, do not move on to the next problem until the cycle for the current one is complete: the cause is confirmed, the countermeasure is implemented, the result is verified, and the standard is updated.
Conclusion
The step-by-step problem-solving method is a simple but very powerful approach to quality management. It helps organizations avoid spreading efforts too thin and instead remove root causes in a disciplined sequence.
For work under ISO 9001, this method is especially useful because it supports key requirements of the standard: cause analysis, corrective action, verification of effectiveness, and process improvement.
When an organization learns to solve problems one by one, it becomes more stable, its processes become more manageable, and the quality management system becomes less formal and more useful for the business.