The Absentee/Visionary Owner Fallacy
“If a business can't run without you, you don't have a business. You have a job.”
I've heard some version of that statement for most of my career, and I've probably repeated versions of it myself. It sounds right, especially to anyone who has spent years carrying too much of their company on their shoulders. The problem is that it becomes less true the more literally we take it.
Michael Gerber probably did more than anyone to popularize the idea with The E-Myth Revisited. Gerber made an important distinction between working in your business and working on your business. His argument addressed a very real problem: the great technician who starts a company only to discover that instead of gaining freedom, he has created a bigger and more complicated job.
His answer was to build systems, processes and an organization capable of producing consistent results without everything depending on the owner. That's good advice, and so are many of the ideas that followed.
Traction gave entrepreneurs a practical framework for accountability and execution. Its Visionary and Integrator concept helped owners understand that the person who sees where the company needs to go may not be the best person to manage every detail required to get there. Lean Startup pushed another important idea forward: test assumptions, learn from customers and adapt instead of blindly following a plan.
There is a lot of good management thinking in all of this. The problem isn't the concepts. It's the hyperbole that has grown around them.
Somewhere along the way, “your business shouldn't depend on you for everything” became “a successful business shouldn't need you.” Working on the business became more important than working in it, and eventually we arrived at the idea of the visionary or absentee owner: build the right systems, hire the right people, get out of the weeds and eventually the company should operate without you.
You don't have to look very far today to find someone willing to sell you a version of that dream. It's an incredibly effective marketing proposition because, frankly, who wouldn't want it? Make money, own the company, set the vision and skip much of the grind that comes with operating it.
I think it's worth questioning that promise.
Not because owners shouldn't delegate or because systems don't work. They should, and they do. Certainly an owner shouldn't make every decision, manage every employee, approve every purchase or spend a career buried in details other people are perfectly capable of handling.
The problem is much simpler: businesses don't run themselves.
Working on the business is still working in it
The distinction between working on and working in a business is useful until we start treating the two as opposites. In practice, they overlap constantly because management is where working on the business and working in the business meet.
Consider what management actually involves: setting priorities, allocating resources, developing people, reviewing performance, solving problems, improving processes, understanding customers, maintaining standards and responding to change. Most importantly, management is how strategy gets turned into action.
Those are operational activities.
If a company is missing its sales target and you sit down with the sales leader to understand why, you're involved in operations. If margins are shrinking and you change pricing, purchasing or staffing, you're involved in operations. The same is true when you change an organizational structure that no longer supports the company's size, develop a manager who isn't quite ready for the responsibility you've given them, or adjust strategy because customer behavior has changed.
Even strategy becomes operational the moment someone tries to achieve it.
The owner of a growing business should stop doing many of the things they once did. That's part of growth. But that doesn't mean the owner leaves operations; it means their role in operations changes.
Someone who once performed much of the work begins managing the work. Eventually they manage people who manage the work. As the organization grows, the owner's attention moves toward systems, resources, managers, culture, strategy and the direction of the enterprise.
The altitude changes, and it should. The responsibility doesn't disappear.
Then there is entropy
This is the part of the absentee-owner conversation that I rarely hear discussed.
Organizations have a natural tendency toward disorder. Borrowing from the concept of entropy, maintaining an organized system requires continuing effort. Researchers have applied entropy to organizational management as a way of understanding the uncertainty, complexity and disorder organizations face, along with the continuing need for learning, adaptation, resource allocation and process improvement.
You don't need to understand thermodynamics to recognize it. Anyone who has managed a company for very long has watched it happen.
You create a good process. Then an unusual customer requires an exception, so someone develops a workaround. Eventually a new employee learns the workaround instead of the original process. Meanwhile the market changes, a manager leaves, software gets replaced, costs increase and customers begin expecting something different.
A few years later, everyone may still be following “the process,” but it looks remarkably little like the process you originally designed.
Nobody did anything malicious. The organization moved.
That's entropy, at least in the way I'm using the term here.
Businesses are particularly susceptible to it because they aren't machines. They're collections of people operating inside markets that are also changing. Employees leave, customers evolve, competitors respond, technology improves and yesterday's competitive advantage eventually becomes something customers simply expect.
Growth adds another layer because growth creates complexity. More people create more communication paths. More customers create more exceptions. More products create more decisions. More locations create more distance between leadership and the front line. Success itself can make the organization harder to manage.
Bain & Company has studied this problem extensively and describes a paradox of growth in which successful companies become larger, add complexity and begin losing some of the characteristics that made them successful in the first place.
Its research also found something worth considering. Founder-led companies in the S&P 500 produced roughly three times the indexed shareholder return of other S&P 500 companies between 1990 and 2014.
That doesn't prove founders are always better managers, nor does it prove founder involvement caused those returns. Large public companies are obviously not small businesses either. But the finding should at least make us question the assumption that the natural destination of a successful company is an increasingly irrelevant founder.
Bain's work points instead toward characteristics such as an owner's mindset, a focus on the front line and a strong sense of mission.
In other words, staying connected to the business may matter.
Systems are part of the answer, not the end of it
One of my favorite observations about management comes from Jeff Bezos. In his 2016 letter to Amazon shareholders, he described what he called “Day 2”:
“Day 2 is stasis. Followed by irrelevance. Followed by excruciating, painful decline. Followed by death.”
That's a pretty good description of organizational entropy, but the more interesting part of the letter comes later when Bezos warns about allowing process to become a substitute for results.
Every good company needs processes, and I would argue that most small businesses need considerably more process than they have. But eventually people can become more concerned with following the process than determining whether it still works. The process becomes the goal instead of the outcome it was designed to produce.
That's dangerous because every system is built from what we know at a particular point in time. When the world around the system changes, the system eventually has to change too.
This is one of the reasons I remain a fan of the thinking behind Lean Startup. Build, measure and learn, then do it again. The entire concept begins with the humility to acknowledge that we might be wrong. We develop an idea, test it against reality, measure what happens, learn something and adjust.
A system that never changes eventually becomes a liability. A playbook is a record of what worked.
Management is deciding whether it still does.
That's also why I struggle with the idea that enough systems eventually allow an owner to transcend operations. Systems don't eliminate management; good systems make better management possible. Someone still has to look at the results, notice when reality no longer matches the assumptions behind the system, develop the people, allocate resources and decide what needs to change next.
Maybe that person isn't the founder. That's perfectly legitimate. A professional CEO, president, COO or management team may assume much of that responsibility as the company grows.
But someone is doing the work.
What great operators actually did
Business history gives us plenty of reasons to think about this differently. Consider people such as Henry Ford, Sam Walton, Jeff Bezos, Larry Ellison, Mark Zuckerberg and Elon Musk. Their companies became enormous, but their involvement didn't simply disappear as those companies grew.
Their work changed.
Sam Walton obviously didn't operate every cash register at Walmart, but he remained famously interested in stores, customers, competitors and how the business actually worked. Henry Ford didn't personally assemble every Model T; his attention moved toward designing and improving the system capable of producing millions of them. Bezos eventually stopped packing Amazon orders himself, but he didn't stop thinking about customers, organizational structure, capital allocation, technology, processes or how decisions were made.
I don't think these examples prove that founders should remain CEOs forever. Some shouldn't. Nor do they suggest that an owner needs to remain involved in every detail of the company.
They suggest something more useful: successful operators learn to change how they are involved.
The same idea is present inside Traction. The Visionary/Integrator model doesn't eliminate management; it divides management responsibility. The Visionary remains connected to direction, culture, the market and important relationships, while the Integrator brings together the major functions of the organization and drives accountability and execution.
Both are operating the company, just from different positions.
Maybe the better lesson isn't that owners should eventually escape operations. Maybe they should learn to operate at the level their company now requires.
The owner can be the problem too
None of this means owner involvement is automatically good. I've spent enough time around companies to know that owners can become the biggest constraint in their own organizations.
They approve everything, second-guess managers and jump into problems their people should be solving. Some refuse to give up responsibilities because nobody can do the work quite as well as they can. Others hire talented people, tell them they're empowered and then override their decisions the moment they disagree.
That's not the kind of involvement I'm advocating. It's dependency, and it limits a company to the capacity of one person.
The objective shouldn't be to make yourself indispensable. The objective is to keep making yourself useful.
That requires something harder than installing a playbook because it requires the owner to improve.
The person capable of running a $500,000 company may not yet be capable of running a $5 million company, and the person running a $5 million company may not yet have the skills needed for $50 million. We spend a lot of time talking about scaling businesses, but the business isn't the only thing that has to scale.
The owner does too.
As the organization grows, you should become less important to some things and more valuable to others. You should make fewer decisions yourself while getting better at the decisions only you should make. You should solve fewer problems personally while becoming better at developing people who can solve them. You should spend less time enforcing processes and more time understanding whether those processes are producing the results they were designed to produce.
That isn't absentee ownership. It's becoming a better operator.
Maybe we're asking the wrong question
This is where I think it helps to forget the business advice for a moment and work through the idea from the foundation up.
Instead of asking, “How do I build a company that doesn't need me?” ask a more useful question:
“What does this company need from me now?”
If the company needs you to schedule every employee, approve every small purchase or personally handle every customer complaint, you probably have dependencies worth eliminating. Those are exactly the kinds of things systems, delegation and good managers should solve.
But perhaps the company needs you to develop your management team, understand why margins have been declining, question a strategy built around assumptions that are no longer true, allocate capital, understand customers or decide what the next stage of the company should look like.
Those aren't necessarily signs of a poorly designed business.
They may simply be your job.
This is where critical thinking matters more than any business playbook. Understand what is actually happening, identify the real constraint, change what needs changing and see what happens. Then do it again.
There can't be a permanent answer because the business you're managing today won't be exactly the same business you're managing three years from now.
Hopefully, neither will you.
There is no easy way
This may be the least marketable part of the argument, but I think business owners deserve to hear it.
There isn't a business operating system that removes the need to think. There isn't a playbook that eliminates uncertainty, an organizational chart that develops people for you, or a strategy that executes itself. There also isn't a point where a healthy company becomes immune to entropy.
You can build a business that allows you to take a month off, and you should. You can develop a management team capable of making important decisions without you. You can create systems that produce predictable results and professionalize the organization as it grows.
Those are accomplishments.
But none of them mean the business is running itself. They mean you've built a better organization, and a better organization should allow you to operate at a higher level.
That's the opportunity I think gets lost when we sell business owners the dream of becoming absentee visionaries.
Freedom shouldn't require disengagement. It should give you the ability to spend your time where your judgment, experience and leadership matter most.
There will always be employees to nurture, managers to develop, assumptions to question, customers to understand, systems to improve, resources to allocate and a desired future state that someone has to turn into reality.
That's management.
And management is operations.
Maybe the mistake was believing that building a great business would eventually free us from that responsibility. I think it offers something better: the opportunity to become better at it.
Build systems and question them. Delegate and develop people. Measure results and challenge your assumptions. Change the playbook when reality tells you it's wrong. Raise the level at which you operate as the company grows, but stay an operator.
A business doesn't become great when it no longer needs management. It becomes great when good management happens throughout the organization, whether the owner happens to be in the room that day or not.
And if you reach the point where you genuinely don't want to be involved in operating the company anymore, there is nothing wrong with that either.
Maybe you don't need another system for becoming an absentee owner.
Maybe it's time to sell.
References
- Gerber's own materials describe The E-Myth Revisited as drawing the distinction between working “on” and “in” the business, while his broader methodology describes building systems so a company can work without depending on its owner.
- Bain's Founder's Mentality research reports that its index of 115 founder-led S&P 500 companies produced about 3.1 times the indexed shareholder return of other S&P 500 companies from 1990–2014; excluding technology companies reduced the multiple to about 1.8. Bain also identifies frontline focus, an owner's mindset and mission as characteristics associated with founder-oriented companies.
- Jeff Bezos's 2016 shareholder letter is the primary source for the “Day 2” quotation. More importantly for the argument, Bezos warns specifically about process becoming a proxy for outcomes and advocates customer obsession, adaptation to external trends and high-velocity decision making.
- Eric Ries identifies the Build-Measure-Learn cycle, validated learning and pivoting based on evidence as central concepts of Lean Startup.
- EOS describes the Visionary as maintaining a pulse on the market, managing major external relationships, inspiring people, creating the company's vision and protecting it. It describes the Visionary/Integrator combination as central to an entrepreneurial company's ability to execute the vision rather than as a mechanism for eliminating management.