Where Do Humans Shine?

How do humans “shine”? Systems can be built. Processes can be documented. Frameworks can be borrowed, refined, repackaged, and scaled. AI can retrieve and synthesize faster than any person in any room. And still, something keeps slipping through the machinery.

No one is going to systematize their way to good judgment. Noticing what the process missed, sitting with ambiguity long enough to understand it, recognizing that the person across the table is more than their function dos not get built into a framework. It is part of learning and growing as a person, a human experience that cannot be documented because humans are not mechanical.

That is where humans shine. What follows traces how we got here, what we handed off, and what we cannot afford to.

The E-Myth and the Systems That Followed

Michael Gerber wrote the book The E-Myth (1985), and his entire framework was built around the idea that a business should be treated as a system, designed to run like a franchise prototype, independent of the people inside it. E-Myth

Gerber’s core message was simple: work ON the business, not IN it. Build systems. Document processes. Make it replicable. Create something that runs without you.

Gerber used some mechanical language. His famous analogy was that a business should run like a McDonald’s franchise. Every process documented. Every role scripted. Every outcome predictable. But Gerber was transparent about the analogy. He was openly saying: treat your business like a machine. He was not pretending the machine language was people language. The analogy was the point.

On the other hand…

EOS (Entrepreneurial Operating System) essentially took Gerber’s foundational thinking, repackaged it, added a consulting and licensing model around it, and gave everything new names. Some of those names happen to be mechanical sounding names.

Even the word “Entrepreneurial” in EOS feels like a direct nod to Gerber, whose entire brand was built around the word “Entrepreneur” and debunking the myth of what one actually is. Gerber called his myth the E-Myth. Gino Wickman and Mark Winters called their (rocket fuel) system the Entrepreneurial Operating System (EOS). The lineage is not subtle.

Gino/Winters took the same foundation as Gerber, dressed it up in new terminology, and presented it as a fresh and original system. What they did not do was acknowledge with any real clarity how much of the intellectual groundwork had already been laid by Gerber decades earlier. For a framework that asks business owners to operate with clarity and honesty, that is a glaring omission.

Attribution: who gets credit for ideas, whether human or AI?

Refinement Is Innovation

The concept of building systems so a business can run without the founder is genuinely valuable. Gerber deserves credit for putting that idea into the mainstream. What followed was largely refinement and rebranding. But refinement is not nothing. It is how ideas become usable.

Wickman and Winters took an intellectual framework and turned it into something a room full of business owners could actually implement on a Monday morning. That is a different skill than originating the idea. It is closer to engineering than invention. And in practice, it may be more valuable. An idea that stays theoretical helps no one. An idea that gets systematized, taught, licensed, and repeated across thousands of companies has real impact, whatever its origins.

The same logic applies to AI. Large language models did not invent the ideas they reflect back. They refined access to them. They compressed decades of accumulated thinking into something retrievable in seconds. That is not creation. But it is not nothing either.

The mechanical term Gino and Mark used for a key position, integrator, makes human work sound like a machine function. Even the visionary role can be replaced by AI. But that is not mechanical. That is process. And process, it turns out, is exactly what refinement produces. The question worth asking is not whether something is original. It is whether the refinement added enough to justify the distance from the source.

Where AI Borrows from Humans

AI adopts language, frameworks, and ideas the same way Gino Wickman and Mark Winters borrowed from Michael Gerber. Fluidly, efficiently, and without attribution. Gerber and Wickman had human motives for the omission. AI has no motive at all. It absorbs, synthesizes, and outputs. The origin gets stripped in the process.

When someone asks an AI tool to explain how to scale a business, the response sounds like a distillation of Gerber, Collins, Drucker, and a dozen others, reworded, restructured, and presented as if the ideas emerged from nowhere in particular. No footnotes. No lineage. No acknowledgment that a human being spent years developing what just got summarized in forty seconds. The ideas travel without their authors.

