This entry is part of a multi-post case study. So we’ve developed our why tree: we’ve identified all the potential reasons why we’re having our problem and we’ve organized these reasons in such a fashion that they only appear once in the tree. Next we need to test these hypotheses. […]
This entry is part of a multi-post case study. So, we’re back to our cables negotiation. We’ve defined the problem and identified the basic framework for breaking down the key question. Next we need to build our diagnostic tree, why issue tree. Building the why issue tree / issue map essentially […]
In a complete problem-solving process you’ll have to build two logic trees: one “why” to find the root cause of your problem and one “how” to identify potential solutions. The good news is, you might not have to start them from scratch if an existing framework can be leveraged. Consider using […]
Mutually exclusive and collectively exhaustive (MECE) thinking ensures that you consider all solutions to your problem exactly once.
Issue trees (also called issue maps and logic trees) are at the heart of our problem-solving approach and, therefore, are a recurrent theme on this site. We use two types of trees: diagnosis trees and solution trees. An issue tree is a graphical breakdown of your key question. Trees have […]