Operations is the operating system of the business

Most companies treat operations like a back office.

It's where the support tickets get answered, the vendors get paid, the systems get maintained, the spreadsheets get reconciled. Important work, but adjacent to the real business. Strategy lives somewhere else. Revenue lives somewhere else. Customer experience lives somewhere else. Operations runs in the background.

That framing is wrong, and it gets more wrong as the company grows.

Operations isn't a function. It's the operating system that everything else runs on. Strategy, revenue, customer experience, and execution don't exist in separate boxes. They run through the same underlying infrastructure — the systems, cadences, handoffs, dashboards, and accountability mechanisms that connect what the business is trying to do with what it actually delivers.

When that operating system is working, the company gets faster. Decisions happen sooner. Forecasts hold. Customers feel taken care of. Teams execute without escalating every ambiguous situation up the chain. The business compounds.

When the operating system is broken, the company gets heavier. Growth creates drag instead of leverage. Forecasts become narrative instead of operating tool. Customers feel the gaps. Teams build workarounds. Leaders make decisions from partial information.

The company may still grow. Strong product, real market, talented people — those can carry a business for a while even when the operating model is unclear. But the complexity compounds faster than the system can absorb it. At some point, growth becomes harder than it should be, and nobody can quite say why.

Here's the test for whether your operating system is working.

• Forecasts. Are they an operating tool, or a story you tell the board? If your forecast is wrong by more than 15% on either side most quarters, the issue isn't sales effort. It's that the forecasting process doesn't reflect how the business actually runs.

  
  

• Customer experience. Are NPS, retention, expansion, and renewal trending in the right direction without heroics? If your customer team is constantly running fire drills to save accounts, the operating model has gaps that the team is absorbing personally.

  
  

• Cross-functional decisions. When a decision needs to happen across sales, product, and operations, does it happen in days or weeks? If your major cross-functional decisions are taking three meetings and a Slack thread, the accountability system isn't doing its job.

  
  

• Founder time. What does the CEO spend their week on? If it's still individual deal escalations, hiring fires, and operational triage, the operating system hasn't matured enough to absorb that load. Founder time is the leading indicator of operating maturity.

  
  

• Team confidence. Do people closer to the work believe the systems above them work? If your best people are quietly working around the official process to get things done, that's a signal — and it's almost never about the people.

None of these are sales problems, operations problems, or product problems on their own. They're operating system problems. And they don't get fixed by adding more strategy, more headcount, or more process.

They get fixed by understanding how the pieces actually connect, and building the mechanisms that hold the connections together.

That's the work that doesn't have an obvious owner. Most companies don't have a head of "how the business runs." They have a head of sales, a head of operations, a head of customer success, a head of finance — each running their own function, each measured on their own metrics. The connections between them get managed by escalation, intuition, or accident.

The companies that scale well are the ones where someone is paying attention to the operating system itself. Not the functions in isolation. The system that connects them.

That's where the leverage is. And it's where the work is hardest to see until the company starts to feel it.