UDEHA

The business that only runs when you are in it

Gerber is right about the trap and quiet about what the escape costs

Michael E. Gerber · The E-Myth Revisited · 1995

One solid block ringed by dozens of translucent plates on thin rods.

What the book is really about

Gerber's argument is narrower than the cover suggests, and it is not really about entrepreneurship. It is about one specific mistake made by people who are good at their work.

You were the best technician in someone else's business — the best hygienist, the best colourist, the best surveyor — and one day you decided you would rather do that work for yourself. Gerber calls that moment an "entrepreneurial seizure", and the point of the phrase is that the decision skipped a step. You bought yourself a job with longer hours and more risk, and the thing you now own is shaped exactly like your own hands.

His remedy is to build the business as though it were the prototype of a hundred identical ones, whether or not a second location ever opens. Not because franchising is the goal, but because a prototype has to be describable: every result has to come from a process rather than from one person's judgement on the day. Take that seriously and the daily question changes. It stops being "what needs doing today" and becomes "which part of today should never need me again".

The obstacle it speaks to

Working In, Not On, described with more precision than most books manage.

The mechanism is not laziness and it is not disorganisation. It is that operational work carries a deadline and strategic work does not. The client at eleven is a fact. The hiring plan is an intention. When the two meet in the same morning the fact wins, every morning, for years — and nothing in the accounts records what the intention would have been worth.

Underneath it sits the Owner-Dependency Trap, and the reason it stays invisible is that it is made of compliments. Clients ask for you by name. Your team checks with you because you are the one who knows. Suppliers have your mobile number. Each of those is evidence that you are valuable, and all of them together describe a business that loses money on any day you are not standing in it.

The third piece is SOP Avoidance, which almost never arrives feeling like avoidance. It arrives as speed: writing it down would take an hour, doing it takes twelve minutes. That arithmetic is correct the first time and wrong the fortieth.

And when someone does offer to take a task, Delegation Distrust closes the loop: no one does it to your standard. That is usually true. It is also a documentation problem wearing a trust problem's clothes, because the standard exists in one head and has never been written anywhere a second person could read it.

Gerber's real contribution is the reframe, and it holds. The work is not the business. The work is the product the business makes.

Three ideas that change behaviour

Draw the org chart of the business you will have in three years, then write your own name in every box you currently fill. Most owners find themselves in six or seven boxes, and the exercise stops being abstract at that moment. The empty boxes are not a fantasy hiring list. They are the order in which you will document, train and hand over.

Write the procedure for the result, not for the task. A usable procedure says what the finished thing looks like and what a bad version looks like, so somebody tired on a Saturday can tell which one they have produced. An unusable one is a list of steps that makes sense only to the person who already knows the steps.

Give the three jobs separate hours. Technician, manager, owner. They do not share an attention span, and the owner's work is the only one of the three with no external deadline — so it gets the slot you defend, or it gets nothing. Two hours, one morning, the same morning each week, phone in a drawer.

Where it falls short

The prototype model was built for work that repeats with low variance. A print shop, a lettings agency, a drive-through: the value is the consistency, and consistency is precisely what a documented process produces.

Your business may not be that. If people book because of your judgement — a surgeon, a stylist with an eighteen-month following, a consultant whose entire fee is discernment — then the part your clients are paying for is the part that cannot be written down. Follow the book literally and you will systematise reception, follow-up and the stock order, then stall at the thing that actually earns the money and conclude you have failed. You have not failed. You have found the boundary.

The cleaner move is to split the delivery in two. Name the portion that is genuinely you, price it accordingly, and defend the hours it needs. Then build process around it until that portion is all you do.

Gerber also writes as though documentation were free. For a six-person business it is not. The month you spend writing procedures is a month you are not selling, and he says nothing about where that month comes from. Take it in half-hours, attached to the job you were already interrupted for.

What to do this week

For the next five working days keep a note — paper, by the till, one line each time — of every occasion when somebody had to ask you something before they could carry on.

On Friday, read it. One item will appear more often than the rest. Write that one down in half a page: what the finished result looks like, what a bad version looks like, and the two decisions that always come back to you. Hand it to the person who asked most, and let them work from it next week without you correcting them in the moment.

That half page is the first line of the org chart you will eventually draw.

  • Habits
  • Leading people
  • Systems

What it speaks to

More on the shelf