What is an Operational Diagnostic and what do you actually get?

An Operational Diagnostic is a focused investigation into what is affecting performance and what should change.

That sounds straightforward. It is still reasonable to ask what somebody will actually do, how much of your team’s time it will take and whether the report will become another document living quietly in a folder.

This guide explains DeaconOps’s offer, its limits and the decisions it is intended to support. It is for business owners and leaders who can see operational symptoms but want a clearer explanation before committing to change.

1. What business problems can a Diagnostic investigate?

A team works harder while the backlog grows. Customers keep chasing. Managers disagree about what is wrong.

The business may have plenty of explanations and very little agreement about which one should receive the budget.

A Diagnostic examines how work, information, decisions and accountability move through the operation. Typical symptoms include delays, inconsistent performance, repeated correction, unclear ownership and increasing dependence on workarounds.

The investigation should be scoped to a meaningful problem. It is not a promise to review every department, control and system in a few days.

A useful starting question is: which operational outcome is disappointing, who is affected and what decision does the business need to make next?

2. When is a Diagnostic useful—and when is it unnecessary?

You do not normally need a detailed investigation to replace a light bulb.

You may need one if the lights keep failing and nobody agrees whether the problem is the bulb, the fitting or the wiring.

A Diagnostic suits uncertainty about the cause, particularly where the issue crosses teams or previous fixes have moved the pressure elsewhere. It can also support a decision about recruitment, process redesign or technology.

If the problem and required change are already clear, a defined improvement project may be more appropriate. If the business needs somebody to manage operations regularly, occasional investigation will not provide that ongoing capacity.

The scope should reflect the decision required, rather than making diagnosis a compulsory first purchase for every client.

3. How are the problem and scope agreed?

A request to “review everything” can produce an impressive amount of looking and a limited amount of understanding.

Boundaries make the review more useful.

Before work begins, agree the operational question, affected processes, intended decisions and available evidence. Identify the people who need to contribute and any constraints on access or timing.

The scope should specify what the review includes, its deliverables and where further investigation would require additional agreement. Data availability and operational complexity influence what can reasonably be established.

This creates a shared expectation of the work. If evidence reveals a different issue, discuss the implications rather than silently expanding the assignment.

4. What happens during the operational review?

The process document is a useful introduction. The team member who says “that is not quite how it happens” is also worth hearing.

A Diagnostic needs both.

DeaconOps speaks with relevant people, reviews available information and follows work through the actual operation. Depending on scope, that may include examining queue age, handovers, decisions, recurring manual tasks, performance measures and returned work.

Sampling delayed and successful items helps identify conditions associated with different outcomes. Stakeholder views provide context, while records and observation help test the explanations offered.

The aim is to connect symptoms with evidenced causes. It is not to begin with a favoured framework and search for a reason to apply it.

For more on that reasoning, read how to find the real cause of poor operational performance.

5. What does the diagnostic report contain?

“Communication needs to improve” may be true. It is also a recommendation capable of surviving indefinitely without inconveniencing anybody.

A practical report should make the issue and response more specific.

The DeaconOps report sets out the findings, evidence and explanation of why the problem is happening. It connects the visible symptoms with their operational causes and considers the effect on customers, teams and performance.

Recommendations are prioritised and arranged into a sequenced action plan. Important dependencies, uncertainties and further questions should be clear, rather than disguised by confident wording.

The report supports decisions and delivery. It does not guarantee that implementation will succeed without the resources, ownership and follow-through needed to make the changes work.

6. How are recommendations prioritised?

A list of thirty actions can leave a busy manager with thirty new reasons to postpone starting.

Sequence is part of the value.

Consider customer impact, operational risk, constraints on completion, dependencies and the effort required. Some issues need immediate containment; others need a test or a more substantial project.

A recommendation should explain what changes, why it is expected to help and how the effect can be checked. Where evidence is limited, identify the uncertainty and the next step needed to resolve it.

The findings session gives the business an opportunity to challenge the reasoning and discuss what is practical. Agreement is more useful when people understand the basis for the priority.

7. How do three consultancy days work over two weeks?

Three consultancy days delivered over two weeks means three days of consulting effort across that period.

It does not mean a consultant sitting in the business for ten working days, powered entirely by the meeting-room biscuit supply.

The time covers the agreed review, stakeholder discussions, analysis, report and findings session. The exact sequence depends on access, availability and scope.

The elapsed period provides room for conversations, information gathering and analysis. The business still needs to make agreed people and information available; delays in access can affect the timetable.

Larger or more complex operations may need a different scope. That should be discussed and priced before the additional work begins.

8. What does the starting price include?

A price is more useful when it explains the work attached to it.

Otherwise, comparing consultancy proposals becomes an exercise in guessing how much analysis is hiding behind the word “review”.

DeaconOps’s Operational Diagnostic starts from £2,250 + VAT. The standard arrangement includes three consultancy days delivered over two weeks, covering the operational review, analysis, diagnostic report and findings session.

That is a starting scope, not a universal fixed price for any size of business. More complex requirements are agreed in advance.

The review is intended to establish what needs to change. Detailed implementation is scoped separately where required, so the business can assess the findings before committing to further delivery work.

9. What happens after the findings session?

Sometimes the business has the people and capability to implement the recommendations itself.

That is a perfectly useful result. The report does not need to come with a consultant attached permanently.

Where additional delivery support is appropriate, Improvement Projects can help design and implement the agreed changes. Operational Reviews can provide ongoing challenge, direction and senior operational input at intervals.

The appropriate next step depends on the findings and the business’s capacity to act. A substantial leadership gap may need a different arrangement altogether.

Start a conversation if you want to discuss whether the Diagnostic fits the problem you are seeing.

Questions about Operational Diagnostics

Do we need to know the root cause before contacting DeaconOps?

No. Knowing the symptoms and the outcome you want to improve is a useful starting point. Establishing the cause is part of the investigation.

Will every team member need to be interviewed?

No. The people involved should reflect the agreed scope and the evidence needed. The review should be proportionate to the operational question.

Are implementation costs included?

The standard Diagnostic covers review, analysis, reporting and the findings session. Implementation support is agreed separately where required.

---

About the author

Dean Cain is the founder of DeaconOps, with more than 15 years’ experience across operational delivery, leadership and regulated environments. Read about the DeaconOps approach.