When Founder-Judgment Becomes a Routing Tax

A practical look at the moment a senior hire stops being a capacity problem and starts being a documentation problem, and the one artifact that changes that.

You've passed the readiness gate. The role is named. The cost is priced. The calendar is blocked. The next move, in the founder-led firms we tend to see, is the one almost nobody schedules.

You sit down on a Friday afternoon. You write down the decisions the new hire is going to inherit.

Not the job description. Not the strategic plan. Not the org chart. The actual decisions. Pricing exceptions, scope creep, client escalations, refund authority, hiring authority, vendor selection, project sequencing, quality bar. Eight categories, or close to it, depending on the firm. For each one: the rule you currently apply, the exception, and the point above which it escalates to you.

Most founders skip this work. The hire shows up two months later. They walk into a firm where the rules live in the founder's head. The founder is then surprised when the hire either kicks decisions back or makes calls the founder would have made differently.

That's not a hire problem. It's a documentation problem wearing hire-problem clothes.

If your firm is founder-led and the next hire is in motion or about to be, this week is about the artifact that closes that gap. We call it the Decision-Rules Document. It is the piece of a role-spec that makes the hire actually hireable.

When founder-judgment becomes a routing tax

For most of a founder's run at a founder-led firm, the fact that decisions live in the founder's head is fine. It is, in fact, often what makes the firm's work distinctive. The founder's taste is the brand. The founder's judgment is the quality bar. Senior staff and clients both rely on it, and the firm ships work that reflects it.

That works until the firm grows past the size where one person's head can hold all the rules.

The shift, when it happens, doesn't announce itself. The first sign is usually a senior person on the team starting to cc the founder on more decisions than they used to. Then a client asking, on a call where the senior person is supposed to be running point, "what does Sam think?" or "is the founder going to weigh in?" Then the new hire from six months ago, the one who looked great in interviews, holding back on a decision because they're not sure where the line is.

(Quick context for what's about to follow. My co-founder Katie and I both spent years inside major global tech and telecom orgs before standing up Altvina. In those firms, the decision-rules layer was institutional. It lived in playbooks, in policies, in the way senior people had been shaped by years of watching others apply the rules. When you start a smaller firm from scratch, none of that exists yet. The founder is, by default, the entire decision-rules layer. That's normal. The trap is leaving it that way past the point where the firm grows out of it.)

Each of those moments is the same pattern. A decision needs to be made. The rule for making it isn't written down. The path the firm has learned to use is "ask the founder." The senior person isn't being timid. The client isn't being difficult. The new hire isn't being passive. They are all doing the rational thing in a firm where the rules are unwritten. They are checking with the person who has them.

The cost of that pattern is not the time spent on each individual check-in. The cost is what the firm becomes shaped around. Every senior staff member learns that the safer path is to defer. Every client learns that the founder is the actual authority on every meaningful decision. Every new hire learns that "ask the founder" is the cultural default. Over the first six to twelve months of any senior hire's tenure, the firm hardens into a shape where the founder is the routing hub for everything, no matter what the org chart says.

That's what we mean by founder-judgment becoming a routing tax. The founder's taste was an asset. The absence of any other place for it to live becomes a tax on every decision the firm makes.

Why the next hire makes this visible

The moment a senior hire walks in is the moment the routing tax becomes legible to the founder.

Before the hire, the routing pattern is just how the firm works. The founder doesn't notice it because the founder is the constant in every loop. After the hire, the pattern shows up as a series of small frictions. The hire asks a question the founder thinks should be obvious. The hire makes a call the founder would have made differently. The hire stops bringing up a category of decision at all because the signal in week two was "I'll handle that." Each one feels like a hire-quality problem in the moment. None of them are.

What's actually happening is that the senior hire is reading the firm honestly and discovering that the rules live in the founder's head. They have two options. Ask, which the founder reads as not being senior enough to decide. Or guess, which the founder reads as making bad calls. Both options are losing options, and neither is the hire's fault.

