Skip to main content

Flowcharts & processes

Decision tree template

A branching tree of questions that ends in clear outcomes. Free to use and edit in your browser — no account needed.

Decision tree template previewA branching tree of questions that ends in clear outcomes. Contains: Should we buy the team plan?, Budget over $10k?, Needed this quarter?, Start on the free plan, Buy the annual plan, Revisit next quarter, Review usage after 30 days, Yes, No, Yes, No.Budget over$10k?Needed thisquarter?Start on thefree planBuy theannual planRevisit nextquarterReview usageafter 30 daysShould we buy the team plan?YesNoYesNo
Preview of the decision tree template. On the board every shape, label and arrow is editable.

What is a decision tree?

A decision tree turns a fuzzy choice into a short series of questions. Each answer narrows the options until you land on an outcome. This template walks through whether to buy a software plan now, later or not at all — replace the questions with your own and the structure still holds.

When to use it

  • Making a repeatable call, such as which plan to buy or which support tier to offer.
  • Writing triage rules that anyone on a team can follow consistently.
  • Teaching a diagnostic process step by step.

How to make a decision tree in SketchFlow

  1. Step 1: Open the template in SketchFlow.
  2. Step 2: Write your first question in the top diamond — the one that splits the options most.
  3. Step 3: Rewrite the follow-up question and the outcome boxes at the ends of each branch.
  4. Step 4: Extend a branch by duplicating a diamond (Ctrl/Cmd+D) and joining it with an arrow (A).
  5. Step 5: Export the tree as PNG or SVG to share with your team.

Tips for a better result

  • Put the question that eliminates the most options at the top.
  • Make every leaf an action someone can take, not another question.
  • If a tree grows past four levels, split it into two linked trees.

Questions about this template

What is the difference between a decision tree and a flowchart?

A flowchart describes a process in order, including loops. A decision tree only branches: each question splits the path, and every branch ends in an outcome.

Can I use more than yes/no answers?

Yes. Draw one arrow per answer from the diamond and label each one, for example Under $1k, $1k to $10k and Over $10k.

How do I keep a big decision tree readable?

Use frames to group related branches and keep consistent spacing. Ctrl/Cmd+0 fits the whole tree on screen while you work.