TL;DR: “Work on the business, not in it” gets repeated constantly and defined almost never. It is not about stepping back or thinking big. It is a specific category of work: reviewing what broke, documenting what you already know, fixing recurring friction, and improving systems that are already running. If you have 2 hours a day, that is enough. Here is what those 2 hours actually look like.
Most founders have heard this advice. Work on the business, not in it. It sounds clear until you sit down to do it and realize nobody told you what the work actually is.
Research from The Alternative Board found that the average entrepreneur spends 68% of their time on day-to-day operations. Only 32% goes toward structural or strategic work. That is not because founders are unaware or undisciplined. It is because “work on the business” is advice without a task list.
This post gives you the task list.
What Does “Working On the Business” Actually Mean?
Working on the business means spending time on the structure of how work gets done, not on the work itself. It is any activity that makes future work faster, less dependent on you, or less likely to break. The output is always something that changes how the business runs: a documented process, a fixed friction point, a recurring review, an updated template.
It is not strategy. It is not planning. It is not a vision exercise or a coaching call.
Most definitions stay too vague because they describe the goal (be more strategic) instead of describing the task. The in-the-business work has visible, immediate deadlines. The on-the-business work does not. So it keeps getting pushed until nothing actually improves.
The line between them is clear. In-the-business work is what keeps things running today: delivering a service, answering client questions, reviewing proposals, approving invoices. On-the-business work is what makes that delivery easier, faster, or less dependent on you being in the room. Both are real work. One just has a deadline attached and the other does not.
Why 2 Hours a Day Is a Realistic Frame, Not a Stretch Goal
Two hours a day is not an aspirational number. It is a practical one.
SCORE research found that the average small business owner has only 1.5 hours of genuinely uninterrupted, highly productive time per day. SCORE That is your actual ceiling. Everything else gets fractured by messages, context switching, and operational fires.
The goal is not to find more time. It is to use the time you already have on a different category of work. Two hours across a day is four 30-minute blocks spread across a week. That is a realistic operating cadence, not an idealized one.
The bigger obstacle is not time. According to The Alternative Board, the biggest reason small business owners work more than they should is because they feel like there are some tasks only they can handle (32%). Thealternativeboard That belief is a signal: knowledge is still trapped in one person’s head. Getting it out is the first category of on-the-business work.
What Are the Four Categories of On-the-Business Work?
On-the-business work falls into four categories: reviewing what broke, documenting a process you repeated, fixing one recurring friction point, and improving something already running.
That is the complete list. If the task you are doing does not fit one of those four, it is either in-the-business work or adjacent thinking that has not produced anything operational yet.
Here is what each one looks like in practice.
Review what broke. Once a week, look at what went wrong. A client question that took too long to answer. A task that fell through the cracks. A handoff that required your involvement when it should not have. You are not trying to fix everything. You are looking for patterns. A useful frame from the How to Build Systems guide: pick the activity that hurts the most and has the most potential value if improved. That is your starting point.
Document a process you repeated. If you did something more than twice this week, it belongs somewhere outside your head. Not a 15-page manual. A brief outline: what triggers the task, the key steps, who handles each one, when it is done. Instructions that stay in your head require your team to ask you every time. Externalizing them, even roughly, removes that dependency.
Fix one recurring friction point. Not ten. One. Pick the thing that comes up repeatedly and costs your team time to navigate each week. Build the fix, test it, move on. This is not a project. It is a 30-minute task with a clear output.
Improve something already running. A process that works but has a step you always change. A template that needs updating. A decision rule that could be clearer. The system does not need to be broken to be worth improving.
How to Fit This Into a Real Operating Day
The answer is shorter slots, not longer ones. Do not try to block 2 hours on a Tuesday. Block four 30-minute windows across the week, one per category.
Same day, same time, recurring. If the slot is not automatic on your calendar, it will not happen. This is not a discipline problem. It is a memory problem.
Chapter 6 of The Self-Managing Business frames this precisely: improvement is a 15-minute recurring rhythm, same time every week, looking at what broke and picking one thing to fix. Not a meeting. Not a planning session. A standing appointment with your own operations. The guide makes a sharp point: the businesses that actually improve are the ones that scheduled the time before it felt convenient. The rest kept waiting for a calm week that never arrived.
Chapter 9 goes further. The systems that last are the ones that do not rely on memory. A recurring task in your project tool. A note at the top of your issue log. A line at the end of every template that tells you when to update it. If your system requires you to remember to use it, it is already fragile. Get the full guide if you want the framework for wiring all four categories together so they run automatically.
One practical note: when you are unsure which direction to take a process improvement, do not map out every possible scenario. Pick the one unknown variable and test it. That is a 30-minute task, not a 3-hour planning session.
What Does Not Count as Working On the Business?
On-the-business work has a visible output. If you cannot point to what changed, it was not on-the-business work.
Thinking about strategy does not count unless it produces a decision you can act on. Reading a business book does not count unless something in how you operate is different afterward. A coaching call does not count unless a process, document, or system changes as a result.
The clearest test is this: can you describe what changed? A documented process, a fixed friction point, a blocked calendar event, an updated template. If the answer is no, you spent time on something adjacent to the business, not on it.
Most of what gets labeled “on-the-business work” is valuable thinking that never gets converted into an operational output. The fix is not to stop thinking. It is to add one step at the end: write it down and change something.
At The Admin Workshop, the framing is simple. Most operational problems are not effort problems. They are structure problems. The thinking exists. The knowledge exists. What is missing is a system that captures it and makes it usable by someone other than you.
How Do You Know If It’s Working?
You will not see it on a dashboard. You will feel it in how many times per day someone asks you the same question.
When on-the-business work is actually happening, your team asks fewer repeat questions. Problems you fixed stay fixed. The same issue stops showing up in a different form. You spend less time being the person with the answer and more time on work that genuinely requires your judgment.
The clearest signal is what does not happen: a task that used to land on your plate stops landing there. A question that used to come to you gets answered without you.
For a more concrete measure, keep a short issue log. One line per problem that required your involvement when it should not have. If the log gets shorter over time, the work is producing results. If it stays the same length or grows, the on-the-business hours are not sticking yet.
Want more breakdowns like this? The blog covers the operational layer that keeps small businesses running without constant firefighting. Or work with me directly if you want to build this into your week with support.
Frequently Asked Questions
Working in the business means doing the tasks that keep operations running today: delivering a service, handling client questions, approving invoices. Working on the business means improving the structure that supports those operations: documenting processes, fixing recurring problems, reviewing what broke. Both are necessary. In-the-business work always has an immediate deadline and will win unless you protect time for the other category.
It falls into four activities: reviewing what broke last week, documenting a process you repeated, fixing one recurring friction point, and improving something already running. Each fits in a 30-minute block. The goal is not a major project. It is one small, concrete output per session that makes future work easier or less dependent on you.
Two hours a day is a useful frame, not a hard target. SCORE research shows the average owner has about 1.5 hours of truly uninterrupted productive time per day. Four 30-minute blocks spread across the week is a realistic starting point. Consistency matters more than volume. One hour per week done without skipping produces more operational improvement than 4 hours done occasionally.
Any change that makes a process faster, less dependent on one person, or less likely to produce errors qualifies. Writing down a process that exists only in someone’s head. Updating a template based on something you changed three times in a row. Creating a decision rule so a question does not have to escalate to you. Fixing a handoff step that causes repeated confusion. The output must be tangible. Thinking about an improvement does not count until something in the workflow actually changes.
The time does not come from adding hours. It comes from redirecting them. Replace one reactive hour per week, not a full day. Block four 30-minute recurring slots and treat them as unavoidable. If they keep getting pushed, that is a signal: your operations are too dependent on your constant presence. That is exactly the problem on-the-business work is designed to solve. Start with one session per week. Fix one thing. See what changes.
3 responses to “What Working On the Business Actually Looks Like When You Have 2 Hours a Day”
[…] Working on the business starts with knowing what’s breaking, not with knowing what category of founder you are. The same is true for qualification. A demographic profile is a shortcut that skips the most important question. […]
[…] vendor audit is exactly the kind of on-the-business work that doesn’t feel urgent until the math adds up. Pull your contracts once. Note the renewal […]
[…] whole point of working on your business instead of constantly in it is to make room. Room for the thinking that requires your actual brain. Room to breathe between […]