Cultivating Effective Problem-Solving Skills
During the course of a day, we are tasked with solving a wide range of problems from something more straightforward like figuring out how to restock the refrigerator to the more complex like managing a staffing crisis at work.
Some of the problems we face are so rote that the solution is a no-brainer. But applying a knee jerk response to more complex problems can result in poor decisions with big consequences, not the least of which could be avoidable delays in resolving the problem with wasted time and resources.
We do not always get the answer right on the first try but we can certainly maximize the likelihood that we have enough information to walk into a decision with eyes wide open.
What is “Solution Jumping”?
In essence, “solution jumping” is deciding on a course of action to address a problem without adequate information.
It’s very understandable to want to address an issue quickly and move on to the next, especially if you bear the weight of others depending on you for answers. Solution jumping may be efficient in the short term but often results in overlooking the core problem.
Why Is It Important to Avoid Solution Jumping?
Not all problems are accurately characterized and clearly understood. The issue may actually be symptomatic of a much deeper root cause problem that you risk overlooking in your haste to make a decision and move on to the next challenge.
In the medical world, this can translate to treating a symptom or a distracting anomaly (what’s often referred to as a “red herring”) instead of the disease causing the symptoms.
The outcome is that issues continue to surface because the root cause continues unchecked or the outcome falls short of generating the desired results. Arriving at a suboptimal or erroneous solution reduces and may even negate the return on investment of time, money, and other resources to tackle the problem in the first place.
So how can you avoid this and keep projects and implementation plans on track?
3 Things to Help You Avoid the Solution Jumping Trap
Ensuring an accurately characterized problem statement is a topic for another time but assuming that this step has been completed, the following actions can help minimize the temptation to solution jump.
It helps to set expectations for others that spending a little time on the front end to get coordinated is worth the investment to avoid a mess later.
1. Is there clear agreement on what the problem is?
Ensuring from the start that there is a clear problem statement is critical. Well-characterized problem statements include a description of what success will look like once the issue is addressed. If you are just joining a team in which problem-solving has already progressed, asking the stakeholders for a recap on the problem that the team is trying to solve will quickly level set the discussion for everyone to ensure the team is still on the same page and to minimize drifting off the plan.
2. What are the most viable options?
Once there is agreement on the problem statement, solutions should be brainstormed and then evaluated for viability. Here are questions you may find helpful to guide the discussion:
- How do the emerging options stack up against the success factors you’ve identified?
- What would have to be true for a solution to be considered a success?
- What risks or challenges are associated with each option?
- What is the likelihood and magnitude of impact if those risks come true or challenges remain?
- What countermeasures should be taken to pre-empt or address the risks and challenges?
Invariably, a short list of viable solutions will emerge and you will need to pick one or the team will need to make a recommendation to the designated decision maker(s).
3. How do you know you implemented an effective solution?
As noted earlier, despite best efforts to be thorough and thoughtful, not all initial solutions work as intended. Pre-agreed upon metrics or events that would trigger a time-out to re-evaluate should be noted up front with appropriate internal controls put in place to make sure they don’t get ignored (e.g., hard stop provisions in a contract or a policy/procedure). Periodic check-ins are also helpful to quickly note unintended and unforeseen consequences of a chosen solution so that the team can check and adjust.
Conclusion
Assuming a well-characterized problem statement has been described, taking a moment to ensure adequate understanding of the issue can make a big difference in an outcome that is effective and one that is not or, even worse, creates more problems. Having the awareness that solution jumping is a real phenomenon that poses risks to success is half the battle. Developing the skill and discipline to recognize a solution jump when you see one or to lead others in avoid falling into that trap to begin with will be invaluable in your efforts to artfully design and successful implement strategies and solutions.
For questions or to find out how EverSparq can help, contact christopher.kodama@eversparq.com
