The final step in the problem-solving process is evaluating the results of your solution to confirm it actually worked. Every major problem-solving framework ends with some form of review, monitoring, or control phase. The specific name varies by model, but the purpose is the same: check whether the problem is truly solved, learn from what happened, and prevent the issue from coming back.
Why Evaluation Comes Last
Most problem-solving models follow a similar arc. You define the problem, identify its root cause, generate possible solutions, choose and implement the best one, and then assess the outcome. That final assessment exists because implementing a solution and solving a problem are not the same thing. A fix can fail quietly. It can partially work. It can solve one issue while creating another. Without a deliberate evaluation step, you have no way to know.
In the PDCA cycle (Plan, Do, Check, Act), the final step is “Act,” where you standardize the solution if it worked or loop back and try again if it didn’t. In the DMAIC model used in Six Sigma (Define, Measure, Analyze, Improve, Control), the final step is “Control,” which focuses on sustaining the improvement over time. The Eight Disciplines (8D) framework used in manufacturing ends with taking preventive measures: modifying management systems, operating procedures, and practices to stop the problem, and similar problems, from recurring. Different labels, same core idea.
What Evaluation Actually Looks Like
Evaluation means comparing your results against the targets you set before implementing the solution. This requires having measurable criteria in place from the start. If you decided a solution should reduce customer complaints by 30%, your evaluation checks the actual complaint data after implementation. If you were solving a personal budgeting problem by automating your savings, your evaluation looks at whether your savings balance actually grew over the following months.
Feedback channels need to be built into the implementation itself so you can monitor results in real time rather than guessing after the fact. This could be as formal as a dashboard tracking key metrics or as simple as a weekly check-in where you ask whether the situation has improved.
What To Do When the Solution Falls Short
If your solution didn’t hit its intended targets, the evaluation step helps you figure out why and where to go next. There are generally three reasons a solution fails:
- Poor execution. The solution itself was sound, but the implementation was flawed. You go back and rework how the solution is carried out.
- Wrong solution. The implementation was fine, but the solution you chose wasn’t effective. You return to the solution-generation phase and develop a better option.
- Wrong root cause. You solved the wrong problem entirely. You go back to root-cause analysis and identify what’s actually driving the issue.
This is what makes the evaluation step more than a formality. It’s the mechanism that tells you whether you’re done or whether you need another pass through earlier stages of the process.
Preventing the Problem From Returning
A complete evaluation doesn’t stop at confirming the fix worked right now. It also asks whether the problem could come back. Preventing recurrence typically means updating the systems and routines that allowed the problem to happen in the first place. In a workplace, that might mean revising standard operating procedures, adding a new quality check, or changing how a team communicates. In your personal life, it might mean setting up an automatic payment so you never miss a bill again, rather than just paying the one you missed.
The Eight Disciplines framework makes this explicit by calling for modifications to management and operating systems that prevent recurrence of both the specific problem and similar ones. The goal is to turn a one-time fix into a lasting change.
Capturing What You Learned
The best evaluations also include a brief retrospective. This means documenting what happened: what the original problem was, what solution you chose, what worked, what didn’t, and what you’d do differently next time. In a team setting, this involves collecting feedback from everyone involved, comparing project outcomes against the original goals, and recording the obstacles you encountered along with how you handled them.
This kind of documentation pays off the next time a similar problem shows up. Instead of starting from scratch, you have a reference point. You know which approaches failed, which succeeded, and what the real root cause turned out to be. Even for personal problem-solving, keeping a simple record of what you tried and what actually moved the needle saves you from repeating the same experiments.
Applying This to Everyday Problems
You don’t need a formal framework to use this final step effectively. Whether you’re troubleshooting a conflict at work, figuring out why your marketing campaign underperformed, or solving a recurring household issue, the evaluation step boils down to three questions: Did the solution work? Why or why not? What needs to change so the problem stays solved?
Skipping this step is the most common reason people find themselves dealing with the same problems over and over. Taking even a few minutes to honestly assess results turns problem-solving from a reactive habit into a process that actually improves your situation long term.