Technician Manager Entrepreneur Framework: E-Myth Roles

Created by Michael E. Gerber - https://www.emyth.com/

Overview

The technician manager entrepreneur framework is Michael E. Gerber's model of the three E-Myth business roles every small business owner carries: the Technician who does the work, the Manager who creates order, and the Entrepreneur who decides where the business is going. Gerber introduced it in The E-Myth, published by Ballinger in 1986, and reworked it in The E-Myth Revisited, dated 1995. The framework is a way to compare technician vs manager vs entrepreneur as three personalities inside one person, and to balance technician, manager and entrepreneur work deliberately instead of letting the craft take every hour.

The name comes from what Gerber calls the Entrepreneurial Myth. EMyth's own about page describes it as "the myth that businesses are started by Entrepreneurs" and states Gerber's counterclaim plainly: "most businesses are started by Technicians. Plumbers open plumbing businesses, auto mechanics open auto repair shops, doctors open medical practices and so on." The error underneath, which Gerber calls the Fatal Assumption, is quoted on the EMyth home page: "if you understand the technical work of a business, you understand a business that does that technical work." A StoryShots summary of the book describes the moment a skilled worker decides to become their own boss as Gerber's "entrepreneurial seizure."

Each role has its own orientation and wants something different. In Shortform's guide to The E-Myth Revisited, the Entrepreneur "is always thinking of the future" and "has a strong need for control." The Manager "is a pragmatist who uses planning and systems to create order and predictability" and "sees problems rather than opportunities." The Technician "is an individualist and a doer" who "lives in the present" and likes "to work on one thing at a time." The three pull against each other, and the same guide sums up Gerber's position: "A small business needs all three mindsets working in harmony."

Gerber also describes how the three usually show up in practice. In its summary of the book, StoryShots states that the typical small business owner is "only 10 percent Entrepreneur, 20 percent Manager, and 70 percent technician" (StoryShots), and Shortform gives the same split (Shortform). Both summaries present it as a description of the typical owner. Neither presents it as a target ratio, and this page does not treat it as one.

The behavioral core of the model is the difference between working in the business and working on it. EMyth calls "Work on your business, not in it" the defining idea behind the company (EMyth about page). Working in the business is Technician work that produces today's output. Working on it means designing the business as a system that produces that output without depending on the owner, which Gerber frames as building a franchise prototype: "imagine your business is merely a prototype of 5,000 more just like it" (StoryShots). The same summary lists Gerber's three growth phases (infancy, adolescence and maturity) and the seven steps of his business development program, from the primary aim through the systems strategy.

Gerber built a company and a series of books on the idea. EMyth's about page traces it to 1975, when Gerber was helping small business clients of his brother-in-law's advertising agency build their sales process. The company dates its own founding to 1977 and says Gerber still urges owners to move "from Technician Leader to Entrepreneurial Leader so their business works without them rather than because of them." That transition is what people mean when they talk about how to emerge from technician to entrepreneur. He later applied the model to management in The E-Myth Manager (1999) and to specific trades, including The E-Myth Contractor (2002) and The E-Myth Physician (2003), which is the basis for applying the E-Myth to agencies and service businesses.

This page covers the model, its origin and how it compares with related role frameworks. The skills below turn it into practice: assessing your current role balance, designing a weekly time allocation, building systems in the Manager role, writing the Entrepreneur's vision, handing off technical work, and shifting from working in to working on the business.

Core Principles

The business is a separate thing from the craft

The Fatal Assumption confuses knowing the technical work with knowing how to run a business that does that work (EMyth). A skilled baker, developer or designer can run a shop that only works while they are at the bench. The model asks the owner to treat the business itself as the thing being built. StoryShots gives Gerber's example of Ray Kroc, who "realized the hamburger wasn't his product, McDonald's was" (StoryShots).

All three roles are needed

The Technician without the Manager produces work that cannot be repeated by anyone else. The Manager without the Entrepreneur runs an orderly business with no direction. The Entrepreneur without the other two produces plans that never get delivered. Gerber's point, as Shortform summarizes it, is that the owner possesses all three "to varying degrees" and the business needs them "working in harmony."

The Technician is the default

Owners usually start as Technicians, so Technician work feels like the real job and everything else feels like overhead. Urgent client or product work also arrives with deadlines, while Manager and Entrepreneur work rarely does. Left alone, the Technician fills the week. The practical consequence is that the other two roles need scheduled time and named outputs, because they will not win on urgency.

Work on the business as well as in it

Working in the business produces today's revenue. Working on it produces the systems, structure and direction that decide next year's revenue. EMyth treats this distinction as its defining idea (EMyth about page). Both kinds of work are necessary, and the owner's job is to make sure the second kind happens on purpose.

Build a prototype that others can run

Gerber's franchise prototype asks the owner to design the business as if it would be copied many times, whether or not it ever is. That forces documented processes, quality standards and training that do not depend on one person's judgment. StoryShots quotes his definition of the goal of systems work: "Orchestration is the elimination of discretion, or choice, at the operating level of your business" (StoryShots). Discretion stays with the people designing the system, and the people running it follow it.

