What It Costs the New Hire When the Rules Live in Your Head

The cost of an undocumented operating doc, priced from the hire's side, and what that pricing changes about how you think about the worksheet.

Most posts about senior hiring price the cost from the founder's side. The salary. The ramp time. The opportunity cost on the founder's calendar.

I want to flip the angle today. There's a cost that almost never gets named, and it changes what the worksheet is actually doing.

It's the cost the new hire pays, in their first 90 days, when the decision-rules live in your head.

If you run a founder-led service firm, and you're about to bring a senior person in, sit with this for a minute. The cost from the hire's side is the cost that decides whether the hire stays. The cost from the founder's side is what you tell yourself you paid for after the hire leaves.

The four costs the new hire takes on in the first 90 days

When a senior hire walks into a firm where the rules live in the founder's head, four costs land on the hire from week one. The founder rarely sees any of them. Each one shows up as a small frustration on the hire's side, and a vague sense of "the new person isn't ramping fast enough" on the founder's.

(Quick context. My co-founder Jay and I both ran teams inside major global tech and telecom orgs before standing up Altvina. The kind of firms where senior hires walked into a written operating layer that someone else had built. When you watch senior hires land into firms where that layer doesn't yet exist, you start to see how much of the ramp-time problem comes from the missing document, not the person.)

The cost of guessing. Every undocumented decision the hire faces, they have two options: ask, or guess. Asking gets read by the founder as "not senior enough to decide." Guessing produces calls the founder would have made differently. Both options are losing options. The hire spends the first 30 days running a low-grade test on what the founder actually wants, in the absence of the document that would tell them. Capable senior people are very good at this. That's what makes the cost invisible. They are also slower than they would have been with a written rule. The slowness, from the founder's side, looks the same as being a less-capable hire.

Looking junior in front of clients. When the hire sits in a client call and a question lands in their stated scope, they have to make a call in real time without the rule. The two options are: defer to the founder ("let me check with the founder"), or make a call that may not match the founder's pattern. Deferring in front of the client signals to the client that the hire isn't actually the authority on that decision. The client learns to route around the hire to the founder. Making a call that doesn't match the founder's pattern produces a post-call correction. By week three, the hire has stopped trying to avoid it, because the rules they're being held to are unwritten and inconsistent. Either way, the hire's standing with the client erodes. That erosion comes from the missing document, not from the hire.

The cost of holding back. The smartest senior hires, after enough rounds of guessing wrong, stop volunteering decisions at all. They wait to be told. The founder reads this as "the hire isn't taking initiative," which produces a confirming pattern. The founder steps in more. The hire steps back more. Within 60 days, the firm has a senior person operating at maybe 40% of their actual capacity, because the trade-off on initiative has tipped against them. This is the cost most founders never name, because it looks like a hire-quality problem. It is a documented-rules problem with a hire-shaped cost.

The unspoken evaluation. A hire operating against unwritten rules is being evaluated against unspoken expectations. There is no 90-day metric they can target, because the metric lives in the founder's mood. There is no decision rubric they can self-assess against, because the rubric is "did the founder agree." This puts the hire in a setup where they cannot improve through clear feedback. They can only improve through the slow read of pattern. Senior people who can credibly do other roles in the market tend not to last in setups like this. They leave. The founder tells the next candidate "the last person didn't work out," when the real cause was an operating doc that didn't yet exist. (Adjacent data on the pattern: Gallup's 2024 employee-engagement benchmark shows only 46% of US workers strongly agree they know what is expected of them at work, down 10 points from March 2020. Heidrick & Struggles' executive failure data puts 40% of senior hires out within 18 months.)

Add the four together. The number isn't in dollars on the hire's side. It's in standing, momentum, and the rate at which they ramp to autonomy. From the founder's side, the same four costs translate directly into a hire who looks underwhelming for the first six months, leaves a few quarters in, and gets remembered as a misfire. The real cause was a document that took two to four hours to write.

The rationalization that keeps the rules in your head

There's a version of this conversation where the founder hears the case and rationalizes it.

"I'd rather they use their judgment. I don't want a document that boxes them in."

That sentence is doing a lot of work, and almost none of it is the work it claims.

It's true that documented rules can box in a senior hire if the rules are written too tightly, with too narrow a band of allowable exception, and held with too little flexibility. That version of the document does exist. It does produce the failure mode the rationalization is naming.

The version of the document we're talking about is not that version. It is a 2 to 4 page artifact with rule, exception, and escalation point for each major decision category. The exceptions are stated. The escalation points sit above the bands the hire can act in. The document does not box anyone in. It tells the hire where the band is, and trusts them to operate inside it.

The honest test, in our view, is one question. If the hire makes a decision today that you disagree with, can you point at a written rule that says "this is the rule, here is how it should have been applied"? If yes, you and the hire can have a calibration conversation against a shared reference. If no, the conversation collapses into "I'd have done it differently." The hire learns nothing they can use, because the rule wasn't written.

"I'd rather they use their judgment" is almost always cover for "I haven't written the rules yet, but I am going to evaluate against them anyway." That is the version that costs the hire most.

What changes when the rules are written before the hire starts

Spec work before the hire isn't a delay tactic. It's a 2 to 4 hour piece of focused writing. It changes the hire's first 90 days on four concrete dimensions.

The hire ramps to autonomy faster. A hire reading a written rule can apply it, calibrate it, and propose changes from a position of having operated against it. A hire reading "ask the founder" cannot. The first version produces a senior person who is making real decisions inside their charter by week three. The second produces a senior person who is still cc-ing you on every meaningful call in month four.

The hire's standing with clients gets built rather than eroded. Walking into a client call with a written rule means the hire can answer questions in their stated scope without deferring. Clients learn within the first two or three calls that this is a person whose calls they can rely on. That standing compounds. Without the written rule, the standing erodes equally fast in the other direction.

Calibration becomes a real conversation. When the rule exists, every hire-vs-founder disagreement becomes a productive calibration. "The rule says X, you applied X, the outcome was Y. Do we update the rule, or update the application?" That is a conversation a senior person can grow against. Without the rule, every disagreement collapses into "I would have done it differently," which is not a conversation. It is a verdict. The hire cannot improve against verdicts.

The hire's evaluation becomes honest. A 90-day check against named decisions and named outcomes is honest. A 90-day check against the founder's mood is not. The rules existing means the evaluation happens against the rules. The hire can target them. The hire either ramps cleanly, or it becomes clear early that the role is a real misfit. Both outcomes are useful. The version where the rules don't exist is the version where it takes nine months to find out which one you have.

Pricing this from the hire's side this week

You don't need to be in a hire process to run this exercise. You need an afternoon and one decision category.

Pick the category from the worksheet that you most often handle by judgment. For most founders, it's pricing exceptions or scope creep.

For that one category, write down the rule, the exception, and the escalation point. 60 minutes, in writing.

Then ask yourself, as if you were the new hire reading the document on day one: could you make the call in front of a client tomorrow without checking back? If yes, the rule is concrete enough. If no, the rule isn't yet a rule. It's a hint. The hire is going to face this in the first 30 days without enough surface to land on.

Run the exercise on one category. Then run it on the rest. Two to four hours of focused writing, ideally over a single afternoon, produces the document the hire actually inherits.

Founders don't tend to write the document because someone told them to slow down. They write it when they've sat with what the cost is on the hire's side. They write it once they've concluded that the discomfort of writing it down once is much smaller than the discomfort of two to three quarters of a senior person working against a moving target.

Closing

Tomorrow's post is the framework. The 8-row Decision-Rules format walked through one row at a time, with the carousel. If today's exercise produced a row that surprised you, the worksheet is the next step.

The thing I want to leave you with: the cost of writing the rules down is two to four hours of your time, once. The cost of not writing them down is paid by the hire, every week, for the first three quarters of their tenure. Most of it shows up on your side as "they didn't quite work out."

That math doesn't favor the founder who waits to see how the hire does first.

Continue the series

This is part 2 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
• Tuesday: What It Costs the New Hire When the Rules Live in Your Head (this post)
• 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.