Working On Your Business vs Working In It: What Actually Has to Change

Every founder has made this resolution at least twice. Less time in delivery, more time on strategy. It survives roughly a fortnight, until something urgent lands and the calendar quietly reassembles itself into what it was before.

The advice is not wrong. It is incomplete in a way that makes it unusable. Working on the business gets described as a choice about how you spend Tuesday, when it is really a question of whether the business can function while you are not in the room. Those are different problems, and only one of them responds to better time management.

Michael Gerber, who gave this distinction its language, put the test more bluntly in The E-Myth Revisited: “If your business depends on you, you don’t own a business—you have a job.”

What follows is what the phrase actually means structurally, and what has to change for it to hold past a fortnight.

What does working on the business actually mean?

It means building the structure that lets decisions get made without you.

Working in the business is doing the work the business sells. Delivering to clients, producing the thing, being the expert people paid for. It is not lesser work. For most founder-led firms it is the reason the business exists, and it is usually what the founder is best at.

Working on the business is different in kind, not in importance. It is deciding what the business sells and to whom. Establishing how work moves through the firm and who owns which outcome. Documenting the standard so somebody else can hold it. Setting the rhythm by which the business reviews itself.

The distinction that matters is not strategic versus tactical. It is whether the activity depends on you personally. Anything that only functions while you are present is work in the business, no matter how senior it looks. A founder who spends Friday afternoons on strategy that never becomes anyone else’s responsibility has not worked on the business. They have had a nice Friday.

Why do founders stay in delivery?

Because delivery is legible, urgent, and rewarding, and structural work is none of those things.

Client work has deadlines and visible outcomes. Somebody is waiting. Finishing it produces a clear sense of a day well spent. Structural work has none of that. Nobody is waiting for your decision framework. It has no deadline, no applause, and no obvious moment of completion.

There is a second reason, less comfortable. Delivery is where the founder is most confident. It is the thing they are demonstrably excellent at, and the structural work is the thing they have never done. Staying in delivery is not only easier. It feels more competent.

Both of these are understandable. Neither of them changes what the business needs.

Is the business at its ceiling, or are you?

This is the question worth separating, because founders routinely mistake one for the other.

The business appears to have plateaued. Revenue has flattened, the team is at capacity, and every attempt to grow seems to hit the same wall. The natural conclusion is that the market is saturated, or the model has a limit, or this is simply what the business is.

Usually it is not at its ceiling. It is at the founder’s ceiling, which is a different problem with a different solution. The constraint is not demand or capability. It is that everything routes through one person, and that person is now full.

The signs are consistent. Decisions wait for you rather than being made. Deliverables need your review before they ship, because the team has never been given a standard clear enough to judge readiness themselves. Clients expect your personal involvement because, explicitly or otherwise, that is what they were sold.

None of those are growth problems. They are structural ones, and adding effort to a structural problem produces a more exhausted founder, not a larger business.

Which decisions actually have to be yours?

Far fewer than currently are, and the work is deciding which ones in advance rather than case by case.

Most founder-led businesses have never made this explicit. Decisions route to the founder by default, not by design, because no one ever specified an alternative. The result is a queue, and the queue moves at the speed of one person’s attention.

The structural fix is to define, in writing, which decisions belong to the founder and which belong to a role. Not which decisions the founder is willing to hand over when busy. Which ones belong elsewhere permanently.

That usually means sorting decisions into three groups. Those that genuinely require the founder, because they set direction or carry consequence nobody else can hold. Those that belong to a role, with a defined boundary and no requirement to check first. And those that need a conversation, which should be the smallest group and the one people are most tempted to expand.

Then comes the part that decides whether any of it works. When someone makes a decision inside their boundary and reaches a different answer than you would have, the outcome gets evaluated rather than the method. A team corrected on method every time stops making decisions within a month, and will shortly afterwards be described as lacking initiative.

What has to be written down?

The standard, because a standard that lives only in the founder’s head cannot be taught, delegated, or held by anyone else.

This is the piece most often skipped, and it is the one that determines whether delegation is possible at all. Founders frequently believe nobody else can do the work to the required level. That belief is often half true, which is precisely what makes it durable. But the reason is almost never that the capability is missing. It is that the standard was never documented clearly enough for anyone to learn it.

