Problems

Recognisable operating problems.

Most operational friction in growing businesses falls into a small set of patterns. If you recognise your situation here, it is not unique—and it can be improved.

Embedded Operator / Fractional COO

The founder is the bottleneck

Every decision finds its way back to the founder. The business cannot move without their input on things they should not need to touch.

Likely causes

  • No clear ownership for recurring decision categories.
  • Unclear decision rights — who can decide what, alone versus with sign-off.
  • Exception paths that all lead to the founder.
  • Teams that have not been given real authority in their domain.

Diagnostic questions

  • Which decisions should you not be making—but do anyway?
  • What would stall if you were unavailable for a week?
  • What would your team need from you that they currently cannot do themselves?

Things that do not fix this

  • Delegation lists that do not change the routing.
  • Hiring more people without assigning ownership.
  • Trust exercises.
Smooth Sprint

Nobody owns the handoff

Work moves between teams, but the transfer point is where things fall. Follow-up loops back to the founder. Customers experience the gap.

Likely causes

  • Process defined within teams but not between them.
  • No agreed standard for what "complete" means when work leaves one team.
  • Accountability that ends at the team boundary.

Diagnostic questions

  • Where does the work sit between teams without a clear owner?
  • What does the handoff look like — what information transfers, and what gets lost?
  • How do you know when a handoff has failed?

Things that do not fix this

  • More meetings between teams.
  • A shared inbox without ownership.
  • Escalation paths that go to the founder.
Smooth Sprint

Tools do not agree

Five systems hold five versions of the same truth. No one number can be trusted until someone checks another. Data reconciliation is a part-time job.

Likely causes

  • Tools acquired for isolated needs without a data model.
  • No decision about which system is authoritative for which category of data.
  • No owner for data quality.

Diagnostic questions

  • If the CRM and the spreadsheet disagree, which one is right?
  • Who is responsible for the accuracy of your key numbers?
  • How long does it take to produce a reliable view of current status?

Things that do not fix this

  • More integrations that sync conflicting sources.
  • A new tool that repeats the problem.
  • Asking everyone to update everything.
Operating Diagnostic

Meetings have replaced management

The calendar is full. Decisions require another meeting. Information that should exist somewhere is extracted live in status calls. Nobody feels like they know what is actually happening.

Likely causes

  • No reliable source of operating information between meetings.
  • Unclear ownership means people align in the room because there is nowhere else to do it.
  • A meeting culture that substitutes for management infrastructure.

Diagnostic questions

  • What would you know without any meetings next week?
  • How many of your meetings exist because a decision or piece of information is not otherwise available?
  • Which meetings would not be necessary if ownership were clearer?

Things that do not fix this

  • No-meeting days.
  • Meeting templates.
  • Reducing the number of meetings without addressing the underlying information problem.
Smooth Sprint

Reporting is late or distrusted

By the time the numbers arrive, the decision window has passed. Or the numbers arrive but nobody is confident they are right. Or different teams report the same metric differently.

Likely causes

  • Reporting built as a separate activity rather than a natural output of the operating system.
  • No single authoritative source for key metrics.
  • Manual compilation from multiple systems with high error potential.

Diagnostic questions

  • What would you want to know by Monday morning that you currently cannot know?
  • How long does it take to produce your key operating report?
  • Who challenges the numbers, and what do they challenge?

Things that do not fix this

  • Another dashboard.
  • A BI tool that reads from conflicting sources.
  • More detailed reporting that arrives with the same lag.
Smooth Sprint

Automation has become fragile

Automations exist, but nobody is entirely sure what they do or why. When one breaks, finding the owner takes longer than fixing it. Some have been running for years on logic that no longer applies.

Likely causes

  • Automations built without documentation or assigned owners.
  • Logic that encodes a business process that has since changed.
  • No review cadence for what the automation is actually producing.

Diagnostic questions

  • Can you name every automation running in the business?
  • Who owns each one — who is responsible when it breaks?
  • When did anyone last check that the output is correct?

Things that do not fix this

  • Documenting automations after they have already broken.
  • Assuming everything is working because nothing has complained.
Smooth Sprint

AI activity without operating purpose

The business is "exploring AI" but nobody has named a specific job for it. Tools are being tested, but nothing has changed in how the work actually gets done. The effort is activity, not progress.

Likely causes

  • Starting with tool selection before defining the problem.
  • No named owner for AI applications in the business.
  • No definition of what good looks like or how to know if it is working.

Diagnostic questions

  • Can you name a specific job you want AI to do in this business?
  • How would you measure whether it is doing that job well?
  • Who is responsible for the quality of what the AI produces?

Things that do not fix this

  • More AI tool trials without a defined use case.
  • A strategy document that never becomes an operating change.
Smooth Sprint

A priority project is stuck

The important initiative has been "in progress" for longer than it should be. It keeps losing to the urgent work. Nobody is moving it. When asked, it is always nearly done.

Likely causes

  • No clear single owner for delivery.
  • Competing priorities with no governing decision.
  • Missing resources, decisions or dependencies that nobody is actively clearing.
  • A project definition that was never made specific enough to close.

Diagnostic questions

  • What would have to be true for this project to be done in four weeks?
  • Who is the single person accountable for this project closing?
  • What is the next concrete action, and who owns it?

Things that do not fix this

  • Another status meeting.
  • Adding more people without clearing the blockers.
  • Setting a new deadline without changing the conditions.

Not sure which problem to start with?

The Operating Diagnostic is designed for exactly this situation—when you know things are not working but you don't yet have a shared diagnosis.

Tell me what's not workingAbout the Operating Diagnostic