Solving Problems Like a Pro, Tips and Techniques

Problem-solving skills are essential to find efficient solutions to complex problems on a daily basis, make a real impact in our field, and to make informed decisions. Being able to identify and solve problems quickly and efficiently can make the difference between a successful project and a complete failure. Furthermore, effective problem solving can help you reduce stress, increase productivity, and have a better job experience.

In this article, we'll explore a few problem-solving methods and strategies to improve your problem-solving skills.

What problem-solving methods exist?

Problems arise every day in all aspects of life. Luckily, there's a set of techniques to help you solve them, we will explore the following:

1. PDCA (Plan-Do-Check-Act) Cycle
2. 5-Why Analysis
3. Ishakawa (Fishbone) Diagram
4. Simplified Failure Modes and Effects Analysis (SFMEA)
5. The Scientific Method
6. Critical Thinking

Each of these techniques provides a structured approach to problem-solving, allowing you to tackle problems in an organized and efficient manner. Let's take a closer look at each technique and how it can help you solve problems like a pro.

What is the PDCA Cycle

This technique is a four-step process for continuous improvement. It starts with planning, where you define the problem and come up with a solution. Then, you implement the solution, check to see if it worked, and act on the results. PDCA is particularly useful for solving problems that are repetitive or cyclical.

In practice this is how it'd look, let's say that every time a new feature is implemented and pushed to production, it causes the server to crash. The development team might fix the issue temporarily, but then it reoccurs a few weeks later when another feature is pushed to production.

The team might then use the PDCA problem-solving technique to identify the root cause of the issue. They would first plan by identifying the problem and gathering information on when and how it occurs. They would then do a thorough analysis to find the root cause of the issue, such as code inefficiencies or conflicts between features.

Once the root cause is identified, the team would create and implement a solution (do). This might involve re-writing code, adjusting server configurations, or adding new monitoring tools. After the solution is implemented, the team would check if the problem will be resolved and if the solution is sustainable over the long term. With that, the team acts by releasing the solution to production and monitoring the server to ensure that it is working properly.

Using the PDCA technique in this scenario allows the team to continuously improve the reliability of the web application and reduce the time spent on fixing server errors.

PDCA - sydle.com

Here's a mini-episode from Ray Dalio's Principles addressing a similar approach to solving problems: Youtube

What is 5-Why Analysis

"5-Why Analysis" is a problem-solving technique that involves asking "why" questions about a problem in order to determine its root cause. This approach helps you to uncover the underlying issues behind a problem and find its root cause, which is the key to implementing a successful solution.

To use 5-Why Analysis, start by asking "why" five times in a row to get to the root of the problem. For example, if the problem is a machine that is not working, you could ask "why is the machine not working?" The first answer might be "the electrical circuit is broken." Then you would ask "why is the electrical circuit broken?" And so on, until you have asked "why" five times and have found the root cause of the problem.

This technique can be used in a variety of industries and is often used in manufacturing and engineering. It is a straightforward and effective way to find the root cause of a problem and implement a solution that will prevent it from happening again in the future.

5-whys with examples - Indeed.com

How to use the Fishbone Diagram

This technique is useful in engineering as it allows you to break down a problem into smaller components, making it easier to understand and solve.

          Cause_1  Cause_2
          /        /
         /        /
Problem +----------------
         \        \
          \        \
        Cause_3  Cause_4

The Ishakawa diagram is named after its creator, Kaoru Ishakawa, who used it as a quality control tool in the 1960s. The diagram is shaped like a fish skeleton, with the problem being represented by the head and the causes being represented by the bones. To use the Ishakawa diagram, simply draw the fish skeleton and list the problem in the head. Then, brainstorm the potential causes and attach them to the bones as sub-causes. This process can be repeated until the root cause is identified.

Fishbone diagram - asq.org

The Simplified Failure Modes and Effects Analysis technique

This technique is especially useful in industries where product or process failures can have serious consequences, such as aerospace, automotive, and medical devices. By identifying potential failure modes, you can take steps to prevent them from happening.

The process consists of several steps, primarily:

• Listing the potential failures.
• Assessing the severity, occurrence, and detection of each.
• Prioritizing based on risk.
• Identifying corrective actions to mitigate risks.

The Scientific Method as problem-solving technique

This technique is based on the scientific method and is used to identify the root cause of a problem. Start by defining the problem, creating a hypothesis, testing the hypothesis, and then analyzing the results.

The steps of the Scientific Method are:

1. Observe and define the problem: Start by observing the problem and gathering information about it. Define the problem in clear and concise terms.
2. Formulate a hypothesis: Based on the information gathered, formulate a hypothesis or an educated guess about what might be causing the problem.
3. Test the hypothesis: Conduct experiments to test the hypothesis and gather data to support or disprove it.
4. Analyze the results: Analyze the results of the experiments and draw conclusions based on the data.
5. Evaluate and conclude: Evaluate the results and draw a conclusion about the hypothesis. If the hypothesis is supported by the data, it becomes a theory. If not, the hypothesis must be modified or discarded.

By following these steps, you can ensure that your problem-solving process is systematic, unbiased, and based on data and evidence. This technique is also helpful in avoiding common pitfalls such as jumping to conclusions or making assumptions without sufficient evidence.

Combining Techniques for Effective Problem-Solving

It is important to have a toolkit of problem-solving techniques at your disposal. But the best way to tackle a problem is to not rely on just one technique, but to use a combination of techniques that work best for the situation at hand.

For example, you could use the Ishikawa (Fishbone) Diagram to identify potential root causes, then apply the 5-Why Analysis to drill down further into the most likely cause. Or, you could use the Scientific Method to structure your problem-solving approach, and then use an SFMEA to identify potential risks and consequences.

The goal is to find the best approach that will give you a comprehensive understanding of the problem. This way, you can identify both internal and external factors that may be contributing to the problem and arrive at a solution that addresses all the underlying issues.

In short, combining problem-solving techniques allows you to tackle complex problems in a systematic and effective way. So, it's crucial to keep experimenting with different techniques and refining your approach until you find the combination that works best for you.

Closing thoughts

We've discussed several problem-solving techniques that you can use to identify and solve problems. Each technique has its own strengths and weaknesses and can be used in conjunction with other techniques for a comprehensive understanding of a problem. I hope that this article has provided you with a better understanding of these techniques and how they can help you to become a more effective problem-solver.

I've wrote an article about how to write an specification document, it provides a template to structure your thoughts and approach when solving a problem, you can find it here.

Resources

1. "Thinking, Fast and Slow" by Daniel Kahneman - This book explores the psychology of decision-making and how our minds often lead us to make irrational decisions.
2. "Problem Solving 101: A Simple Book for Smart People" by Ken Watanabe - This book provides a simple and effective approach to problem solving, using the author's own experiences and case studies.
3. "How to Solve It" by George Polya - This classic book offers a systematic approach to problem solving, using mathematical examples to illustrate key concepts.
4. "The 7 Habits of Highly Effective People" by Stephen Covey - This book covers the importance of proactive problem solving and the habits that can help us achieve it.

Let me know if you liked this post (or not), and if you'd like me to post on a topic of your interest!

Follow me to get notified when I publish a new post. And thanks for reading! :)