Decision tree: one question at a time, to a clear answer

A guide that asks one question at a time and ends on a clear answer, for staff or customers.

Live example

The example: Which permit a home project needs in Thistle Bend, a made-up town

Twelve questions, sixteen endings, an outline below

Which permit a home project needs in Thistle Bend, a made-up town

Open the exampleThe names and numbers are made up.

What to notice

  • No path is longer than four questions, and replacing a water heater takes two.
  • Each ending that needs a permit gives the cost, the wait and what to bring. A building permit is $120 plus $6 per $1,000 of work, with a $9,000 job worked out as $174.
  • The outline underneath holds all 12 questions and 16 endings, and marks the answers picked so far.

The prompt that starts one like it

Make an interactive decision tree as a single HTML page that answers [the question people keep asking]. Here are the rules: [paste them]. Ask one question at a time, with a button for each answer. End on a clear result that says what to do next and why. Show the answers so far, with a way to go back a step or start over. Underneath, print the whole tree as a plain outline. It must work on a phone and with a keyboard. Then publish it on sharable.link.

A permit desk hears the same question all week, and the answer depends on three or four facts the caller hasn't mentioned yet. A decision tree asks for those facts one at a time and ends on an answer. Thistle Bend and its permit rules are invented, so don't plan a real shed by them. Yours go in through the prompt.

Who it's for

An operations or support lead whose team answers one rule-bound question again and again: can this order be returned, which plan covers this, who approves this expense. Send it to staff as their reference, or put the link where customers ask.

It works when the rules are settled and each question has a few fixed answers. It doesn't suit judgment calls, and it shouldn't stand in for legal or medical advice. The page keeps nothing, so it can't tell you which answers people chose or where they gave up.

What a good one contains

  • A first question about the visitor's situation. "What are you planning?" has four everyday answers. Nobody arrives knowing a zoning certificate from a building permit.
  • Questions with the threshold inside them. "Will the shed be bigger than 120 square feet?" can be settled with a tape measure.
  • Short paths. The longest route is four questions. A new water heater takes two.
  • Endings that say what to do. Each names the permit, the fee, the wait and what to bring. "You don't need a permit" is an ending too, with the conditions that keep it true.
  • A way back. The answers so far sit above the question as buttons that reopen it, with "Back one question" and "Start over" below.
  • The whole tree in plain text. An outline lists every question and ending. Colleagues can check a rule without clicking, and it's the part worth printing.
  • A date, a source and a fallback. "Rules as of January 1, 2027, from chapter 14 of the town code" says how far to trust it. Odd cases are sent to the permit desk.

Walk every branch before it goes out

A tree fails at the edges of its questions. A deck of exactly 200 square feet has to land on one side, so the sample writes the boundary into the buttons: "Yes, bigger" and "No, 200 or smaller".

Then click every path from start to finish. Sixteen endings take about ten minutes. Hand three common cases to someone who doesn't know the rules and watch where they hesitate. That question needs rewording.

When a rule changes, change the page and its date in the conversation where you made it. The saved link keeps working, which matters once it's on a counter sign.

How to send it

As an open link. A guide like this gets linked from a website, an email signature or a sign on the counter. The rules in it are public already, so nothing in it needs locking.

Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.

Make yours in Claude

Add the connector once, then publish from any Claude conversation and get a link to send.

Add Claude Connector

Already have the file? Upload it here.

More in strategy and finance

  • Business plan: A one-page plan an owner sends to a bank, a landlord or a partner ahead of the full version.
  • SWOT analysis: Strengths, weaknesses, opportunities and threats for one organization, each backed by evidence.
  • Gantt chart: One project's tasks as bars across weeks, with owners, milestones and a line for today.
  • Executive summary: One screen that tells executives what a longer report found and what they're being asked to decide.
  • Timeline: Dated events in order, for a history people will enjoy or a project they have to follow.
  • Org chart: Who reports to whom in a small company, with teams, open roles and what each person looks after.
  • All use cases

Keep reading