The Phantom Org

Your org chart shows one company. Your operating reality is another. You know this. Most of the people around you know it too. Nobody says it out loud.

There is a function where the title belongs to someone else but the decisions still come to you. Probably more than one. You review the thing. You edit the thing. You catch the thing before it goes out. You tell yourself you’re “just staying close” or “helping them ramp.” What you have is a VP in name and a VP-flavored assistant in practice.

The org that exists on paper

Walk the org chart from your last board deck. Five functions, five owners. Now trace where the final calls land. Who approved the marketing copy that went out last week? Who said yes to the pricing exception on the mid-market deal? Who set the number on the offer for the senior engineer? If the answer keeps coming back me, you’re running a phantom org. Titles on paper, decisions in your inbox.

Your team has already adjusted to it, which is why it’s quiet. They pre-clear things. They wait. They’ve learned that final calls come back to you eventually, so they’ve stopped making them. That isn’t weakness. They read the pattern correctly. The org chart says delegation. The Slack threads say otherwise.

You’ve felt the private version. It’s 11 p.m. and you’re rewriting a two-line Slack reply to your own VP for the third time. What you want to type is this isn’t the call I’d have made. You know what sending that does. So you soften it. Then you take the decision back anyway. Quietly.

Why founders rebuild the cage

Noam Wasserman’s Founder’s Dilemmas names why this happens: founders under-hire and over-review because the cost of a mistake feels bigger than the cost of staying involved. A mistake is vivid. A botched launch, a bad hire, a lost deal. The cost of staying involved is invisible. It is spread across every decision your team didn’t make, every week, forever.

Ben Horowitz has a name for it. The rehire. You bring someone in, quietly take parts of the work back, and end up with the worst of both worlds. You have paid for a senior hire and you are still doing the work. Run the six-month test on your most recent senior hire. Did they take it, and you haven’t looked back? Did they take it, but you’re still checking in more than you expected? Or have you quietly taken parts of it back?

Underneath all of it sits the question nobody asks out loud: if someone else can run sales well without you, then what do you do here? Nobody asks that in a meeting. It runs the org chart anyway.

First Round’s research on the $1M→$10M transition is blunt about the stakes: the founders still holding shadow functions at that band are the ones who stay stuck there for years.

How to know it’s you

Count the Slack threads waiting on your input right now. A few is a normal weekday. More than you can clear today, month after month, is a structure rather than a workload. Then there’s the hire you’ve been circling and haven’t made. What’s the real reason? Sometimes it’s timing. Sometimes it’s cost against an unknown return. But sit with it. If the answer is closer to what it would mean to hand that over, that’s the pattern talking.

And the question you’d rather not answer: walk the chart and count the functions where you would admit, if pressed, that you’re still running the show. “I’d rather not count” is a count.

What it compounds into

Shadow functions rarely exist alone. Often you hold them because nobody else knows the story well enough to make the calls without you. New hires ask “what should we do about X?” and the honest answer is “it depends on who we’re for,” which is the question that hasn’t been answered clearly. Without that answer, every delegation is conditional and every senior hire has to read your mind to succeed. Your team isn’t underperforming. They are working without the document they’d need to perform.

The functions you hold longest are the ones closest to revenue. Sales, marketing, maybe customer success. If they broke, the company wouldn’t survive the quarter. That’s real. It is also the argument that stops you ever letting go, because those functions will always be closest to revenue. Waiting until it feels safe to delegate revenue work is waiting for a moment that never comes.

The hand-off happens while it’s still scary.

Meanwhile your week fills with approving, reviewing and unblocking, and the CEO work goes undone. The calendar doesn’t show it, because Slack threads don’t appear on calendars. But it’s where most of your week goes, and it’s its own pattern.

Naming the functions: three moves

Take the honest census. List every function. Mark the ones where the title and the decisions diverge. Then mark the one or two you should still hold at this stage. Naming those out loud is what makes releasing the rest credible.

Write the mandate you never gave. Pick one shadow function. One page: what the owner decides without you, what they bring to you, what good looks like in ninety days. Most failed delegations fail here. The hire got a title and a backlog, never a mandate. Hand the function over with the document.

Move yourself from pre-approval to post-review. Stop being the gate decisions wait at. Review outcomes on a cadence instead of approving inputs in the moment. Your team will make calls you wouldn’t have made. That’s not the risk. That’s the point.

Name the functions. Some you should still hold. Most you shouldn’t. The first move is honesty about which is which.