Today, I am going to be reviewing another problem solving method known as issue trees. Issue trees help in separating a significant problem into smaller, easier to solve pieces. This can assist you in solving your main problem by solving the smaller problems that are all a part of the original one. There are also two different types of issue trees. So, here is how the issue trees work, and the different versions of them!
In order to make an issue tree, the first set of actions you need to take is to put the main problem statement in some sort of box on a piece of paper or online drawing. Then, draw lines from this box to the right. Connected to these lines should be multiple boxes filled with sub-problems for the initial problem. After you do this, keep on repeating the second step. Once you find more sub-problems, find sub-problems for those sub-problems! If you continuously do this, you can reach a point where your problem is divided into a few easy problems that you can solve in a blink. Here is a visual to help understand issue trees even more.
Now, while this method is straight forward, there are still some tips to make your life easier when using issue trees! For example, using the 80/20 rule can aid you in saving time finding solutions. The 80/20 rule states that you only have to focus on and solve the most important sub-problems from your issue tree. Eyeing in on a few important issues can have the exact same result as solving every single problem. This can help you save countless hours, especially if you are solving a difficult and long problem.
Another trick is MECE, which stands for mutually exclusive, and collectively exhaustive. The collectively exhaustive means that there are no gaps of information. There is nothing missing, and all of the information is accessible. Mutually exclusive means that everything is covered once and once only. Pieces of information should not be repeated in the issue tree. If you make an issue tree that does not follow either or both of these concepts, then even if you follow the 80/20 rule, your actions will end in failure.
In the very beginning of this post, I said that there are two types of issue trees, and this is when I will cover them. The first type is the problem issue tree, which is the one in the image above. You find sub-problems for your main problem, and continue doing this until you find root problems. This is also known as the why issue tree, because asking why questions is how you find sub-issues. The other version of issue trees are solution issue trees. Solution issue trees are when you ask how questions in order to find a solution to your problem. Here is an example of a solution tree.
In this solution tree, you would start off by putting down what you want to improve in the box to the left. After you complete this, put down a few possible solutions for your problem. Then, you will put down solutions that tell you HOW you would do the possible solutions you just listed. You can repeat this until you find the exact right solution for your problem.
So, now you know everything about Issue Trees and how you can make them. However, before you leave, I want you to take a quick look at an example I made up in order for you to better understand this topic.
In the example above, let’s assume that I run a bakery. I feel ecstatic about creating a bakery, however in the first few months, while I get a surprising amount of customers, most of them leave after trying my samples. So, I create a problem issue tree, and try to figure out what solutions I can get. In this issue tree, I start off by putting my problem statement, which is that I can not sell my cakes due to customers leaving after trying my cakes. Then, I put down some sub-problems. These consist of me possibly using low-quality ingredients and also using inadequate recipes.
Now that I have my main problem and sub-problems, I can start digging deeper and get to the bottom of why my customers leave after taking samples. For sub-problem 1, I put down that I might be buying eggs from a company that is second-class. This could lead to my products tasting terrible, as I am using nasty eggs in my cakes. Another possible problem could be that I am accidentally using expired milk, and it is pretty obvious that using expired milk would make my cakes taste awful. For sub-problem 2, I put down that my recipes could have too little flour. In baking, using too much or too little of a certain ingredient can ruin the final result. This means that using too much flour will lead to my cakes being dreadful. This concept also applies to my second sub-sub-problem, in which I put down that I may have used too much baking soda and baking powder.
Something to note is that this is definitely not a perfect issue tree. There are definitely better examples out in the endless depths known as the internet. However, I still hope that this specific example at least allowed you to understand issue trees even more than you did before.
In the end, I taught you all about issue trees. I explained the different types of issue trees, gave you diagrams for each type, and even gave you an example. I hope that I was able to teach you at least a tiny bit about issue trees, and I hope that one day, issue trees will allow you to find a solution to a problem you face. Anyways, please check out any of my other blogs about other problem solving methods. I thank you and pray that you have a wonderful day!