
Not every decision is yours to make. Root, Trunk, Branch, Leaf, and who actually decides.
In most founder-led companies, every decision routes through one person: the founder. It feels like control. It's actually the biggest bottleneck. Rocket Routine OS classifies every decision by its impact across four levels, Root, Trunk, Branch, Leaf, and sets who actually decides.
Most founder-led companies share the same bottleneck, and it has a name: you.
Every decision crosses your desk. Whether to enter a new market and what color the button in the newsletter should be both land in the same place.
It feels like control. It's closer to the opposite. When every decision passes through the same point, every decision carries the same weight, which means the most important one gets exactly as little attention as the least important. The problem isn't that you control too much. The problem is that nobody ever defined which decisions are actually yours.
The bottleneck isn't volume
You might think the problem is the sheer number of decisions. It isn't. The problem is that they all sit on the same pile, unsorted.
An existential decision and a routine decision look identical on a to-do list. Both are a line item, both are waiting, both need a yes or a no. But they are not the same. One can reshape the company; the other is forgotten by tomorrow. As long as they're treated the same, the routine eats the time that belongs to the existential one.
A company doesn't slow down because too many decisions are pending. It slows down because nobody sorted which decision belongs at which level.
Four levels, one tree
Rocket Routine OS classifies every decision by its impact, not by whoever happens to be available. The picture for it is a tree with four levels:
- Root. Existential decisions. They determine whether and in what form the company exists at all: business model, financing, ownership. The CEO and/or owners decide here, and nobody else.
- Trunk. Structural decisions. They change how the company is built: organization, major investments, entering a new market. This belongs to the senior team.
- Branch. Operational decisions. They govern how a single domain runs, and they sit with the domain leads who hold the context.
- Leaf. Routine decisions with clear, predefined boundaries. They sit with the AI operators, who decide within their Role Contract.
The level comes from the impact of the decision, not from the rank of whoever makes it. A decision isn't Root because you make it. It's Root because it's existential.
A decision at the wrong altitude
Decisions rarely fail because they're hard. They fail because they're made at the wrong altitude.
A Leaf decision that lands on the CEO is just as misplaced as a Root decision made by an operator. In the first case, you spend your judgment on something that doesn't need it. In the second, someone without the context makes a call that affects the whole company. It's the same mistake running in two directions: the decision isn't sitting at its level.
This is also exactly where the classification becomes the precondition for AI operators to work safely at all. An operator gets Leaf decisions, and only those. The boundaries live in the Role Contract; anything above them escalates. That keeps the Root at the top and leaves CEO sovereignty untouched. Delegation here isn't a loss of control. It's what finally puts your control where it counts.
Delegating isn't giving up control. It's putting it where it changes something.
Company 0
At Rocket Routine, every published piece used to route through me. Blog, LinkedIn, X, newsletter, more than twenty assets a week, and I was the approval gate on every single one. I considered that my job.
When I sorted one week of my own decisions into Root, Trunk, Branch, and Leaf, approving each individual post was clearly a Leaf decision. Routine, with clear boundaries, repeated every day. I had been holding a leaf at the root.
What is actually my decision sits one level up. Not the approval of the individual post, but the line: do we keep building in public, does the language stay free of buzzwords, does this positioning still belong to us. That's Root. The approval itself now runs through the content operator, within its Role Contract, with a quality check in front of it. I decide the line. The operator decides the individual post.
What comes next
Rocket Routine OS classifies every decision by its impact, across four levels: Root (existential, CEO and/or owners), Trunk (structural, senior team), Branch (operational, domain leads), Leaf (routine, AI operators within the Role Contract). Not every decision is yours to make. The task isn't to decide more, it's to put every decision where it belongs.
If you're running a founder-led B2B company with 15 to 50 employees and you want measurable execution control without spending your judgment on routine: rocket-routine.com