AI is trained on the accumulated output of human thinking and reflects it back without attribution. There is no intent in the omission. That is simply how the architecture works. Unless a user asks where an idea comes from or who originated a framework, the source rarely surfaces. The output feels authoritative because it is clean. Stripped of its origins, an idea sounds timeless. It sounds like it was always obvious. That is the erasure.

The irony is that the frameworks being borrowed most heavily are the ones built around clarity, ownership, and accountability. Gerber’s work. Collins’ work. (see source links below). The thinkers who insisted on knowing where things come from. 

The Distinctions That Process Cannot Make

Following a process does not require discernment. That is both the power and the problem.

A person can execute a checklist. AI can execute it faster, at scale, without fatigue or complaint. But execution and discernment are not the same thing. Process tells you what to do next. Discernment is what makes you question whether next is worth doing.

Without it, a process can be followed into the wrong outcome. The steps get completed. The boxes get checked. The metrics get reported. And somewhere in that compliance, the judgment call that no flowchart accounts for gets skipped because it was never in the system to begin with.

The employee quietly unraveling does not show up on the dashboard. The performance numbers that look off for reasons no report captures. The moment where something feels wrong but nothing in the checklist flags it. These are not gaps in the process. They are limits of what process is designed to see.

Discernment is not a step you add. It is a habit of attention, noticing what was not anticipated, sitting with discomfort before moving to the next task, weighing what is measurable against what is happening. That is not something you can document and hand off. And it is not something that gets more reliable because the system around it does.

AI may replace jobs that are process-oriented. AI cannot replace human discernment.

Sources

note: AI used in researching this article

Michael Gerber — The E-Myth Revisited https://www.michaelegerber.com

Jim Collins — Good to Great https://www.jimcollins.com

Peter Drucker — Management: Tasks, Responsibilities, Practices https://www.drucker.institute

Gino Wickman — Traction / EOS https://www.eosworldwide.com

Mark Winters — Rocket Fuel https://rocketfueluniversity.com

Where do humans shine over AI and mechanical processes?  Answer this.

P.S.

Dear Gino and Mark,

This letter was prompted because of an email from Sharran Srivatsaa.

First, I want to acknowledge the genuine value you have brought to thousands of business owners through your work. The framework you built around the Visionary and Integrator relationship is insightful and has helped many founders finally understand why they feel so alone at the top.

I write with one respectful piece of feedback.

The term ‘Integrator’ does a quiet disservice to the very people it is meant to describe.

When you trace the word back to its Latin root ” integrare ” it means to combine parts into a whole. That is a mathematical and mechanical concept. It belongs to systems and machines, not to human beings.

The person in this role is often the most capable and committed person in the company. They carry enormous responsibility, exercise real leadership, and make consequential decisions every single day. They deserve a title that reflects their humanity and authority.

Compare how the two roles land:

Visionary — inspiring, human, full of dignity.
Integrator — mechanical, functional, cold.

That asymmetry, I believe unintentional, quietly diminishes the very person your framework depends on.

And because you named it in a book, people repeat it. It spreads into job postings, performance reviews, org charts, and daily conversation then each repetition further embedding the mechanical framing into how these individuals are seen by their teams, their founders, and perhaps most damaging frame, how they see themselves. A word repeated often by many people becomes a belief.

There is a further consequence worth naming. Today, many of the people performing this role are talented professionals in the Philippines and other countries, hired remotely at a fraction of what a domestic hire would earn. They are doing serious, skilled, leadership-level work and because the title itself sounds operational and mechanical rather than executive and human, it becomes easier to justify paying them less, titling them less, and valuing them less. The language enables the under-compensation. A person called a Director of Operations commands respect and fair pay. A person called an Integrator can be quietly slotted into a lower tier even when the work is identical.

Your framework helped founders see they needed this person. But the title you gave that person has made it easier for the world to undervalue them.

A title like Chief of Staff, Second in Command, or Director of Operations would give that person the dignity their work earns them.

Your concept is sound. The name simply does not honor the human being behind it.

I share this with respect for your work and genuine hope that it is useful.

Warm regards,
Sherrie Rose