There is a harder version of this problem worth naming. What you tolerate becomes what you allow, and what you allow becomes the standard. Not the standard described on the website or in the proposal. The actual one, which the team operates from and clients experience, whether it was designed or simply arrived.

Standards slip for a reason that has nothing to do with carelessness. Holding them is exhausting when no structure exists to make holding them the path of least resistance. Where expectations are documented, communicated, and reviewed on a rhythm, the standard becomes a function of the system. Where they are not, holding the standard requires the founder to be everywhere at once, noticing everything, correcting everything. That is not a structure. It is a founder standing in the gap where infrastructure should be.

What has to exist before you hire?

A defined outcome the role owns, a boundary around its decisions, and a documented standard for the work.

Hiring is the point where the absence of structure becomes expensive rather than merely tiring. A capable person arrives, finds no definition of what they own or what they may decide, and does the only thing available: they wait to be told. Two months later the hire is judged a disappointment, when the business never gave them anything to work inside.

Rhythm belongs in this list too. A business operating on a consistent cadence has a shared heartbeat: everyone knows when decisions get made, when information moves, when priorities are set. Without one, everything is urgent because nothing has a designated time and place, and the founder becomes the default routing point for all communication. That is the fastest available route to becoming the bottleneck in your own business, and hiring into it simply adds an inbox.

Which senior role the business actually needs is a separate question, and one worth settling before a search begins rather than after. The difference between a fractional COO and an operations manager decides which of them you are hiring.

Why do the changes never stick?

Because most attempts at working on the business are renovation theatre rather than renovation.

Renovation theatre is visible change made in place of structural change. A new website. A rebrand. A renamed offer. A reorganised team chart. It produces the sensation of transformation without the substance, and it is genuinely appealing, because the founder knows something needs to change and does not have the capacity for the structural version right now.

It sometimes works, briefly. The new brand generates energy. The reorganised team feels fresher for a few weeks. Those are not worthless outcomes; they buy time. The problem is that they postpone the structural work until it costs considerably more. A business that needed rebuilding in year two is a far simpler project than the same business in year five, after more has been built on the wrong foundation.

Three signals suggest the structural version is actually required. The setup no longer suits the stage the business is at. The same problem keeps returning in different forms, which means the system is producing it by design. And the founder has started avoiding parts of their own operation, which is usually the structure asking to be redesigned.

How do you know it is working?

By what continues in your absence.

The test is simple and uncomfortable. If the business went two weeks without contact from you, no email and no messages, what would stop moving? Things slowing but continuing means structure exists and the business needs capacity. Everything halting means there is no structure independent of one person, and that is the honest map of where the work begins.

The goal was never to make the founder less important. It is to make them important in the right places, available for the decisions and relationships nobody else can hold, rather than for the ones where they were never irreplaceable, only unintentionally necessary.

Frequently asked questions

What is the difference between working in the business and working on it?
Working in the business is delivering what the business sells. Working on it is building the structure that allows the business to deliver without you: what it sells, who owns which outcome, what the standard is, and how decisions get made in your absence.

How much time should be spent on the business?
The framing is the problem. Founders are commonly told to allocate a percentage of the week, which turns a structural question into a scheduling one. What matters is whether the time produces something that outlives the session, such as a documented standard or a defined decision boundary. An hour that does is worth more than a day that does not.

Can this be done while still delivering client work?
Yes, and for most founder-led firms it has to be. The structural work does not require withdrawing from delivery. It requires that some portion of it produces permanent structure rather than another completed task.

What should be tackled first?
The decision queue. Identify what is currently waiting for you that should not be, and define who owns it instead. That produces the most immediate relief and reveals what documentation is missing.

Where the work actually starts

Working on the business is not a scheduling decision, and it is not delegation. Delegation is a tactic: handing a task to a person on a given day. What is being described here is structural, and structure is what makes delegation possible in the first place.

Start with the two-week question and answer it honestly. What stops moving is not a list of tasks to redistribute. It is a map of where the business has been depending on one person to stand in place of a system.

That map is where Brenna & Co. begins with founder-led expert businesses, usually through a House Audit: an examination of how the business actually operates, what its foundation is genuinely made of, and which parts are load-bearing rather than decorative.