Principle · Operations

The E-Myth: Work ON the Business, Not IN It.

Source: Michael Gerber, The E-Myth Revisited: Why Most Small Businesses Don't Work and What to Do About It (1995), HarperBusiness.

The Principle

Most small businesses are started by technicians. The plumber starts a plumbing company. The chef opens a restaurant. The consultant goes solo. The technician is good at the technical work and assumes that being good at the technical work is what running the business is. It is not. Running a business is a separate discipline, and the technician who does not learn it stays trapped inside the work, building themselves a job instead of a company.

Gerber names three roles inside every business: the Technician (does the work), the Manager (organizes the work), and the Entrepreneur (designs the system that does the work). Most founders are 70% Technician, 20% Manager, 10% Entrepreneur. The healthy ratio is closer to balanced, with the Entrepreneur role getting the time it deserves. The Entrepreneur is the one working ON the business, designing the system. The Technician is the one working IN the business, running the system. A founder stuck working IN the business for fifty hours a week never builds the system that frees them.

The fix is to design and build the business as if you were going to franchise it. Not because you intend to franchise. Because that mental model forces you to document, systematize, and depersonalize the work. The system, not the senior person, is what produces the result. The senior person's job is to build, improve, and own the system.

Why It Matters Here

Operations is the department where this principle most directly applies. The COO's job is not to do the operational work. It is to design the system that does the operational work. Without the E-Myth lens, the COO ends up as the most senior technician in the company, racing to keep delivery alive instead of building the machine that delivers without them. The role is fundamentally Entrepreneurial, not Technical, even though the work itself is hands-on.

Signals (When to Apply)

The same task is being done by hand for the third or fourth time, with no documented standard
The COO or the founder is the only person who knows how a critical workflow runs
A new hire takes weeks to get productive because nothing is written down
Delivery quality varies depending on which senior person ran it
The team is busy but the founder still cannot take a real vacation

How to Apply

Before doing any task that will recur, ask: "Am I building the system, or running the system?" If running, document while you run. The next time, someone else can use the document instead of asking you.
Write the standard before delegating the work. A delegation without a written standard creates dependency on the delegator. A delegation with a written standard transfers ownership.
Design every workflow as if the next person to run it has never seen it before. That person might be a new hire, a contractor, or an AI agent. The standard either holds up or it does not.
Review one workflow per week. Improve the document, the checks, and the handoffs. Compounding improvement to the system is the highest-leverage work the COO does.
Refuse to be the backup plan. When something fails, fix the system. Do not patch it by personally doing the work. Patching trains the team to keep escalating to you.

Examples

Applied well A founder runs every client onboarding personally for the first ten clients. By client eleven, she has documented the steps, recorded a loom for each one, and built a checklist that her ops lead can run. By client twenty, she has not been in an onboarding for two months. The system runs. Her time is now spent improving the document and shipping the next system. The business grew. She did less of the work. That is the E-Myth applied.

Misapplied The same founder runs every onboarding personally because "nobody does it like I do." By client twenty, she is doing forty hours a week of onboarding. She cannot sell more, build more, or take a day off. The team grew, but only she can run the most important workflow. The business is bigger and the founder is more trapped. That is the E-Myth missed entirely.

When to Break It

In genuinely novel situations where there is no system to follow because the work has never been done before. The first time, the senior person does the work. The second time, they document. By the third time, the system runs.
When the volume is too low to justify systematization. A workflow that runs twice a year may not earn the cost of a written standard. Document it lightly and move on.
During short-term capacity crises where speed matters more than scalability. Acknowledge it as temporary and rebuild the system once the crisis is over.