How to Run an Operational Diagnostic in Your Organization

Most operational problems are not mysterious. They are hiding in plain sight, in the gap between how leadership thinks work moves through the organization and how it actually moves. An operational diagnostic is a structured way to close that gap. This article describes how we approach the process at Bold Citadel Lab, and what organizations can do to prepare for one.

What an operational diagnostic is not ¶

It is not an audit. An audit checks whether processes comply with a standard. A diagnostic asks whether the processes themselves are the right ones, and whether they are working as intended. The distinction matters because the two activities require different kinds of access and produce different kinds of output.

It is also not a performance review of individual employees. The goal is to understand how the system works, not to evaluate the people inside it. We are explicit about this with every team we interview, because the quality of information we get depends on people feeling safe enough to describe what is actually happening.

The four phases of a well-run diagnostic ¶

The first phase is scoping. Before any interviews or observations, we agree with the client on which parts of the organization are in scope and what questions we are trying to answer. A diagnostic that tries to cover everything tends to produce findings that are too diffuse to act on.

• Phase 1: Scoping and question definition (days 1-3)
• Phase 2: Document review and process mapping (days 4-8)
• Phase 3: Staff interviews across multiple levels (days 9-16)
• Phase 4: Analysis, prioritization, and report writing (days 17-22)

What the output should look like ¶

The deliverable from an operational diagnostic should be a prioritized findings report, not a comprehensive inventory of everything that could be improved. The prioritization is the hard part. It requires judgment about which bottlenecks are causing the most downstream friction, and which improvements are feasible given the organization's current capacity.

A good findings report has three sections: a short summary of the two or three highest-priority findings, a longer section with supporting evidence and context for each finding, and an implementation notes section that describes what a realistic first step would look like. The last section is the one most often omitted, and the one clients find most useful.

How to prepare your organization ¶

The most important preparation is communication. Before any external diagnostic begins, leadership should tell staff what is happening, why, and what will be done with the findings. Diagnostics that are announced without context tend to generate anxiety, and anxious staff give incomplete information.

Practically, you should also prepare a list of the documents you can share: org charts, process documentation, recent performance data, and any internal reports that describe known problems. We will ask for these in the first week. Having them ready saves time and signals that the organization is serious about the work.

An operational diagnostic is most useful when the organization is ready to act on what it finds. If leadership is not prepared to make changes based on the findings, the report will sit on a shelf. The diagnostic itself is not the intervention. What happens after it is.