BizThinkFrame
← Back to frameworks
Structure a problem

Logic tree

Break a broad question into explicit branches so you can examine its parts and decide what to investigate next.

When to use it

Use a logic tree when a question has several parts that need to be organized. A tree used to break down a problem is often called an issue tree. Keep a tree about causes separate from one about possible solutions.

What to bring

One clear question, a basis for dividing it into branches, and evidence or open questions for each branch.

What you will have

A structured investigation with defined branches, visible gaps, and specific checks for the next level of detail.

How to use it

  1. Write one clear question at the root.
  2. Choose a consistent way to divide the question into branches.
  3. Check branches at the same level for overlap and comparable detail.
  4. Break down a branch where doing so leads to a useful investigation. Attach evidence and unresolved questions.
  5. Choose a next check based on the evidence and the importance of the branch.

Keep its limits in mind

The shape of a tree does not establish causation or completeness. Check for overlap, missing branches, and changes in the question being answered.

Fictional teaching example

Organizing an investigation into late orders

A fictional store promised to dispatch 100 orders in a week. Twenty missed their promised date. Each late order is assigned to its first recorded blocker, so the counts below assign each order once.

Central questionWhat blocked the 20 late orders?Branch level 1Stock confirmation incompleteBranch level 28 ordersBranch level 1Address clarification requiredBranch level 25 ordersBranch level 1Different interpretations of the order cutoffBranch level 24 ordersBranch level 1Carrier pickup changedBranch level 23 ordersEvidence and next checksOrder logs, stock lookup records, address fields, customermessages, timestamps, and carrier notices form the practiceevidence. The first-blocker classification does not imply thateach order had only one cause.

On a small screen, scroll across the diagram to read it.

Stock confirmation: 8 orders — inspect stock records and lookup timing.

Address clarification: 5 orders — inspect address fields and customer messages.

Order cutoff: 4 orders — compare page wording and timestamps.

Carrier pickup: 3 orders — inspect handover records and the carrier notice.

Next step: Stock confirmation affects the most orders in this case, making it a possible starting point. Urgency and impact may justify choosing another branch first.

Check your work

  • All branches answer the same parent question.
  • Categories and their counts use an explicit classification rule.
  • Cause branches and proposed actions are not mixed together.
  • Leaf nodes lead to observable checks or clearly identified unknowns.

Put the method to work

Use this framework in the English Workspace with early access. Local generation copies clearly labeled fields; you can edit the diagram afterwards.

Open in Workspace

Practice with an example

Compare 5 Whys and issue trees using the same late-order evidence, then plan your next investigation.

5 Whys vs issue trees for investigating a problem →