How to stop being the bottleneck with a one-page decision tree

Executive overview

Answering team questions consumes 10–20 hours a week for many small business owners. SOPs and how-tos don't fix this because the real problem isn't a lack of information — it's unclear ownership.

A decision tree is a one-page visual that maps who is responsible for what decision, so team members stop defaulting to asking you.

The core insight: unclear ownership, not missing information, is what keeps you in the inbox.

What a decision tree is and when to use one

• A series of branching questions that lead to a decision or outcome based on facts, not feelings
• Use one when the same decisions keep landing on your plate
• The goal: write down your existing decision logic so others can follow it without asking you
• Covers ownership of decisions — not task tracking or process steps

How to build one

• Pick a recurring decision area (e.g. email inbox ownership)
• Identify the first question you ask yourself when facing that decision
• Branch out from there based on the possible answers
• Assign a responsible person at each endpoint
• Color-code by department or role for fast scanning
• Build it in Whimsical, Canva, a whiteboard, or a spreadsheet — tool doesn't matter
• Test it yourself by walking through it as if you were the team member

Three common mistakes

1. Making it too optimistic — the tree must reflect how you actually decide, not how you wish things worked
2. Not holding people to it — if you keep stepping in despite the tree, your actions override the written rule and create confusion
3. Treating it as the only tool — decision trees solve ownership, but systemisation has four pillars

The four pillars of a systemised team

1. Seeing work — use task management principles
2. Tracking work — use communication best practices
3. Ownership — use decision trees
4. Practice — use SOPs, daily rituals, and policies

All four must work together. Decision trees are powerful only within their category.