Field Notes · Management

Getting out of the day-to-day: an operator's approach

Most advice for owners stuck in daily operations treats it as a discipline problem: delegate more, protect your calendar, hire an assistant. I have run operations for more than twenty years. In my experience, delegation advice by itself rarely solves the underlying problem. The more durable answer is usually to redesign where decisions go and who has authority to make them.

Why you are actually stuck

Owners are not trapped in daily operations because they cannot let go. They are trapped because the business is wired to route decisions to them. Nobody defined who else can approve a price exception, release a job, resolve a customer complaint, or spend five hundred dollars, so by default, everyone asks the owner. Each question may be small, but enough of them routed to one person can consume the time that should be going to leadership.

An assistant can help manage the queue, but cannot solve the underlying decision-rights problem by itself. And willpower alone does not fix it, because the questions are real and someone with the authority to answer them still has to answer them.

The design approach, in five steps

1. Track the interruptions for one week. Every question that reaches you, in a note on your phone: what was asked, who asked, what it was about. Do not fix anything yet. You are collecting a dataset that is easy to miss when the decisions arrive one at a time.

2. Sort the list into two piles. Decisions only you can make: pricing strategy, key hires, large commitments, the direction of the company. And decisions that reach you only because no one else has the authority: the everyday exceptions, approvals, and judgment calls. The exercise shows how many decisions reach the owner simply because authority was never assigned elsewhere.

3. Give the second pile owners and boundaries. Not "use your judgment," which pushes the decision back to you the moment it gets uncomfortable, but written boundaries: the service manager resolves customer issues up to a defined cost; the estimator prices within defined margins without sign-off; anything outside the boundary comes to you, with a recommendation attached. The boundary is what makes delegation real, because it tells people exactly where their authority ends.

4. Replace interruptions with a cadence. A short weekly review of the numbers and the exceptions, with the people who now own decisions. Many of the daily questions may not be urgent; they may simply have no scheduled place to land. A standing rhythm can reduce the daily stream of non-urgent questions by giving them a place to land.

5. Count again a month later. Same tracking, one more week. If the interruption count has not dropped, revisit whether the boundaries are clear and whether the team believes the new authority is real. Route questions back to their owners, and the design starts to hold.

What this does not solve

Design gets the routable decisions off your desk. It does not fix a workflow that generates the exceptions in the first place: if every third job produces a customer issue, decision rights determine who handles the issues, and the workflow determines why there are so many. That is a different problem, found a different way, and it is usually the next thing worth looking at once your week has calmed down enough to look. That is the problem a Diagnostic finds.

Field notes describe how we think about operating problems. They are not client case studies.

Related: Six signs the operation is not keeping up with the business

If the interruption list looks unfixable from the inside

That is a reasonable moment for outside eyes.