What a business diagnostic is - and is not
A business diagnostic - also called a business review, health check, or operational review - is a structured, time-bounded independent assessment of a specific area of your organisation. It is designed to answer a set of focused questions with evidence, not opinion, in a compressed timeframe.
It is not a management consultancy engagement that takes three months to tell you what you already know. It is not a presentation of frameworks. It is not a list of generic recommendations that could apply to any business in your sector.
A well-scoped diagnostic starts from where your business actually is, uses your own data, and produces findings that are specific, evidenced, and prioritised for action. If a finding could have been written before anyone set foot in your organisation, it is not a finding from a diagnostic - it is a generic opinion.
"We had been sitting on the same problems for eighteen months. The diagnostic identified the root cause in two weeks and gave us a board slide we could act on immediately. Nothing in it was a surprise. Everything in it was new."
— MD, mid-market professional services firm
The distinction between "nothing was a surprise" and "everything was new" is important. The value of a diagnostic is rarely in identifying problems nobody knew existed. It is in providing an independent, structured, evidenced basis for acting on problems that were already visible but had not been clearly framed or prioritised.
When do leadership teams commission one?
The most common triggers for commissioning an independent diagnostic:
Before a major technology decision
Platform replacements, ERP implementations, and cloud migrations are decisions that will shape the business for 5-10 years. An independent diagnostic of the current state - what actually needs fixing, and whether the proposed solution addresses the right problem - is one of the highest-return uses of diagnostic budget. The alternative is finding out after a £1m commitment that the problem was something different.
A board or investor is asking difficult questions
When a board, PE investor, or audit committee is pressing for an independent view of operational performance, cost efficiency, or programme delivery - and internal reporting is not providing satisfactory answers - an external diagnostic provides the independent assurance they are asking for.
Before a strategic decision about structure or investment
Acquisitions, market entries, operating model changes, and significant capital investment all benefit from a clear-eyed view of current operational capability. Decisions that assume a level of operational maturity that does not actually exist tend to fail in delivery. A diagnostic tests that assumption before commitment.
A programme is drifting without clear root cause
When a programme is behind, over budget, or losing board confidence - but the programme team cannot provide a credible diagnosis of why - an external review creates the objective basis for a recovery plan. Internal teams are rarely well-positioned to diagnose their own failures honestly.
A change in leadership
A new CEO, CFO, or operational director inheriting an organisation they did not build needs an independent baseline - not a view mediated through their new team's interests. A diagnostic in the first 60-90 days provides a structured starting point.
Cost pressure without clear levers
When leadership knows the cost base needs to reduce but cannot identify where to cut without damaging capability - or when previous cost reduction programmes have not held - a diagnostic focused on value and waste at process level provides the basis for targeted, evidenced intervention.
What does a diagnostic actually produce?
The specific outputs vary by scope and provider, but a well-structured diagnostic typically delivers:
Root cause findings with evidence
Not a list of symptoms - an evidenced analysis of the actual causes of the problems the diagnostic was commissioned to investigate. The distinction matters: treating symptoms is expensive and temporary. Addressing root causes is cheaper and lasting.
Prioritised recommendation set
Recommendations ranked by impact, cost, and urgency - with enough specificity that the leadership team can make a decision about whether and how to act on each one. Generic recommendations that could apply to any business are a sign the diagnostic was not sufficiently specific.
Board-ready summary
A one-page or two-page summary of findings and recommendations that can be presented at board level without modification. The standard is that a board member who was not present during the diagnostic can read the summary, understand the situation, and make a decision. If it requires explanation, it is not board-ready.
Current-state baseline
A documented, evidence-based view of current operational performance - data flows, process performance, system landscape, capacity utilisation - that becomes the reference point for measuring improvement. Many organisations lack this because it was never captured independently.
Options analysis
Where the diagnostic surfaces a decision - about a technology investment, an operating model change, or a make-or-buy question - a structured options analysis with costs, risks, and dependencies for each route. The board should receive options, not a single recommendation presented as the only choice.
Indicative business case
Where changes are recommended, an indicative quantification of the cost of those changes and the benefit - in cost reduction, risk reduction, or revenue protection - that a well-executed intervention could achieve. This is indicative, not a detailed business case, but it provides the order-of-magnitude basis for a go/no-go decision on further investment.
Why 14 days - and can it be done faster?
A 14-day timeframe reflects a specific balance: long enough to gather primary evidence through interviews, data analysis, and process observation; short enough to prevent scope creep, maintain intensity, and produce findings while they are still commercially relevant.
Diagnostics shorter than two weeks tend to rely too heavily on interview data rather than evidence, and produce findings with insufficient depth to hold up under challenge. Diagnostics longer than three weeks tend to drift in scope, produce findings that are already out of date, and cost more than the decisions they are informing warrant.
The 14-day window is not rigid - some engagements are structured differently based on access constraints or organisational complexity. But it is the right default for the majority of mid-market diagnostic scope.
What happens during the diagnostic?
The structure varies by scope, but a standard Assured Velocity Business Review follows this sequence:
Days 1-3: Scoping and data gathering
Agree the specific questions the diagnostic is designed to answer. Identify the data sources - operational data, management information, system reports, financial data - and begin collection. Conduct initial stakeholder interviews to understand the leadership team's current view of the situation.
Days 4-8: Deep analysis and evidence gathering
Systematic examination of the evidence: process observation, data analysis, additional interviews with operational managers and front-line staff, and review of existing documentation. The focus is on finding the evidence that supports or challenges the hypotheses formed in the first three days.
Days 9-11: Synthesis and findings development
Structuring the evidence into findings. Testing those findings for robustness - can each one be supported by the evidence gathered, or is it based on interview data alone? Identifying the root causes and the options for addressing them.
Days 12-13: Recommendation development and validation
Developing the prioritised recommendation set. Testing the findings and recommendations with a small number of key stakeholders to identify any significant gaps or errors of fact before the formal presentation. This is not a consensus exercise - the findings are independent - but it is a quality check.
Day 14: Board presentation
Presentation of findings and recommendations at board or ExCo level. The standard is that the leadership team walks out of this session with a clear view of the situation, a prioritised set of options, and enough information to make a decision about next steps.
What board-ready findings look like
The board-ready standard deserves its own treatment because it is where many diagnostics fall short.
A finding that is board-ready:
- States the finding in one sentence - not a paragraph, not a heading with five sub-bullets
- Can be supported by evidence in the diagnostic workpapers if challenged
- Has a clear commercial consequence - the board cares about it because it affects cost, risk, revenue, or a regulatory obligation
- Points to a specific, actionable recommendation - not "improve data quality" but "the reconciliation failures in module X are caused by Y and can be fixed by Z at a cost of £W"
- Is written in the language of the business, not the language of the diagnostic methodology
The one-page board slide is not a constraint - it is a discipline. If a finding cannot be stated clearly enough to fit on a single slide with its evidence and recommendation, it has not been thought through clearly enough.
An example of what this looks like in practice: one of the case studies on this site describes a business review that prevented a £1.8m technology purchase. The board slide from that engagement stated the finding ("the proposed platform does not address the root cause of the reconciliation failures"), the root cause ("a data integrity issue in the time-recording module"), the fix ("£15k, 6-8 weeks, within the existing system"), and the alternative ("£1.8m, 18 months, with no guarantee of resolving the underlying issue"). That is a board-ready finding.
What typically happens after a diagnostic
Diagnostics typically lead to one of four outcomes:
Decision confirmed or reversed
The most common outcome is that the diagnostic either confirms a decision the leadership team was already moving toward, or provides the basis to stop a decision that was heading in the wrong direction. Both outcomes are valuable. The second is usually the more commercially significant one.
A scoped programme of work
Where the diagnostic identifies a specific problem with a clear solution, the natural next step is a scoped programme of work to implement the recommendation. The diagnostic provides the business case; the programme delivers it.
A more detailed assessment
Some diagnostics surface an area of risk or opportunity that warrants deeper investigation than the initial scope allowed. In these cases the diagnostic output is a recommendation for a more focused follow-on review.
No further action
Sometimes a diagnostic concludes that the situation is better than leadership feared, or that the problems identified do not warrant the investment required to fix them. This is a legitimate outcome. A diagnostic that tells you not to act has saved the cost of acting unnecessarily - which is often worth more than the diagnostic itself.
What does it cost?
A 14-day Business Review with Assured Velocity is priced from £5,000. The scope and complexity of the engagement determine the final price - a review focused on a single process or technology decision at the lower end; a broader operational diagnostic or programme health check toward the upper end of the range.
The relevant comparison is not the cost of the diagnostic against the cost of doing nothing. It is the cost of the diagnostic against the cost of the decision it is informing. A £5k review that prevents a £500k commitment to the wrong technology has a 100:1 return. A £15k review that identifies £300k of annual cost savings and delivers the business case to pursue them has paid for itself before it starts.
There is also a floor on what a useful diagnostic costs. Below a certain investment level, the depth of analysis required to produce evidenced findings is not achievable in the available time. Diagnostics that are priced significantly lower than this range are typically based on interviews rather than evidence - which produces a different quality of output.
How to choose the right provider
The most important questions to ask a diagnostic provider before commissioning:
- Who will lead the engagement? A diagnostic is only as good as the judgement of the person leading it. If the answer is a team of analysts with a senior partner who reviews the output at the end, that is not senior-led work. Ask for the CV of the individual who will personally conduct the analysis and present the findings.
- What does the board-ready output actually look like? Ask for an anonymised example. If the provider cannot or will not show you what the output looks like, you cannot evaluate whether it meets the standard you need.
- Do you have vendor relationships or implementation interests? A provider that earns revenue from implementing the solutions they recommend has a structural conflict of interest. Independent diagnostic work should not lead to implementation revenue from the same provider.
- What is the guarantee? A provider confident in the quality of their work should be willing to stand behind it. Assured Velocity offers two guarantees: the diagnostic will produce a board-ready output that is presentable without modification, and if it is not useful the fee will not be charged.
- Have you worked in this sector before? Sector familiarity reduces the time spent understanding context and increases the time available for analysis. It is not essential - good diagnostic methodology transfers across sectors - but it is a genuine advantage.
"The question that mattered was not whether the diagnostic would find anything. We knew there were problems. The question was whether it would give us something we could act on at board level. It did."
— CFO, financial services firm
See what a Business Review produces.
A 30-minute scoping call to establish whether your situation is the right fit for a 14-day diagnostic - and what the output would look like. No obligation.