The expensive hire who checks everything
You hired above your level on purpose. Fifteen years of experience, ran bigger things than yours, references that described exactly the independence you were missing. The plan was that this person would take a whole area off your desk.
Six months in, they are good. Genuinely good — the work is better and you are glad they are here. They also ask you about eleven things a week, and several of those are things you would have expected someone at their level to simply decide.
The story that forms is unfair and almost irresistible: maybe they are more cautious than they seemed, maybe the seniority did not travel. And it is worth noticing that the same story formed about the last two people, which makes it less a fact about individuals than a fact about the place they all arrived in.
Judgment is portable, context is not
Break a decision into its parts. There is the reasoning — how to weigh options, spot risk, sequence a plan — and that is what seniority buys, and it does transfer between businesses. Then there is the context the reasoning operates on, and that does not transfer at all.
Context is things like which clients receive exceptions and why, what margin a piece of work has to clear before it is worth taking, which of last year's shortcuts were fine and which caused nine months of pain, and what you will personally be upset about on a Friday. None of that is written anywhere. All of it is required to convert good general judgment into a correct specific decision.
So the senior hire's behaviour is not caution, it is competence. Deciding without context is how experienced people cause expensive damage, and they know that better than a junior would. The more senior the person, the more reliably they will check — which produces the counterintuitive result that hiring more seniority can increase how often you are consulted, at least at first.
There is a further turn to this. Enablement is not about trusting people first — it is about trusting your systems enough that people can succeed inside them. When the system holds no context, trusting the person is not a generous act, it is asking them to guess. Most founders in this position have already tried the generous version, said just make the call, and watched a good person hesitate anyway, because permission is not the missing input.
People do not become low-agency by nature, they become low-agency by design, by being placed in an environment that requires hesitation rather than action. A senior hire in a context-free business is that sentence demonstrated at high cost.
What the missing context costs
The first cost is that you paid for something you are not receiving. A senior salary buys independent decisions; if the decisions still route through you, you have bought excellent execution at a premium price and left the capability on the table.
The second cost is that it gets worse before it gets better, and most founders abandon it during that phase. A new senior person generates more questions initially than a junior would, because they are trying to build a model of the business rather than complete tasks. That is the correct behaviour and it looks exactly like the problem you hired them to solve.
The third is what it does to them. Capable people who cannot act at the level they are capable of get frustrated within about a year, and they do not usually say so — they leave. Then the context they had painstakingly assembled from six hundred small conversations leaves with them, and the next hire starts from zero.
The fourth is that it makes the diagnosis wrong in a way that repeats. If you read this as a hiring miss, the response is to hire differently next time, and the next person will do the same thing, because the environment is unchanged. That is not a hiring problem wearing a design costume; it is a design problem wearing a hiring costume, and it can absorb three or four expensive attempts before anyone reframes it.
Write down what good means here
The work is to externalize the context, and the good news is that you do not have to guess at what it consists of. The questions you are being asked are the specification. Every question is a piece of missing context announcing itself, with the priority already assigned by frequency.
So capture at the point of asking. When a decision comes to you, answer it and write down the rule behind the answer — not the answer, the rule. Not yes, discount that client, but we discount when the account is over a certain size and the relationship is over a year. One sentence, in a place people can find. Forty of those and a senior person can operate almost entirely independently.
Then be explicit about decision rights, because context without authority still routes upward. Name the decisions this person owns outright, the ones they should inform you about after the fact, and the small set that genuinely need you first. Most founders have never stated this, which means the default is to check everything — and the default is not a choice anyone made.
Make the cost of being wrong survivable and say so out loud. Independent decisions require a tolerance for some of them being suboptimal, and if every misstep is examined, a rational person will keep checking regardless of what the document says. The permission that matters is not permission to decide, it is permission to be occasionally wrong.
And give them the protocol for what to bring you. What is the real problem, what are three possible solutions, and which do they believe is best and why. That single change converts an escalation into a decision review — it takes you ninety seconds instead of fifteen minutes, it develops the person's judgment rather than substituting for it, and within a couple of months most of those conversations stop happening because the third question answers itself.
Enablement, and the honest offer
This is Enablement, and it is the pillar's central claim tested with the most expensive possible variable. Your culture is only as high-agency as the systems allow — and a business that has hired three senior people and still makes every call has run that experiment three times at considerable cost.
The reframe that actually helps: your job is not to be indispensable, it is to build something that does not depend on you. Hiring seniority is an attempt to buy your way out of dependency, and it does not work, because dependency is a property of the environment rather than of the people in it. Empowerment gives people ownership, education equips them for it, and environment supports it — a senior hire arrives with the capability for all three and finds none of them installed.
The honest offer: log every question you get asked for two weeks and write the rule behind each answer as you give it. That is free, it takes about ten extra minutes a day, and for many founders it is most of the fix — the list is shorter than you expect and it stops growing quickly.
The harder version is when the context genuinely cannot be written down because the decisions are not consistent — when the answer depends on your mood, the month, or facts nobody else can see. The OPERATE Report is a $1,997 diagnostic across all seven pillars, for the founder who has hired well twice and is still the only one deciding.
You bought judgment and the business never supplied context, so a competent person did the responsible thing and checked. The questions you get asked are the specification for what to write down.