What 38 Years of Operational Work Taught Me About What Actually Matters.

← Back to Insights

I have spent 38 years in operational work. Hospitality, my own marketing agency, consulting across small businesses, construction, cleaning companies and hotel companies, now pet services and technology. One underlying problem, every time: the gap between what a business intends to do and what it actually does.

This is not a bio piece. It is the list I wish someone had handed me when I was twenty years in and thought I knew most of it. I did not. Here is what I know now.

The Business You Think You Have and the Business You Actually Have Are Not the Same Business

This is where most operational failures start. The owner has a clear picture of how the business runs. The team has a different experience of how it runs. The clients have a third experience. And the gap between all three is where problems live.

The business you think you have is based on your intention: the standard you set, the process you described, the culture you believe you have created. The business you actually have is based on what happens on a Tuesday afternoon when you are not there.

I have never walked into a business where those two things were perfectly aligned. I have walked into businesses where the gap was small — and those businesses ran well. And I have walked into businesses where the gap was enormous — and those were the ones in trouble, usually without understanding why. Closing that gap is the ongoing work of building and maintaining operational alignment.

Good People Do Not Make a Business — Systems Make a Business

This is the one that surprises owners most, because it sounds like I am undervaluing people. I am not.

Good people are essential. But good people in a bad system will produce inconsistent results. They will compensate for the system's gaps — which means you will get the benefit of their individual competence without building any organizational competence. And when they leave, you get nothing but a vacancy.

A good system with average people produces consistent results. A good system with good people produces excellent results — and those results belong to the business, not just to the individuals. (More on what makes a system survivable in How to Build a Workflow That Survives the People in It.)

The Problem Is Almost Never Where It Looks Like It Is

Revenue down? The owner looks at marketing. Staff turnover high? The owner looks at pay. Client complaints up? The owner looks at service quality. These are reasonable instincts. They are wrong more often than they are right.

In 38 years I have found that the presenting problem is rarely the root problem. Revenue problems are often pricing problems, which are often cost structure problems, which are often staffing problems. Turnover problems are often culture problems, which are often leadership problems, which are often systems problems.

The skill is in following the chain upstream. Finding the cause behind the cause behind the cause. And then fixing that, not the symptom. This is harder than it sounds and requires more honesty than most owners are comfortable with. Because following the chain upstream often leads to the owner.

The Constraint Is Often the Owner

I say this not as criticism but as the most useful thing I can say to any business owner who is working harder every year but not getting proportionally better results.

The owner who will not delegate because nobody does it as well as they do is the ceiling on the business's growth. The owner who makes exceptions to the standard because it is easier in the moment is the reason the standard does not hold. The owner who avoids difficult conversations with the team is the reason the team avoids difficult conversations with clients.

This is the hardest thing I tell the owners I work with. And it is the most useful. (More on this in What to Do When You Are the Hardest Part of the Business to Fix.)

AI Does Not Change the Fundamentals — It Amplifies Them

I spent 38 years building operational systems without artificial intelligence. Manually, painstakingly, with clipboards and checklists and long Sunday evenings going through the week's operations.

What I built those systems to do — capture knowledge, maintain standards, surface problems early, distribute information to the right people at the right time — AI now does in a fraction of the time with far greater reach.

But here is what has not changed: if the fundamentals are not right — if the standards are not clear, if the business does not know what it is trying to do, if the owner is the bottleneck — AI amplifies the dysfunction, not the excellence. A bad process automated is a faster bad process. The fundamentals come first. The technology amplifies them. That sequence matters.

What I Am Most Proud Of

Not the businesses I have worked with where everything went right. The businesses where it went wrong first. The ones where I walked in when things were hard, found the real problem underneath the stated problem, helped the owner see something true about their business that they did not want to see — and then watched them do something about it. That is the work. It is not glamorous. It is not fast. But when it lands, it holds. And a business that holds is worth building.