Leadership before the title

Why this matters

Many doctors imagine leadership as something that begins after appointment to a named role. In practice, services often depend on doctors who coordinate uncertainty, notice recurrent risk, influence colleagues, preserve continuity and improve how work is done. The absence of a title does not make that contribution less real. It may, however, make the contribution less visible, less supported and harder to sustain.

For SAS and locally employed doctors, this distinction is especially important. A doctor may have extensive clinical knowledge and be the person whom colleagues approach when a service is under pressure, yet still be excluded from meetings where priorities, resources or roles are decided. Recognising leadership before the title is therefore not about flattering people. It is about seeing where responsibility already sits and deciding whether authority, time and accountability are properly aligned.

Start with the work before the identity

A useful starting question is not 'Am I a leader?' but 'What work is happening here?' Describe the situation in observable terms. Perhaps a ward repeatedly loses important information at transfer, junior doctors are uncertain about escalation, a clinic has an avoidable delay, or different professional groups understand the same plan differently. Then identify who is helping the team understand the problem and organise a response.

This approach prevents leadership from becoming a personality label. A quiet doctor can lead. A person with a forceful presence may fail to lead if others become less able to contribute or if decisions are not converted into safe action. The relevant evidence is the relationship between purpose, contribution and consequence: what needed to change, what the person did, how others were involved and what happened afterwards.

Where ordinary leadership appears

Clinical work contains frequent leadership moments. These include setting priorities during deterioration, making uncertainty explicit, coordinating a multidisciplinary response, explaining a difficult decision to a patient or family, supporting a colleague after an incident, and deciding that a familiar process is no longer safe enough. Teaching, supervision, job planning, rota design and improvement work also contain leadership when they change how other people understand or carry out the work.

Not every useful act needs to become a project. The senior doctor who creates a reliable weekend handover may have produced more practical benefit than someone who attends a prominent committee without changing a decision. Equally, repeated rescue work can conceal a poorly designed system. The leadership task may be to stop relying on personal availability and create an arrangement that remains safe when that individual is absent.

Helpful, expert, managerial or leading?

Helpful work supports another person in completing an existing task. Expertise contributes specialist knowledge. Management organises resources, roles and processes. Leadership helps people understand purpose, make a judgement and move towards a different or more reliable future. These categories overlap, and one is not automatically superior to another. The distinction matters because each requires different authority, evidence and support.

For example, repeatedly correcting an incomplete discharge document is helpful. Explaining the clinical information that must be present is expertise. Redesigning who completes and checks the document is management. Bringing the relevant teams together, agreeing why the current process creates harm, testing a new approach and reviewing its effect contains leadership. Naming the contribution accurately prevents both inflation and disappearance.

Build an evidence habit

Leadership evidence is stronger when it records an episode rather than an adjective. 'Good communicator' is a claim. A brief account showing how a doctor brought two teams to a shared understanding, clarified a decision, secured an owner and checked the result is evidence. Useful records include the initial problem, the doctor's actual role, evidence considered, people involved, decision made, result observed and learning carried forward.

Evidence should be proportionate. A short note, meeting record, audit result, feedback email or reflective account may be enough. Do not include patient-identifiable information in an unsecured portfolio. Do not claim sole credit for collective work. Attribution becomes more credible when it names both the individual's contribution and the contribution of others.

The risk of invisible reliability

Organisations often reward the visible project while depending on invisible reliability. The doctor who quietly absorbs gaps, answers every telephone call and prevents problems from reaching senior attention may be described as dependable. Over time, that reliability can become a reason not to redesign the service, allocate development time or broaden the doctor's authority. The person becomes essential to the weakness of the system.

A responsible leader makes this pattern discussable. Instead of saying only 'I am overloaded', describe what work is being absorbed, what risk is being contained, what would happen during absence and which part requires a system response. This is not withdrawal of goodwill. It is the conversion of hidden work into information that the organisation can govern.

The SAS and LED perspective

SAS and locally employed doctors should not have to imitate a consultant identity to show leadership. Their value may arise from continuity, detailed knowledge of the service, cross-boundary relationships, education, patient understanding or experience accumulated outside a conventional training pathway. These are legitimate sources of contribution, but they still require evidence and appropriate governance.

Where an informal leadership function is recurrent, ask whether it needs recognition in the job plan, an agreed objective, protected time, access to information, a reporting route or a named role. Not every contribution should become a formal post. The key test is whether the current arrangement allows the work to remain safe, fair and sustainable.

A one-week practice exercise

For seven days, notice one moment each day when your judgement affects what happens next. Record the purpose, who depended on the decision, what you actually did and what followed. Include small moments: an escalation, a teaching conversation, a challenged assumption or a decision to pause. At the end of the week, look for a pattern rather than selecting only the most impressive example.

Choose one behaviour to test during the following week. You might state the purpose before offering the solution, invite a quieter colleague first, make the decision owner explicit or return later to check the effect. Ask one colleague a specific feedback question. This turns leadership development from a statement of aspiration into a small experiment with observable evidence.

• What problem or uncertainty was present?
• What changed because of your contribution?
• What authority or support was missing?
• What should become a reliable team process rather than personal rescue work?