A decision tree turns a judgment call into a repeatable process anyone can follow. This one walks through whether to build a requested feature, but the shape works for anything: support triage, approvals, eligibility checks. Each question lists its answers, and each answer points to the next question or an outcome.
*hideKeys
[ask *vertical] Do customers ask for it?
- Yes ->[core]
- No ->[cost]
[core *vertical] Is it in our core market?
- Yes ->[build]
- No ->[ideas]
[cost *vertical] Will it cut support costs?
- Yes ->[small]
- No ->[decline]
{*vertical} Outcomes
- [build *bold] Build it next quarter
- [small] Scope a small version
- [ideas *dashed] Add to the ideas list
- [decline *dashed] Decline for now
- Yes ->[core].[newq *vertical] Your question, and pointing an answer at it.The full syntax is in the guide.