The E-Myth Revisited: Write Down the Work Only You Know How to Do

Sarah makes the best pies in town, so she opens a pie shop. Before long she's working every waking hour, and the thing she loved has turned into the thing she dreads. Michael Gerber built a whole book around her, and I'd bet most readers recognize someone. Sometimes it's the person in the mirror.

The book in brief

The E-Myth is the entrepreneurial myth: the belief that if you're good at the work, you'll be good at running a business that does the work. Gerber says that belief is wrong, and that it's behind a lot of small business failures.

His model splits every owner into three people. The Technician does the work. The Manager keeps things in order. The Entrepreneur looks ahead and decides what the business should become. Most people who start a business are Technicians who had what he calls an entrepreneurial seizure, and the Technician keeps running the show.

The fix is his best known line: work on your business, not just in it. Gerber's model for this is the franchise prototype. Build your business as if you were going to sell 5,000 copies of it, even if you never sell one. That means every task gets written down as a procedure, clear enough that someone ordinary could follow it and get the same result.

He points to McDonald's and Ray Kroc as the proof. The food isn't the product. The system is. A sixteen-year-old on a first job can turn out the same burger in Ohio and in Oregon because somebody wrote the process down first.

The book repeats itself, and the franchise idea doesn't fit every business. Sarah's story gets stretched thin. But the core lesson has held up since the first edition in 1986: a business that depends on your constant presence is a job, and a demanding one.

The Rhynowerks angle

Gerber is talking to business owners, but read the book as a trainer and something jumps out. The franchise prototype is a training system. The Operations Manual he describes is a curriculum. He just never calls it that.

The Navy figured this out long before Gerber wrote it down. A ship can't depend on one sailor who knows how to do a job, because that sailor transfers, gets sick, or retires. So the job gets written down: the steps, the standard, how you check that it was done right. Then anyone qualified can be trained to do it. I spent most of thirty-nine years in that world, and the lesson that stuck is plain. Knowledge that lives in one person's head is a single point of failure.

Most experts carry exactly that kind of knowledge. You know the order you do things in, the shortcuts that are safe, the mistakes that look harmless and aren't. You know it so well you can't see it anymore. That's the Technician problem in Gerber's book, and it's also why so many experts struggle to teach. They skip steps they don't remember taking.

So try Gerber's exercise, aimed at teaching. Pick one task you do that nobody else around you can do as well. Write it as a numbered procedure. Not an essay. Steps. Then hand it to someone who's never done it and watch them try. Don't help. Every place they stall is a step you skipped, a term you never defined, or a judgment call you made without noticing.

That afternoon will teach you more about what your course needs than a month of outlining. The gaps are the lessons.

And if you never build a course at all, you still win. You'll have one task out of your head and onto paper, which is the first step Gerber asks of every owner.

The Bottom Line

What you know only helps one person until you write it down. Turn one task into steps, test them on someone new, and treat every stall as the next lesson to write.

New posts go up here every two days. Bookmark https://blog.rhynowerks.ai and come back.