A great chef opens a restaurant. She is brilliant in the kitchen, so it seems obvious the venture will succeed. Instead she finds herself working a hundred hours a week, not cooking, but doing payroll, fixing the schedule, chasing suppliers, covering shifts, and resenting the dream that became a cage. She did not build a business. She bought herself the most demanding job she has ever had, and she is the only person who can do any of it. This is the trap Michael Gerber spent a career diagnosing.
What is the E-Myth?
In The E-Myth Revisited, Gerber identifies what he calls the fatal assumption: the belief that because you understand the technical work of a business, you understand how to run a business that does that work.1 These are entirely different skills, and conflating them is the most common reason small ventures grind their founders down. Being a superb chef, coder, designer, or consultant tells you nothing about building the systems, processes, and structures that let such work happen reliably without you at the centre of every task.
So the technician opens a business and simply does more of the technical work, now buried under all the operational work nobody warned them about. They are, in Gerber’s terms, working in the business, doing the tasks, when the job of an owner is to work on the business, building the machine that produces the results.
Why is the operator trap so seductive?
Because the technical work is what you are good at and what feels productive. Doing the thing you mastered is comfortable and immediately rewarding; building systems is unfamiliar, abstract, and slow to pay off. So the founder keeps reaching for the work they know, and every hour spent doing the work is an hour not spent building the structure that would free them from having to do it. The trap tightens precisely because escaping it requires doing something that feels less productive in the moment than just getting the work done yourself.
The result is a business that cannot run without the founder present, which is not really a business at all but a self-made job with extra risk. Revenue is chained to the owner’s hours, cognitive load rises with every new client, and the whole thing collapses the moment the founder stops, takes ill, or burns out. There is no leverage, no compounding, only a person running faster and faster to keep a machine alive that only they can operate.
What does escaping the trap look like?
It means deliberately shifting time from working in the business to working on it. Build systems for the repeatable work, so it does not require your personal attention each time. Document how things are done, so the knowledge lives in the process rather than only in your head. Delegate, to people, to tools, and increasingly to AI, the tasks that do not genuinely require you, reserving your own hours for the judgment-intensive work that actually does.1 The aim is a business that compounds: a flat or falling personal workload as revenue grows, systems carrying the load, and you focused on the small set of decisions only you can make.
This is where the founder’s playbook meets the rest of the book. The operator trap is the entrepreneurial version of letting work expand to fill all available time, and the escape is the same in spirit: question what genuinely needs you, eliminate or systematise the rest, delegate aggressively, and protect your own time for the work of highest value. AI sharpens both the danger and the cure. It makes it easier than ever to keep grinding through technical tasks personally, and easier than ever to build the systems and leverage that let you stop. The founders who thrive will be the ones who use it for the second, not the first. The point of owning a business was never to own a job. It was to build something that works, including when you are not.
Frequently asked questions
What is the E-Myth operator trap?
It is Michael Gerber’s idea that most small-business owners are really technicians who are good at the work and assume that means they can run a business built on it. They end up owning a demanding job rather than a business, trapped doing the work instead of building the system.
What does working on the business rather than in it mean?
Working in the business is doing the technical work itself. Working on the business is building the systems, processes, and structures that let the work happen without you. Gerber argues founders must shift toward the latter to escape the operator trap.
How do you escape the operator trap?
Build systems that do not depend on you personally, document and delegate the repeatable work, use leverage and tools including AI, and reserve your time for the judgment-intensive work only you can do.
About the author
Tom Goodwin is the author of Don’t Work Harder, a book about taking the time AI gives back as time rather than more work. He is a co-founder of GAMEPLAN and writes on productivity, technology, and the economics of the working week.