Some of my best days as an operator were the days when nobody needed me.
That probably sounds strange. We usually recognize leadership when someone steps into a crisis, makes a difficult decision, or fixes something that has gone wrong. Those moments matter. I have had plenty of them, and I have always enjoyed taking apart a hard problem and figuring out what to do next.
But a quiet day can say more about an operation than a dramatic one.
Orders leave on time. Inventory numbers match what is actually on the shelf. Customer service knows what to tell people. A promotion does not surprise the warehouse. Accounting has the information it needs. A vendor understands the next deadline. A manager makes a good decision without waiting for approval on every detail.
Nobody celebrates because nothing became an emergency.
That is part of what makes operations difficult to explain. Some of the best work shows up as problems that never happen.
The work behind an ordinary day
I did not start out planning to become an operations executive. I was not an ecommerce expert, a warehouse expert, a technology expert, or a supply chain expert.
Things just needed to get done.
So I figured them out.
One problem led to another. A warehouse problem became an ecommerce problem. Ecommerce created fulfillment problems. Growth created staffing problems. New products created inventory problems. Accounting needed better information. Systems needed to communicate. Vendors needed negotiating. Payment processors disappeared. Priorities changed.
And somewhere along the way, without really noticing it happening, I became the guy people brought problems to.
Employees came to me when they did not know where else to go. Managers came to me when a decision crossed departmental lines. The owner came to me when something needed to get done. I learned how to operate in an environment where everything could change overnight.
Over the years, I watched a founder-led media and ecommerce company grow from roughly seven employees and $2 million in annual revenue to about 80 employees and $80 million. I eventually led seven department managers across an operation handling approximately 750,000 annual orders and nearly 2,000 SKUs.
At that scale, very few problems stay inside one department.
A product decision affects purchasing. Purchasing affects cash. Marketing affects order volume. Order volume affects staffing and fulfillment. Fulfillment affects customer service. Customer service sees problems that may actually begin with the website, the product, the warehouse, or the promise made in an advertisement.
The customer does not care which department caused the problem. The customer experiences one company.
That is why good operations is usually less about controlling one function and more about connecting the entire business.
I wrote recently that growth usually breaks at the handoffs. This is the other side of that idea: when the handoffs are working, almost nobody notices them.
The warehouse learns about a promotion before the orders arrive. Customer service receives the information it needs before the calls begin. Inventory, sales, and accounting are working from numbers that agree. People know who owns the next step, what complete means, and when a problem needs to be escalated.
The result does not look dramatic.
It looks like a normal day.
A business can become dependent on heroics
There are times when an operator has to step in and rescue something. A supplier misses a deadline. A system fails. Demand exceeds the forecast. A payment processor creates a sudden problem. A decision has to be made before all the information is available.
Being able to respond to those moments is part of the job.
But constant heroics are not the same thing as good operations.
If the same type of crisis keeps happening, the goal should not be to become faster at rescuing it. The goal should be to understand why the organization keeps creating it.
Is ownership unclear? Are two departments measuring the same thing differently? Does a manager have responsibility without authority? Is important information reaching people too late? Has a temporary workaround quietly become the permanent process?
A capable leader can keep a weak system alive for a surprisingly long time. Every time something breaks, that person steps in, makes the call, and pushes the work across the finish line.
From the outside, that can look like strong leadership.
Sometimes it is.
But it can also hide the fact that the business has never learned how to operate without being rescued.
The company can become dependent on the heroics. So can the person doing the rescuing.
The danger of becoming the person everyone needs
I liked being the person people trusted with difficult problems. I liked finding an idea that could actually work. I liked watching something we built succeed. There was real satisfaction in knowing that I could take a complicated situation, find the pieces that mattered, and turn them into action.
There was also a cost.
Eventually, being the person who solved everyone's problems became part of my identity. Being needed felt like proof that I was valuable.
That is an easy trap for an operator to fall into because the behavior is often rewarded. Problems get solved. Deadlines get met. The owner is relieved. The team knows who to call.
But if every answer, approval, and difficult decision has to move through one person, that person eventually becomes part of the problem.
Managers stop building confidence in their own judgment. Employees learn to escalate instead of thinking through the issue. Decisions slow down. The leader spends so much time inside today's problems that there is little time left to prevent tomorrow's.
At some point, you have to ask whether you are solving problems or teaching the organization to send every problem to you.
That does not mean a senior operator should step away from responsibility. It means taking responsibility for more than the immediate answer.
Sometimes the right answer is to make the decision yourself.
Sometimes it is to give a manager the information, authority, and support to make it.
And sometimes it is to fix the structure that made the answer unclear in the first place.
What good operations looks like to me
Good operations is not a company where nothing ever goes wrong. That company does not exist.
It is a company where people know what matters, who owns what, and what to do when reality does not follow the plan.
It is when customer service does not have to guess what was promised.
It is when the warehouse knows what demand is coming.
It is when ecommerce, purchasing, finance, and fulfillment are not working from different versions of the truth.
It is when managers know which decisions are theirs and are expected to make them.
It is when a recurring failure becomes a reason to improve the system, not just another opportunity to blame the person standing closest to it.
It is when leaders can see what is happening without calling a meeting every time they need an answer.
And it is when the business can keep moving if one person takes a day off.
That last one matters more than many leaders want to admit.
The goal is not to remove judgment, experience, or leadership from the operation. Systems cannot anticipate every situation, and a checklist cannot replace someone who understands the business as a whole.
The goal is to make sure good judgment is not trapped inside one person's head.
People should have the information and authority to act, with a clear way to escalate the exceptions.
That is not less leadership.
It is leadership built into the way the organization works.
The operator's real job
I still love solving hard problems. That means asking questions, finding what other people may have missed, and turning a complicated situation into something the team can execute.
But I no longer believe the measure of a strong operator is how many problems require that person's personal intervention.
A better measure is what becomes possible because of the systems, people, decisions, and expectations that operator helped put in place.
Can the team move faster without becoming careless?
Can the company grow without creating the same failure at a larger scale?
Can the leader step away from the room without the work stopping?
There was a particular satisfaction when everything was working so well that nobody needed me.
If I did my job correctly, somebody might eventually look around and ask, “What does Tim even do?”
Perfect.
It meant the machine was running.
An operator's job is not to remain indispensable. It is to build something that works without needing to be rescued every day.