Prioritize branches by impact and workability before diving in

The tree shows what is possible to analyze — decide which branches are worth investigating before spending time on them.

Why it works

A complete issue tree has more branches than can be fully analyzed with available resources. Prioritizing by impact (how much does this branch matter if the hypothesis is true?) and workability (how addressable is this if it turns out to be a driver?) converts the tree from a map of the problem space into an action plan. The alternative — following branches to completion in the order they appear — is a common source of analytical work that produces interesting insights irrelevant to the decision at hand.

How to do it

1. After building the full tree, mark each branch with an estimated impact if it turns out to be a significant driver (high/medium/low).
2. Mark each branch with workability: how much can you actually change this?
3. Start with high-impact, high-workability branches and work down.
4. Explicitly deprioritize low-impact branches — write "not analyzing this" in the tree so the decision is visible.

Evidence

Prioritization within structured analysis is a standard management consulting practice, taught explicitly in strategy training at major firms. Its value is efficiency: equal attention to all branches produces diminishing returns. No direct experimental evidence exists. (anecdotal)

Impact and workability are estimates, and a branch dismissed as low-impact may turn out to be the actual driver. Periodic review of deprioritized branches is warranted.

Common mistake

Analyzing the branches you know how to analyze rather than the ones most likely to contain the key driver — this is the streetlight effect applied to structured analysis.