TextTree

What is a logic tree?

A logic tree breaks one big problem down into smaller elements by branching it out without missing anything or overlapping (MECE — Mutually Exclusive, Collectively Exhaustive).

• Put the “problem you want to solve” at the top
• Below it, lay out the elements that make up the problem, split into 3–4 branches
• Break each of those elements down one more level below that

Two variants are common: a “why tree” that breaks down causes, and a “how tree” that breaks down solutions. The demo above is a why tree — it breaks the problem “Revenue isn’t growing” into three candidate causes, then drills each one down into concrete factors.

Where this works well

• When you want to break a big goal down into actionable initiatives or tasks
• When you want to untangle a problem where the causes are complex and interconnected and can’t be narrowed to just one
• When you want a team to align on how they’re framing a problem

How to build it in ThinkTray

Step 1: Write the problem on a single card at the top

Use the Card tool (R) to write the problem you want to break down on a card.

• Aim for a level of detail that isn’t too abstract, but also isn’t narrowed down too soon
• Example: “Profit isn’t growing”

Step 2: Lay out the elements directly below

Directly below the problem, line up 3–4 cards for the elements that make it up.

• Rather than freezing up trying to be perfectly MECE, it’s smoother to get whatever elements come to mind out first and rearrange them afterward
• Example: “New customers aren’t increasing” / “Existing-customer retention is low” / “Customer spend isn’t rising”

Step 3: Connect them with the Line tool

Use the Line tool (L) to draw arrows from the cards above down to the cards below.

• Always drawing arrows in the same direction, parent to child, keeps the diagram readable

Step 4: Break it down one more level

Add two more cards under each element, going one level deeper into concrete factors.

• Aim for around 3 levels of depth — going deeper than that makes it hard to see the whole picture
• Example: “New customers aren’t increasing” → “Low awareness” / “Low conversion rate from inquiries”

Step 5: Color-code each branch (advanced)

Giving cards in the same branch the same color makes it obvious at a glance which element connects to which problem.

• You can change the fill and border color from the context toolbar when a card is selected
• The demo above color-codes its three branches this way too

Fact-finding comes after the breakdown

The elements you branch out in a logic tree are still just a hypothesis. The shape tends to look similar for any business, but what fills it in differs from company to company.

Fact-finding is what confirms or overturns the hypothesis. Keep verifying by adding “facts we already know” and “insights from data” to each node.

• Example: “Low awareness — not well known” → What awareness activities are actually happening right now, and can their effect be measured?

Building up facts this way also feeds into strategy building through SWOT analysis.

Tips

• Keep each level at the same granularity — Mixing big and small elements within one level breaks down the tree’s overall structure.
• Don’t over-obsess about MECE — Aiming for a perfect breakdown from the start will freeze you up. It goes faster to get things out first and organize afterward.
• Aim for about 3 levels — Breaking things down too deep makes you lose sight of the big picture.
• Summarize conclusions and next actions in text — The diagram is a “map of the breakdown.” Write the conclusions and next actions you derive from it into a .txt file in the same folder.

Logic trees are widely used in consulting practice; there’s no single, clearly attributed inventor.