The instinct to act

When something is not working in a business, the pressure to act is immediate. Leaders feel it from their boards, their teams, and their own sense of urgency. That pressure often translates into a rapid move toward solutions — new systems, restructured teams, revised processes — before anyone has spent adequate time understanding what is actually causing the problem.

This is one of the most consistent patterns in underperforming improvement programmes. The solution is confidently deployed, and the underlying issue remains largely untouched. Six months later, the organisation finds itself back at the same table, this time with a more expensive problem and a team that has lost some of its confidence in the organisation's ability to change.

Good improvement work does not begin with solutions. It begins with rigorous, honest diagnosis.

What diagnosis actually looks like

Diagnosis in an operational context is not simply a matter of interviewing stakeholders or reviewing a set of KPIs. It requires a deliberate effort to distinguish between symptoms and causes — a distinction that is easy to describe but harder to execute in practice.

A symptom is what you can observe: declining margin, missed delivery milestones, increased rework, high staff turnover. A cause is the underlying condition that is generating those symptoms. The same symptom can have fundamentally different causes. High rework in a manufacturing environment might indicate a training problem, a design problem, a materials problem, or a supervision problem. Each of those demands a different response. Treating them the same way will produce no lasting improvement.

Effective diagnosis involves asking questions that go deeper than the surface presentation. Where exactly in the process is the breakdown occurring? At what frequency? Under what conditions? What has changed in the environment — in personnel, in volume, in systems — that might be contributing? Who is closest to the problem, and what do they observe that leadership does not?

The diagnostic phase is also where measurement discipline matters. Organisations often operate on assumptions about performance that turn out to be inaccurate once data is properly collected and analysed. Anecdote and pattern recognition have their place, but they are no substitute for understanding the actual numbers — where waste sits, where time is lost, where quality breaks down.

The gap between symptoms and root causes

One of the most common diagnostic failures is stopping one level too soon. The team identifies a symptom, traces it to an adjacent cause, and declares the root cause found. In reality, they have identified a secondary symptom — one that has its own upstream driver that has not yet been examined.

Consider a business experiencing consistent delays in client deliverables. The obvious cause might be identified as insufficient capacity in the team responsible for delivery. The proposed solution — hire more people — seems logical. But if the underlying cause of the capacity shortfall is a process that generates excessive internal rework, or a scoping practice that consistently underestimates effort, adding headcount will not resolve the problem. It will distribute the same dysfunction across a larger team at greater cost.

This kind of premature diagnosis is not a failure of intelligence. It is a failure of process. Without a structured approach to tracing causes upstream, and without the discipline to keep asking why rather than accepting the first plausible answer, even capable teams will stop short of the real insight.

Common diagnostic mistakes

Several patterns emerge repeatedly in organisations that struggle with effective diagnosis.

The first is confirmation bias. When leadership has a pre-existing hypothesis about what is wrong — often shaped by recent events, visible problems, or the influence of a particular senior voice — the diagnostic process becomes a search for evidence that confirms that hypothesis rather than a genuine inquiry. Information that challenges the prevailing view gets discounted or overlooked.

The second is the tendency to diagnose from a distance. Senior leaders reviewing dashboards and receiving filtered reports are not in a position to observe where work actually breaks down. Effective diagnosis requires proximity to the process — time spent on the floor, in the workflow, with the people doing the work. The further the diagnostic work is conducted from where the problem actually lives, the less reliable its conclusions are likely to be.

The third is a failure to involve the right people. The individuals who understand the details of a broken process most accurately are usually not those presenting at executive meetings. They are the team members who encounter the friction every day, who have developed workarounds and informal practices to compensate for system failures. Their perspective is often the most valuable input available, and it is frequently the last to be formally sought.

How senior operators approach it differently

Operators who have spent time inside complex environments develop a different diagnostic instinct. They have seen enough failures to recognise the difference between a problem that looks straightforward and one that requires more careful investigation before any action is taken. They know which questions to ask, how to read the signals that a formal review might miss, and how to create the conditions in which the people closest to the problem will speak candidly.

Senior experience also brings calibration — an understanding of what good looks like in a given function or environment. Without that reference point, it is easy to mistake an ordinary level of operational friction for a problem requiring a major intervention, or to accept a genuine performance gap as normal because no better benchmark has been observed.

What good diagnostic work unlocks

When diagnosis is done well, it changes the nature of the improvement work that follows. Resources are directed toward the causes that actually matter. Interventions are designed with a clear understanding of the conditions they need to address. The risk of deploying a solution that does not work — with all the cost, disruption, and loss of momentum that entails — is substantially reduced.

Good diagnosis also builds credibility. When teams can see that the analysis behind a proposed change is thorough, evidence-based, and free from the usual shortcuts, their confidence in the improvement effort increases. That confidence is not a soft outcome. It is one of the most reliable predictors of whether change will actually take hold in an organisation.

The instinct to act quickly is not wrong. The organisations that improve most consistently are the ones that apply that urgency to getting the diagnosis right — before the solutions are designed.