The Operating Diagnostic

The situation it addresses

Your business has grown, and something has shifted. Work is harder than it should be. The team is busy but important things stall. The founder is still in the middle of too much. You know things are messy—but you do not yet have a shared diagnosis of what is actually causing the mess, or where to start fixing it.

The Operating Diagnostic is for businesses in this position. It is a focused starting engagement that provides an independent, practical view of the operating system before any interventions are attempted.

Who it is for

• Founders who feel the business has outgrown the way it works but cannot yet name the primary constraint.
• Leadership teams who have different theories about what the real problem is.
• Businesses that have tried to fix individual symptoms without improvement.
• Incoming executives who want an independent view of what they have inherited.
• Investors or boards that need to understand the operating health of a portfolio company.

Who it is not for

Businesses that have already diagnosed the problem clearly and need execution help. If you know what needs to change and need someone to help change it, a Smooth Sprint or Embedded Operator engagement is a better starting point.

How it typically unfolds

The scope is always agreed before work starts. Activities that may be included:

• Founder and leadership interviews — what is actually happening and what has been tried.
• Workflow and decision mapping — how work actually moves, not how it is supposed to move.
• Tool and system inventory — what exists, who maintains it, whether it serves the business.
• Operating rhythm review — cadence, reporting, and how decisions are made and followed through.
• Role and ownership assessment — who owns what, and where ownership is absent or contested.
• Automation and applied-AI opportunity scan — where technology could remove real friction.
• Prioritised action map — what to fix first, and what to do next.

What the output typically includes

These are example outputs, not guarantees. Actual format and scope are agreed before engagement.

• A plain-language view of the operating system: what exists, how it functions, where it fails.
• Key constraints: the two or three things that are causing the most downstream friction.
• Priority sequence: immediate fixes versus structural work, with a rationale.
• Recommended next engagement or internal owner for each identified priority.

What it requires from you

• Access to the people doing the daily work, not only the leadership team.
• Openness to the diagnosis, even if it points somewhere uncomfortable.
• A named internal point of contact with the authority to arrange access.