top of page

Diagnose Before Prescribing

louiejudd6
Sep 4
3 min read

Leadership and organisational difficulties are often met with familiar interventions before the problem has been properly understood. Coaching, training, restructuring and wellbeing initiatives are not interchangeable remedies. A credible response begins with diagnosis.


Organisations rarely lack interventions.


There is always a workshop that can be booked, a course that can be purchased, a restructure that can be proposed or an app that promises to improve wellbeing. The harder question is whether any of them address the problem people are actually experiencing.


Imagine several managers report that they feel overwhelmed. One interpretation is that they need time-management training. Another is that priorities are unclear. A third is that vacancies have redistributed work without removing responsibilities. A fourth is that decision-making has become so centralised that routine work repeatedly stalls. A fifth is that one senior relationship is generating avoidable rework across the organisation.


The same visible symptom can emerge from very different causes.


This is why one of the central principles behind Sustainable Leadership Studio is simple: diagnose before prescribing.


Diagnosis here does not mean reducing organisational life to a neat score or pretending that one survey can reveal an objective truth. Organisations are social systems. Different people occupy different positions within them, see different parts of the work and experience the same arrangements differently.


A useful diagnosis therefore gathers perspectives rather than searching for a single convenient story. It looks for patterns across workload, resources, role clarity, relationships, decision-making, culture and wider pressures. It asks where experiences converge, where they conflict and what those differences may reveal.


Most importantly, it distinguishes between presenting problems and underlying conditions.


“Poor communication” may describe almost anything: missing information, unclear ownership, avoidance of conflict, excessive meetings, inaccessible systems or leaders communicating decisions that have not actually been made. “Low morale” can similarly conceal grief after restructuring, perceived unfairness, impossible demands, a lack of progression or simple exhaustion.


If the description remains vague, the intervention will probably be vague too.


The temptation to prescribe quickly is understandable. Action feels reassuring. Commissioning a programme creates a visible response and may demonstrate that concerns have been heard. Yet premature action can cost money, consume time and weaken trust—especially when staff have explained a problem repeatedly and receive another generic solution.


This does not mean organisations should spend months analysing while people continue to struggle. Diagnosis should be proportionate. Sometimes a focused set of conversations, a review of existing information and a clear decision are enough. At other times, recurring or organisation-wide difficulties warrant deeper enquiry.


The purpose is not endless investigation. It is better action.


A diagnostic approach also clarifies the role of coaching. Coaching is powerful when the client has meaningful agency: choices to examine, relationships to navigate, patterns to understand or action to take. It is less honest when used to help an individual tolerate conditions that require organisational intervention.


Sometimes coaching is the right response. Sometimes it is one part of the response. Sometimes the ethical recommendation is a different specialist, a change in work design, or a leadership decision that cannot be outsourced to personal development.


The discipline lies in not deciding the answer before listening to the problem.


Good intentions do not make an intervention appropriate. Familiarity does not make it relevant. And speed does not always make it decisive.


Before asking which programme to buy, which coach to hire

or which structure to redraw, ask a more basic question:


What problem are we actually trying to solve?


 
 
 

Comments


bottom of page