You brought in a seasoned operator to carry the load, and by month three he's parked at your door for every call. Refund approvals and renewal decisions he was hired to own still route back through you. The operating model that tells everyone how your company runs has never left your head, so your expensive new hire is spending his first 90 days interviewing you to reverse-engineer it. This issue is about getting that model on the page before the next hire starts.

Hampton co-founder Joe Speiser had three roles budgeted: a data engineer, an ops manager, a PM. $440K. He installed Viktor on April 12. Forty-four days later, none are on the calendar, and 18 of his team work with Viktor daily. His VP: we are editors now, not creators.

Get Started for Free

Marcus has run operations bigger than your whole company. That was the point of hiring him.

He came in with 15 years behind him, a resume that settled your board and references who kept reaching for the word "unflappable." You hired him to carry the operational weight so you could climb out of the daily scramble and get back to the work only you can do. For about a week, it felt like the smartest money you had ever spent.

It's the back half of month three now, and Marcus can't seem to move without you. He catches you in the hallway to ask whether he can approve a refund. He schedules a 30-minute meeting to find out how you want a mid-tier renewal handled. Your phone lights up with his name while you're at dinner, and it's another question you could have answered in your sleep. The unflappable guy from the interviews looks tired, and a little smaller, and you are starting to wonder what you missed.

You won't say it out loud yet, but you've started running the numbers on whether this was a mistake.

You remember the salary. You remember telling your co-founder this was the hire that would finally give you your Thursdays back. You remember the relief.

And now you're in a one-on-one watching a seasoned operator wait for you to make a call he was brought in to own, and a cold little thought slides in: maybe he's not who the resume said he was. Right behind it comes the worse one, the one that keeps you up. Maybe the problem is you. Maybe you're the kind of founder who can't be helped, who will be standing in the middle of everything until the day the company dies or you do.

That thought is wrong.

The founder reaches for the same explanation when a hire like this goes sideways: wrong person. It's the only read you can get from where you're standing.

The firm Leadership IQ ran a three-year study of more than 20,000 new hires and found that 46% of them failed inside 18 months. The researchers went digging into why. Of those failures, 89% traced to attitude and fit: coachability, emotional intelligence, motivation, temperament. Only 11% came down to a shortage of technical skill. The people doing the hiring had screened hard for competence and gotten blindsided by everything it doesn't cover.

Read that against Marcus and the dread eases. You judged his ability right. He has the reps, the scars, the track record your board checked twice, but he's stuck on something that has nothing to do with whether he's good at the work, because he was never handed the one thing on which the job runs.

Every growing company has an operating model. It's the accumulated set of judgments that tells everyone how this specific place works: who signs off on what, why the enterprise accounts get handled with kid gloves, why you price the way you do, what a person is allowed to decide on their own and what has to come to you. In most companies at your stage, that model has never been written down anywhere. It lives in one head. You are the manual.

The philosopher Michael Polanyi had a line for this all the way back in 1966: "We can know more than we can tell." He pointed at how you can pick one face out of a crowd of thousands and be unable to explain how you did it. The knowledge is real and you use it constantly, but you have never had to put it into words. Your operating model is exactly that kind of knowledge. Six years of running into walls taught you which customer emails mean trouble and which vendor will flake in a crunch, but none of it ever needed to be said, because you were always in the room to make the call yourself.

Then you hired Marcus and asked him to apply a set of rules you have yet to speak aloud.

With nothing on the page, a good operator makes the sensible move. He starts interviewing you.

That's what those 90 days have been. He follows you from meeting to meeting, reverse-engineering your company one question at a time, trying to pull six years of judgment through the narrow straw of your attention on a busy day.

He asks because the answers live in exactly one place, and that place spends most of its day juggling a dozen other things. You hired Marcus to take interruptions off your desk, but for these first months he has become the single biggest source of them. The weight flipped around and doubled, and you're paying $250,000 a year plus benefits for the privilege.

The bill for this shows up in more places than his comp line.

It shows up on your team, who now have two bottlenecks where they used to have one, because the person you hired to unblock them is himself stuck at your door. It shows up in the calendar math, where three months of runway buys an expensive operator working at half speed while he waits for you to define his job in real time. It shows up in the mornings, when Marcus walks in with a little less of the confidence he had in the interview, because nobody feels good spending their days proving they can't work independently. And it shows up in you, more scattered and more tired than before you hired the person who was supposed to fix exactly that.

Every line of that bill traces to the same missing step: a handoff that never happened.

I'm not going to tell you the hire is always fine and the blank page is always the culprit. Sometimes you do get the wrong person, and no amount of documentation saves it. If Marcus were dodging ownership on things you had spelled out plainly, that's a different conversation, and a faster one.

And you can't write it all out. Some of your judgment is the face-in-the-crowd kind that resists words, and you'll never get every last piece out of your head and onto paper. The goal is smaller than that: get the recurring calls down, with the reasoning attached, and your operator can run most of the company on his own and bring you only the ones that need a founder. Get that far and you've changed the whole trajectory of the hire.

Ikujiro Nonaka and Hirotaka Takeuchi spent years studying how companies turn one person's private know-how into something a whole organization can use. They gave that move a plain name: externalization, the work of dragging tacit judgment out into explicit words other people can pick up and run with. That is the missing step, and it's recoverable, and it starts on a page.

Write down the recurring decisions, each with an owner and a limit. Put it where he can act on it without you: "You own vendor contracts under $10,000; sign them and tell me after." The name tells him it's his to run. The dollar figure marks where the authority stops. Keep that same boundary in your head rather than on the page, and it drifts every time you're slammed, so he quits trusting it and routes back through you.

Spell out the reasoning under each rule. The rule is easy to copy. The thinking under it is harder to pass along, and it's what lets your operator handle a case you didn't foresee. Tell him why the enterprise accounts get the extra care, and he can extend the logic on his own.

Draw a hard line around what still needs you. Put the short list of founder-level calls on paper, and the rest stops drifting to your desk by default. People bring you everything because nobody ever told them what not to bring.

You don't have to produce all of this alone in a weekend, and you don't have to have it perfect before he starts. Begin the page yourself, then make finishing it his first project, the two of you in a room pulling the rest of the model out of your head and into words. That work is the very thing he's been trying to pull out of you by ambush, one hallway question at a time. Do it on purpose, in the open, and you've handed him the thing the job runs on.

Picture the version where you did this first.

Marcus starts on a Monday with the operating model in front of him, the decisions mapped, the boundaries drawn, the reasoning attached. His first weeks go to running the company against that model and flagging the handful of places it doesn't cover yet, exactly what you hired him to do. By the time you'd otherwise have been sitting across from him wondering if you made a mistake, he's the reason you got a Thursday back. The digging was already done, the way you always pictured it.

Marcus was the right call the day you made it. The blank page you set on his desk cost you three months and nearly a good hire. That page was yours to begin, and getting what's in your head onto it is how you finally leave the middle you've been trying to hire your way out of all along. Start it before the next one walks in.

Catch is an AI admin that's as easy as a conversation. Just call Catch and talk, like you would any assistant. Scheduling, bookings, follow-ups: say it once, consider it done. No apps to learn, no forms to fill. Get started at catchagent.ai and speak to your admin savior today.

Start now for free

Thanks for reading. See you next Wednesday.
— Jason

P.S. If your team still routes every call back to you, last month's Why Your Team Brings You Every Decision is the companion piece.