For a long stretch at Celltronix I thought the job I was doing all day was running a company. I was wrong, and it took me embarrassingly long to see it. What I was actually doing was managing one.
Those two words get used interchangeably. They describe almost opposite jobs.
What managing actually looked like
Managing looked productive. That is the whole trap.
My days were full. They started early, they ended late, and every hour had somebody else's name on it. A store manager needed a ruling on a schedule conflict. A customer wanted someone with authority on the phone. A carrier rep had a question only I could answer. Payroll had an edge case. Somebody quit, which meant somebody had to be hired, which meant I was reading resumes at nine at night.
Every one of those was real. Every one of those needed handling. And every one of those was a response to something that had already happened.
That is the definition I eventually landed on, and I have not found a better one. Managing is responding to the company that already exists. Running it is deciding what it becomes.
I was good at the first one. I had built fast reflexes for it, and the reflexes were the problem, because they meant the work never ran out. There is no bottom to a queue of other people's decisions. You will never clear it. You will only get faster at it, and getting faster feels exactly like progress right up until you notice the business has not moved in a year.
The thing that finally gave it away
It was not a crisis. I want to be honest about that, because the story would be better if there were a crisis.
What happened was quieter. I sat down to think about where the company was going and I could not do it. Not for lack of ideas. I could not find the hour. Every block on the calendar belonged to someone else, and the only way to get an hour back was to take it from a person who was waiting on me.
"There is no bottom to a queue of other people's decisions. You will never clear it. You will only get faster at it."
So I did the arithmetic that actually stung. I went back through the previous week, item by item, and asked one question of each: if I had been unreachable, would this have been handled?
Most of it would have. Not as well in every case. But handled. Someone would have made a call, the call would have been eighty percent as good as mine, and the business would have been completely fine.
The rest of it, the part only I could do, the part about what we sell next and where we open and who we are trying to become, came to roughly nothing. I had spent a full week as the most expensive escalation point in my own company.
Why good operators get stuck here
I do not think this happens because founders are bad at delegating. That explanation is too easy, and it is a little insulting.
It happens because being needed is the most reliable feeling available to you. A manager calls, you solve it in four minutes, and you get immediate, unambiguous proof that you are good at your job. Strategy gives you nothing like that. You make a call about next year and you find out whether you were right in eighteen months, if you ever find out at all.
So you drift toward the work that pays you back the same day. Anyone would.
There is a harder version of this too. Early on, you being the answer to everything is not a flaw, it is the operating model. At five people the fastest path really does run through you. The trouble is that nobody sends a memo when that stops being true, and the exact skill that carried you through the first phase is the one that caps the next.
Michael Gerber wrote a whole book about this gap, The E-Myth Revisited, and framed it as working in your business versus working on it. I read it years after I needed it. The framing is right. What the framing does not capture is how invisible the switch is while it is happening to you.
The test I use now
I do not have a framework with an acronym. I have one question, and I make myself answer it in writing, because answering it in my head lets me cheat.
Pull up the last two weeks of your calendar. Go block by block and sort each one into one of two piles:
- This was on here because something happened.
- This was on here because I decided it should be.
The first pile is managing. The second is running. If the second pile is empty, you do not have a time management problem. You have a job description problem, and no productivity system will fix it, because you are not being inefficient. You are doing a different job than the one you believe you are doing.
Then the follow-up, which is the question that actually costs something: what would have to be true for the first pile to belong to somebody else?
In my experience the answer is usually not a hire. It is that the decision lives in your head and nowhere else, so every instance of it has to route through you. That turned out to be the whole mechanism, and I wrote it up on its own: your business is only as big as what you wrote down.
What it cost to change it
I do not want to make this sound tidy. I did not read a book and reorganize my week.
What I did was take the single highest-volume category of interruption and treat it as a design problem instead of a people problem. Why does this keep reaching me? What would someone need to know to handle it without me? Write that down, hand it over, and then sit with the fact that the first few months of someone else's judgment will be worse than yours.
That last part is the price, and it is the reason most owners never pay it. You are trading a little quality today for the only version of the company that can outgrow you. There is no way to make that trade feel good while you are making it.
The honest version of the lesson is this: by the time you notice you are managing instead of running, you have probably been doing it for a year or two. The calendar knew before you did. Nobody reads a calendar as a diagnosis.
I still catch myself sliding back. The pull toward the solvable thing never really goes away. These days I just notice it sooner, and I know what the two piles are supposed to look like.