Organize around functions, then fill them with people

Gerber advises building the organization from the functions the business needs and only then deciding who fills each one; StoryShots puts it as "based on functions, not personalities" (StoryShots). In a small business the owner's name will appear in most boxes of the chart at first. Seeing that on paper shows which functions to document and hand off first.

Delegate with a system behind it

The failure Gerber names in the growth stage is "management by abdication": handing work to employees and then not overseeing it, until the owner has to take it back (StoryShots). Delegation holds when the person taking over has a documented process, a quality standard and a way to report results. Without those, handing off work only moves the problem.

Steps

1. Audit where your time goes Track a normal working period and tag each activity as Technician (doing the work), Manager (organizing, documenting, supervising) or Entrepreneur (deciding direction, markets and offers). Tag by the purpose of the activity rather than its format, since a client meeting where you do the design review yourself is Technician work. Compare what you find with your own impression of your week. The output is a plain statement of how your time splits across the three roles. The self-assessment skill gives a full worksheet for this.

2. Name the dominant role and what it costs Identify the role that crowds out the others and list the concrete costs of that dominance. For a Technician-dominant owner the costs are usually output capped at personal capacity, nothing documented, and no one able to cover when the owner is away. For an Entrepreneur-dominant owner they are unfinished initiatives and a team that cannot keep up with changes of direction. For a Manager-dominant owner they are process overhead and slow decisions. Write the costs down so the case for change rests on evidence you can revisit.

3. Write the primary aim and strategic objective Gerber's development program starts with the owner's primary aim, the kind of life the business is meant to support, and then a strategic objective with measurable standards for the business (StoryShots). This is Entrepreneur work, and it gives the other roles something to build toward. Keep it short enough to reread every week. The entrepreneurial vision skill covers this step in detail.

4. Draw the organization by function List the functions the business needs, such as sales, delivery, finance and operations, and put the name of whoever does each today in its box. In most small businesses the owner's name appears in most of them. Mark which functions you want to hand off first, starting with repeatable work that does not need your judgment. This chart becomes the map for the system-building and hiring that follow.

5. Systematize the work you want to release Pick two or three repeatable Technician tasks and document each one: what triggers it, the steps, the quality standard, and the decisions and exceptions. Gerber's sequence for this is innovation, quantification and orchestration (StoryShots): find a better way, measure it, then make it the standard way. Test each document by having someone else follow it and fixing what they stumble on. The systems skill walks through the format.

6. Hand off work and protect time on the business Transfer documented tasks with a period of overlap and a clear way for the new owner to report results. Put recurring blocks on your calendar for Manager and Entrepreneur work, each with an agenda, and defend them the way you would defend a client commitment. Expect the shift to take several review cycles, because it depends on people and trust being in place. The time allocation skill and the transition skill cover this in practice.

7. Review the balance as the business changes Repeat the audit on a regular schedule and after big changes, such as a key hire, a lost client or a new market. Compare the new picture with the last one and choose the next one or two changes to make. The right balance moves as the business passes through what Gerber calls infancy, adolescence and maturity (StoryShots). A review that happens once and is never repeated usually ends with the Technician back in charge of the calendar.

Comparison with Related Models

Several other role models cover similar ground. They differ in how many roles they name and whether they describe one owner or a leadership team.

The EOS Visionary "owns the vision, generates ideas, maintains culture" and the Integrator "runs the business day-to-day, and holds the leadership team accountable" (EOS Worldwide), which lines up with Gerber's Entrepreneur and Manager. EOS names no Technician seat, since its two roles describe a leadership team. Paul Graham's essay describes manager mode as telling direct reports what to do and leaving the how to them (Founder Mode), which is a debate about how a founder leads at scale. The E-Myth model is most useful earlier, when the owner still does most of the hands-on work.

When to Use

• You are a founder or owner doing most of the hands-on delivery, you are busy all the time, and output has stopped growing. The audit shows whether your own capacity has become the ceiling.
• Your team does good work but depends on specific people, little is written down, and quality drops when someone is away. That pattern points to a missing Manager role and tells you which processes to document first.
• You have hired a team and now spend your days in meetings and firefighting, with no time left to decide where the business should go. The framework separates Manager work from Entrepreneur work so each gets its own time.
• You are bringing in a co-founder, a first manager or an operations lead and need to agree who covers which role. The three roles give a shared vocabulary for dividing responsibilities.
• You run an agency, practice or other service business where the owner is also the main practitioner. Gerber wrote trade-specific versions of the book for exactly this situation.

When Not to Use

• You are still testing whether anyone wants the product. Documenting processes around an offer that may change next month wastes effort, and fast Technician and Entrepreneur work is the right mix at that point.
• You run a deliberate solo practice and have no plan to hire or productize. The model assumes you want a business that works without you, and applying it anyway produces systems nobody will use.
• Demand is the problem. If the market does not want what you sell, rebalancing your own time will not fix it, and the framework can distract from that signal.
• You lead a large company where the roles already sit in separate departments with separate leaders. Organizational design tools fit that problem better than a model of one owner's attention.