The hire is not being evaluated against a written role. They are being evaluated against the founder's unspoken expectations of what the role should be. That is a job nobody can pass.

The artifact that closes the gap

The fix, as far as we've seen, is structurally simple. It is also the thing founder-led firms in this size band most often skip until they've blamed a hire or two for being unable to operate against rules that were never written down.

You write the rules down. Once. Before the hire starts. In a document the hire reads in week one and operates from in week two.

This is the Decision-Rules Document. At minimum, it contains:

• The eight or so categories of decision the hire will own (or partly own).
• For each category: the rule you currently apply, in plain language. The exception. The point above which the call comes back to you.

It is two to four pages. It takes two to four hours of focused writing to produce. It is the difference between a hire who ramps to autonomy by month three and a hire who is still cc-ing you on every meaningful decision in month nine.

The reason firms skip it isn't lack of time. It's that the document is uncomfortable to write. Naming a refund threshold means committing to a number. Naming a quality bar means turning taste into clear criteria. Naming an escalation trigger means naming, in writing, the cases you don't trust the hire on, before they've even started. Each of these feels somehow rude or premature.

It is none of those things. The discomfort of writing it down once, before the hire starts, is much smaller than the discomfort of two to three quarters of a senior person working against a moving target.

Three signals to run before any role goes live

Not theory. Three concrete signals you can run on your firm this week, before the offer goes out.

1. The rules-in-your-head test. Pick one decision category from the list above. Pricing exceptions is a common starting point. Spend 15 minutes trying to write the rule, the exception, and the escalation point on paper. If you finish, that category is closer to ready than not. If you stall, the rule is judgment-only, and the hire is going to flounder there. Then sit with the eight categories from the worksheet and star every other category where the honest answer is some version of "depends" or "I decide each one." Stars aren't failures. They're the categories the hire is going to need the most help with on day one.
2. The cc-the-founder count. Look at the last 14 days of email. Count the threads that include a senior person and you, where the senior person is asking a question that, in a documented firm, they would have decided. The count is your current routing-tax baseline. Then listen on the next two client calls where a senior person is running point. Count the number of times the client (or the senior person) defers to you in front of the client on a question inside the senior person's stated scope. Once is normal. Three times in two calls is structural.
3. The role you almost wrote. If you have a draft job description for the next hire sitting in a doc somewhere, read it. Count the times it leans on the words "support," "help with," "judgment," "as needed," or "manage." Each one of those words is a place the role-spec is hiding the missing decision-rule.

If two or more of these come back loud, the next move isn't the search. It is the worksheet. Two to four hours of writing, before the offer goes out.

What's coming this week

Tomorrow's post walks the cost piece. What it actually costs the new hire when the rules live in your head. The math runs differently when you price the cost from the hire's side instead of the founder's.

Wednesday is the framework piece. The 8-row Decision-Rules format walked through one row at a time, with the carousel that goes with it.

Thursday is the blueprint angle. What a Decision-Rules Document actually looks like in a firm that has done the work, with concrete examples for the eight categories.

Friday closes the week with the most expensive non-handoff in fractional firms. The "trust your judgment" framing, and why it produces capable senior people who never quite become autonomous.

The point of this week isn't to make hiring feel harder. It's to make the post-hire experience meaningfully better. You do that by writing the artifact that turns founder-judgment from a routing tax into a documented surface the hire can land on.

Continue the series

This is part 1 of a 5-part series on The Decision-Rules Document Your Next Hire Should Inherit. The full arc:

• Monday: When Founder-Judgment Becomes a Routing Tax (this post)
• Tuesday: What It Costs the New Hire When the Rules Live in Your Head
• Wednesday: The 8-Row Decision-Rules Format
• Thursday: What a Decision-Rules Document Actually Looks Like
• Friday: Why "Trust Your Judgment" Is a Non-Handoff

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.