The Founder's Decision Tree is a one-page map of a single recurring decision — what triggers it, what you look at, what you weigh, and what you choose — drawn so that someone else could walk it without you. The value is not in the drawing. It is in the test: hand the tree to a capable person on your team and watch where they stop. Every stop is a place where your judgment still lives in your head instead of your architecture.
Key takeaways
- Choose one decision you personally make every week; repetition is what gives you enough material to draw an honest tree.
- Map four branches — trigger, information, criteria, outcome — before you try to improve any of them.
- The portability test, not the drawing, produces the value: the stalls reveal undocumented judgment.
- Convert each gap into exactly one artifact: an encoded decision right, a self-serve context source, or a written standard.
Why recurring decisions are the honest audit
Founders document the big things. Strategy, values, the org chart, the quarterly plan. Those documents are rarely the problem. The decisions that actually keep an organization dependent on one person are small, repeated, and unremarkable: approving a discount, choosing which feature request jumps the queue, signing off on a contractor, waving through an exception.
You have made each of those so many times that the reasoning has collapsed into instinct. Instinct is the one asset you cannot hand over. A weekly decision gives you what a quarterly one cannot — enough repetitions that the real pattern is visible, and enough cost that being the bottleneck actually hurts.
The four branches
1. Trigger. What event starts this decision? Write it as a condition, not a feeling. Not 'when something seems off,' but 'when a rep asks to go below the published band,' or 'when a customer requests a feature that is not on the roadmap.' A trigger someone else cannot recognize is not a trigger. It is a mood.
2. Information. What do you actually look at before you decide? Be honest here. If the answer includes the customer's tone, the account's history, or your read of the room, name those things — they are data, and they can be taught.
3. Criteria. What do you weigh, and in what order? The order matters more than the list. Most founders can produce three criteria in a minute and cannot say which one wins when two of them conflict. That silence is where the decision quietly stays yours.
4. Outcome. What do you choose, and where does the choice get recorded? An outcome that lives only in your memory creates no precedent. It creates a queue.
Most founders fill in the outcome branch in thirty seconds and get stuck on criteria. That stuck point is the finding, not a detour.
The tree at a glance
| Branch | What it captures | What it should become |
|---|---|---|
| Trigger | The event that starts the decision | A written standard for what escalates and what does not |
| Information | What you review before deciding | A self-serve context source the team can read without you |
| Criteria | What you weigh, and in what order | An encoded decision right with a clear boundary |
| Outcome | What you choose and how it is recorded | A documented precedent that survives your absence |
The portability test
Hand the finished tree to someone capable and give them nothing else. No explanation, no context, no phone call. Ask them to make the next three calls using only the page.
Then ask two questions: where did you stop, and what did you have to ask me?
Their answers will sort into three buckets. They stopped because they did not have information. They stopped because they did not have authority. Or they stopped because they did not know which criterion outranked the others. Those three buckets map directly onto the three artifacts below.
Converting gaps into architecture
Encoded decision rights. A decision right says who may decide, inside what boundary, without escalating. Anyone on the accounts team may approve a discount inside the published band; anything outside it goes to the deal owner. The boundary is the work. A decision right without a boundary is just permission, and permission without a limit always comes back to you.
Self-serve context sources. This is your information branch, made readable. A pricing history, a decision log, a short record of why the last exception was granted. The test is simple: can someone answer the question without interrupting you?
Written standards. This is your criteria branch with the ranking made explicit. What wins when margin and precedent conflict. What counts as urgent versus merely loud.
The discipline is one gap, one artifact. Do not build a wiki. Build the three things that stop the three stalls.
A worked example: approving discounts
The trigger: a rep asks to go below the published band. The information: the deal's size relative to the band, whether the objection is price or budget timing, the account's history, and what the customer has already agreed to. The criteria: does this discount protect margin at the scale we are actually selling, does it set a precedent the team will have to honor next quarter, and does it change how this customer behaves at renewal. The outcome: approve, counter, or decline — recorded where the next person can find it.
Now the test. Give that tree to a rep and watch where they stop. They usually stop at criteria: they do not know which of the three outranks the others, so they ask you. That stall becomes a written standard with an order. The second stall: they do not know what happened the last several times someone asked, so they ask you. That becomes a self-serve context source. The third: they are not certain they are allowed to say yes at all, so they ask you. That becomes a decision right with a boundary.
Three stalls, three artifacts, one working session. The next request does not climb the tree to your office.
Doing this across the whole organization
One tree is a demonstration. The same pattern repeats through hiring, prioritization, spend, escalations, and partnerships — dozens of weekly decisions, each holding a small piece of your judgment hostage.
EXIUSS Intelligence is built for that scale. The 14-day free trial runs a guided discovery journey and produces a personalized EXIUSS Protocol that surfaces the patterns, dependencies, and blind spots in how your organization currently decides — including the decisions that still route through you. You draw on 95+ Founder Frameworks and the 10 Universal Laws to convert each branch into a decision right, a context source, or a written standard, and you build it in the Workspace: funnels, CRM, pipeline, and your first initiatives, standing up in the trial rather than in a someday plan.
What the trial does not do is think for you. It gives you the architecture and the place to build it. Everything you build carries over if you upgrade — nothing gets rebuilt. The paid tier adds real-time voice conversation with the intelligence system, grounded in your own architecture, and removes the trial limits.
Start with one tree. Then stop being the tree.
Quick checklist
- Pick one decision you personally make every week and write it at the top of a page.
- Fill in the trigger as a condition someone else could recognize without asking you.
- List every input you actually review, including the informal ones like tone and history.
- Rank your criteria and name which one wins when two of them conflict.
- Hand the tree to someone capable, stay silent, and record where they stop.
- Convert each stall into one artifact: a decision right, a context source, or a written standard.