Logic Trees
Last updated March 27, 2026.
When people face a difficult problem, they often try to solve everything at once. The result is confusion. Too many possibilities are discussed, and the conversation moves in circles.
A logic tree provides a simple way to organize thinking.
The process begins by stating the problem clearly. Then the problem is divided into a small number of major categories. Each category is then divided again into more specific possibilities.
For example, imagine a team investigating a system outage. The first level of the tree might separate the possible causes into a few broad areas:
- Infrastructure
- Application code
- Data issues
- External dependencies
Each branch can then be examined more closely. Infrastructure might include networking or compute resources. Application code might include recent deployments or configuration changes. External dependencies might include third-party APIs or authentication services.
A good logic tree follows an important principle: the branches should be mutually exclusive and collectively exhaustive. Each branch represents a distinct category, and together they cover the full set of possibilities.
The goal is not to produce a perfect diagram. The goal is to organize thinking.
Once the possibilities are structured, a team can evaluate them one by one. Evidence can rule out some branches quickly. Others can be explored more deeply. The problem becomes clearer with each step.
This method is simple, but it changes how people approach complex situations. Instead of reacting to a problem, they begin to analyze it.
Over time, this habit leads to clearer discussions, better decisions, and faster problem solving.
Ken Watanabe describes this style of thinking in Problem Solving 101. The lesson is straightforward: when a problem feels complicated, start by organizing the possibilities.