Product feature prioritization
Who uses it: Product manager deciding which features to build next sprint
Is it on the roadmap?
├─ No → Does it unblock a key customer? → Yes: add to backlog / No: decline
└─ Yes → Does it have a spec? → No: return to design
└─ Yes → Estimated effort < 3 days? → Yes: schedule / No: break it down
Why this works: The tree enforces a consistent gate for feature requests. The 'unblock a key customer' branch captures high-priority exceptions without making them the default.
Customer support triage
Who uses it: Support team standardizing first-response paths
Is the account active?
├─ No → Send reactivation link → resolved
└─ Yes → Is the issue a known bug?
├─ Yes → Link to workaround → escalate if critical
└─ No → Reproduce the issue → file ticket or close
Why this works: Documenting the triage flow as a tree reduced average handle time by giving agents a clear path instead of relying on tribal knowledge.
Hiring decision framework
Who uses it: Hiring manager aligning a panel on candidate evaluation
Does the candidate meet the must-have requirements?
├─ No → Reject
└─ Yes → Strong culture fit?
├─ No → Hold (re-evaluate with team)
└─ Yes → Reference check passed?
├─ No → Reject
└─ Yes → Extend offer
Why this works: The tree makes the hiring criteria explicit and reduces inconsistency between panel members — everyone follows the same branch logic.
Infrastructure incident response
Who uses it: On-call engineer following a runbook during an outage
Is the service responding?
├─ Yes → Are error rates elevated?
│ ├─ No → Monitor for 10 min
│ └─ Yes → Check recent deploys → rollback if needed
└─ No → Check health endpoint → restart pod or escalate
Why this works: A decision tree runbook reduces decision fatigue during high-stress incidents — the engineer follows the path instead of improvising.
Personal finance decision
Who uses it: Student or young professional deciding how to use a windfall
Do you have high-interest debt (>7%)?
├─ Yes → Pay it off first
└─ No → Do you have 3-month emergency fund?
├─ No → Build emergency fund
└─ Yes → Invest in index fund or retirement account
Why this works: Simple trees work well for personal decisions too. The structure makes the priority order clear and prevents decision paralysis.
Content publishing approval
Who uses it: Marketing team standardizing a content review process
Is the content factually accurate?
├─ No → Return to writer
└─ Yes → Does it meet brand guidelines?
├─ No → Request edits
└─ Yes → Legal review needed?
├─ Yes → Send to legal → publish after approval
└─ No → Publish
Why this works: The tree turns a vague 'get sign-off' process into explicit checkpoints. Teams can see exactly where a piece of content is stuck.
