BoardSnap is an iOS app that reads a problem tree whiteboard — trunk (core problem), roots (causes), and branches (effects) — and produces a structured cause-and-effect analysis in one snap.
Teams often try to solve problems before they've correctly identified them. A problem tree forces the discipline of defining the problem precisely before jumping to solutions. The trunk is the core problem. The roots are the causes that produce it. The branches are the effects that flow from it. The visual tree makes the causal logic undeniable — if you're solving a branch, you're treating a symptom; if you're solving a root, you're fixing the cause.
Draiwng a problem tree in a group also prevents premature solution convergence. When everyone can see the full causal chain, it's harder to leap to a solution that addresses only one root while ignoring the others. The tree forces completeness.
Problem trees are especially useful in complex domains — public health, organizational change, product strategy — where symptoms are visible and causes are hidden. Capturing the tree in a usable, shareable format is where teams consistently fall short. The tree on the board is the thinking. What gets documented is usually a flat summary that loses the causal structure.
Write one clear, specific problem statement in the center of the board. Not a solution in disguise ('we need more features') and not an absence ('we have no revenue'). A real problem: 'Customer churn is 8% monthly, above our 3% target.' Box it and label it 'Core Problem.'
Below the trunk, draw roots branching downward. Each root is a cause of the core problem. Write the cause at the end of each root line. Ask 'why?' for each cause to identify deeper roots. For each root, you can add sub-roots — second-level causes — branching further down.
Above the trunk, draw branches extending upward. Each branch is an effect of the core problem. Effects are the consequences if the problem is not solved. Add second-level effects — consequences of the consequences. These make the urgency of solving the problem visible.
Circle the two to three roots that are most directly causing the core problem and most actionable to address. These are the intervention points. Roots that are deep causes but outside your control get a different marker — important to understand, but not your immediate target.
If two roots are connected — one is a cause of the other, or they share a common driver — draw a dashed line between them. Cross-root connections are where systemic patterns live.
Open BoardSnap. The tree structure has a central trunk, roots below, branches above, and circled intervention roots. BoardSnap AI reads the hierarchical tree structure — trunk, first-level roots and branches, and deeper levels.
A structured problem analysis: core problem statement, a numbered list of causes (roots) with second-level causes indented, a numbered list of effects (branches) with second-level effects indented, and the circled intervention points flagged as recommended action areas. Cross-root connections are described as relationship notes. The output is a causal analysis document ready for a strategic planning or intervention design session.
The PM and customer success lead drew a problem tree with 'Support ticket volume is 3x industry average' as the trunk. Six roots, including 'unclear error messages,' 'missing documentation,' and 'onboarding doesn't cover edge cases.' Three branches as effects: customer frustration, CS team burnout, delayed feature work. BoardSnap's output became the brief for the support experience improvement project.
A non-profit ran a problem tree analysis with community stakeholders. The core problem was school dropout rates. The roots went four levels deep — the causal chain was complex and systemic. BoardSnap read all four levels of the tree structure and produced a causal analysis report that the NGO used to design a targeted intervention.
A fishbone diagram (Ishikawa) organizes causes into predefined categories (people, process, equipment, etc.) arranged as bones of a fish. A problem tree has free-form causes as roots and adds effects as branches — giving it both upstream and downstream analysis. Use a fishbone for process problems with categorical causes; use a problem tree for complex systemic problems that have both causes and effects to analyze.
Two to three levels is the practical limit on a whiteboard. Ask 'why?' three times for each root and you'll usually find the fundamental driver. More than three levels on a whiteboard becomes hard to read. Use the Five Whys technique for a dedicated deep-dive on any specific root.
Yes. Sticky notes are good for the initial brainstorm — write causes on one color and effects on another, then arrange them above and below the trunk. Connect them with lines in marker. BoardSnap reads sticky note content and its position (above trunk = effect, below trunk = cause) to assign the correct role.
Snap the board, ship the action items in ten seconds.