Your business has grown. Now your operations need to catch up.

Don't try to organize everything at once.

Start with what's creating the biggest problem today. Where are customers being affected? Where is the company losing time? What keeps creating mistakes? What requires your constant involvement? What are employees complaining about?

Those problems give us somewhere to start. Once we understand the processes behind them, we can prioritize improvements instead of trying to redesign the entire company.

Start by identifying exactly what depends on you. Is it information? Approvals? Customer relationships? Problem solving? Technical knowledge? Scheduling?

Once we know why the business needs you for those things, we can determine what can be documented, delegated, standardized, or handled differently.

The goal isn't to remove you from every decision. It's to make sure you're involved because your judgment is actually needed — not because nobody else knows what to do.

I don't assume it's either one until I understand what's happening.

If several good employees struggle with the same task, I start looking very closely at the process. Are expectations clear? Is the information available? Are responsibilities defined? Does the employee have the right tools? Does the process itself make sense?

Sometimes it absolutely is a performance problem. But fixing the process first makes it much easier to distinguish between a system problem and an individual one.

First, I would look at why they need to ask.

Maybe the process isn't documented. Maybe authority isn't clear. Maybe information is difficult to find. Maybe the answer changes depending on the situation. Or maybe employees have learned that asking the owner is faster than using the existing process.

The solution depends on the reason. The objective is to give employees enough information and authority to handle appropriate decisions without making them guess.

Some do. But you don't need a procedure for everything.

I would document processes where consistency matters, mistakes create meaningful problems, training takes too long, or important knowledge currently depends on one person.

The SOP should also match the work. Sometimes a checklist is more useful than five pages of instructions.

I usually start with processes that are important, frequent, inconsistent, or heavily dependent on one employee.

I also pay attention to processes where mistakes are expensive or customers are directly affected. If nobody knows how to run payroll except one employee, that's probably more important to document than how the office orders coffee.

Documentation should follow business risk and value.

I would compare the documented procedure with what employees actually do.

Sometimes employees aren't following a process because they weren't trained properly. But sometimes they're not following it because the process doesn't work. Maybe it's outdated. Maybe it requires unnecessary steps. Maybe the workaround is actually faster.

Before assuming employees are the problem, I want to understand why the workaround exists.

I would look at capacity before making that decision.

How much work needs to be done? Where is the team spending its time? Is the workload consistently higher than available capacity? Or is a significant amount of time being consumed by inefficient processes, manual work, rework, or unnecessary administration?

If we improve those things and the workload still exceeds capacity, then you have much stronger evidence that another employee is needed.

Because adding employees doesn't automatically remove work from the owner.

If responsibilities aren't clearly transferred, employees may perform the work but still come back to you for every decision. Growth can actually create more work for the owner if the business doesn't develop processes, authority, and accountability along with the additional employees.

Sometimes the next step isn't another hire. It's building a better operating structure around the people you already have.

You shouldn't need to monitor every minute of someone's day. You need visibility into responsibilities, priorities, workload, and results.

What is the employee responsible for? What are they currently working on? What is due? What's blocked? What was completed?

Depending on the work, that may be managed through project tools, operational metrics, schedules, regular reporting, or another simple system. The goal is visibility, not surveillance.

Not necessarily. Spreadsheets are extremely useful.

The problem starts when a spreadsheet becomes a critical business system that only one person understands, contains uncontrolled information, or requires hours of manual updates.

I don't replace spreadsheets simply because they're spreadsheets. I look at whether they're still the right tool for the job.

Maybe. But software isn't the first place I start.

I want to understand what problem you're trying to solve. If your current process is unclear, putting it into a new platform can create a more expensive version of the same problem.

Sometimes the company needs better software. Sometimes it needs to use the software it already owns better. And sometimes the process needs to change before technology is involved at all.

Start with repetitive work.

Where are employees spending time copying information, preparing reports, searching documents, organizing information, or completing other predictable administrative tasks? Those may be opportunities.

But I don't recommend implementing AI simply because it's available. It should solve a real business problem and produce enough value to justify the effort and risk involved.

Look for something repetitive enough to matter but simple enough that you understand the process.

I wouldn't make your most complicated, business-critical process your first automation experiment. Find something employees do frequently that follows a reasonably predictable pattern.

Measure how much time it consumes today. Then determine whether automation could meaningfully reduce that work. Start with value, not novelty.

First, determine what each meeting is supposed to accomplish. Is it for decisions? Coordination? Status updates? Problem solving?

If the meeting exists primarily so everyone can read information to each other, there may be a better way to share that information.

I don't believe the goal should be "fewer meetings" just because meetings are unpopular. The goal is to make sure every meeting has a reason to exist.

Accountability starts with clarity. People need to know what they're responsible for, what result is expected, when it's expected, and what authority they have to accomplish it.

Then there needs to be visibility and follow-up.

It's difficult to hold someone accountable for something that was never clearly assigned in the first place.

Start tracking the fires.

If the same types of problems keep appearing, that's valuable information. Instead of only asking "how do we fix this today?", start asking "why does this keep happening?" That's where process improvement begins.

You may never eliminate every unexpected problem, but you can stop treating recurring problems as if they're unexpected.

The ones that help you run your business.

That sounds simple, but businesses often track numbers because someone told them those are the metrics they should have. I want to know what decisions you're trying to make — sales? profitability? capacity? inventory? customer retention? project performance? turnaround time?

Start with the decisions and work backward to the information. A dashboard with five useful numbers is better than one with fifty numbers nobody acts on.

Yes, but I don't approach cost reduction by automatically cutting people or resources.

I first look at where the business is consuming time and money without getting enough value in return. That could be rework, excess inventory, inefficient workflows, duplicate software, unnecessary administrative work, poor scheduling, recurring mistakes, or other operational issues.

Sustainable cost improvement usually comes from making the operation better — not simply spending less.

Yes. Actually, that's often when an outside perspective is most useful.

You may know something is wrong because you're working too many hours, customers are waiting, employees are frustrated, or the business feels harder to manage than it should.

You don't need to diagnose it before contacting me. Tell me what you're experiencing. Then I'll start following the process.

Not necessarily.

The question isn't how many employees you have. It's whether an operational problem is costing enough time, money, or opportunity to justify fixing it.

A ten-person business can have a process problem that costs thousands of dollars. And smaller businesses often have an advantage: changes can sometimes be implemented much faster because there are fewer layers involved.

That's not my approach.

I want to understand what's already working before changing anything. Small businesses often have processes that developed for very good reasons.

The objective isn't to replace everything with a textbook system. It's to keep what works, understand what doesn't, and improve the parts that are making the business harder to run.

It starts with a conversation. Tell me what's happening — maybe you're overwhelmed, maybe employees aren't clear on responsibilities, maybe customers are waiting too long, maybe the company has grown and things that used to work no longer do.

From there, I follow the work. I look at the processes, people, information, systems, and available data to understand where the problem actually starts.

Then we prioritize what needs attention and develop improvements that make sense for the size and reality of your business. I'm not trying to make your small business operate like a Fortune 500 company — I'm trying to make it operate like a better version of your business.