13 Leadership and service contribution

Leadership can be visible in ordinary work

You do not need a formal leadership title before you can demonstrate leadership behaviour. Coordinating a difficult decision, helping colleagues agree a safer process, supporting a learner or ensuring that an unresolved concern reaches the right person can all involve meaningful contribution.

The challenge is to describe the action and its effect. “I am a team leader” may describe a role, but it does not explain how you lead. “I brought the relevant colleagues together, clarified the disagreement and helped the team agree responsibility for the next action” gives the reader something to assess.

Capability, authority and opportunity are distinct. Being able to contribute does not always mean having permission or resources to make a decision. A useful leadership evidence account explains both the contribution and its limits.

Leadership responsibility should be matched by authority, time, information and access to the people who can act. Consultant status is not a general test of leadership suitability, and SAS status is not a reason to exclude an otherwise suitable doctor. Check any genuine statutory, contractual or role-specific condition separately. The same approach protects a new consultant from being assumed competent in every management task simply because of appointment. [S26, S43]

When a service relies on an SAS doctor to lead, it should make the remit and decision rights explicit. An invitation to help or to influence colleagues may be valuable, but it does not confer authority over budgets, staffing or another person's job plan. Seek the authority needed for the responsibility rather than accepting an indefinite mismatch.

Identify the decision and your role

Start with the service problem. What needed to change or be resolved? Who was affected? Who had authority? What part did you undertake? These questions prevent a leadership account becoming a list of meetings attended.

You may have initiated the discussion, analysed information, represented a clinical perspective, negotiated an agreement or followed through on a decision. Each can be important. Do not claim authority you did not hold, or understate a contribution simply because another person chaired the meeting.

Where responsibility was delegated, describe what was delegated and what remained with the service lead. A doctor can demonstrate sound leadership by recognising when a decision needs authorisation. Acting beyond authority is not automatically evidence of initiative.

The account should also identify colleagues' contributions. Leadership evidence does not require a story in which everyone else was passive. Helping a team use its expertise is often central to the work.

QI01 through a leadership lens

The improvement chapter describes QI01's method and hypothetical results. Here the relevant question is how the doctor helped the team make and revise a decision.

The doctor discussed the unclear follow-up information with the people who prepared and used discharge summaries. Different colleagues had different concerns. Some wanted a clearer prompt; others were concerned about duplicating work. The doctor helped define the issue and contributed to a test that could be reviewed.

When staff identified duplication, the team changed the design. The doctor's leadership evidence might explain how the concern was heard, how the competing priorities were discussed and how agreement was reached. It should not merely repeat the improvement percentages.

The strongest account identifies the doctor's contribution and the evidence for it. A meeting record, version history or colleague's specific feedback may corroborate the account. The project remains a team achievement.

Influence without formal authority

Many service improvements require cooperation from people you do not manage. Influence then depends on understanding the problem, listening to concerns and making a proposal that others can examine. It is rarely achieved by stating that the change is obviously necessary.

Ask what matters to each group. A clinical team may focus on safety, an administrative team on workflow and a manager on capacity. These concerns can be compatible if they are made explicit. A proposal that ignores one group may fail even when its clinical purpose is sound.

Your evidence can show how you changed your own approach after hearing another perspective. That is not a loss of leadership. It may demonstrate judgement and adaptability.

Where a decision cannot be made within the group, identify the appropriate authority and present the issue clearly. Do not let lack of authority become hidden responsibility for an outcome you cannot control.

Courses and applied learning

A leadership course can provide language, frameworks and an opportunity to reflect. Its contribution becomes clearer when you explain how you used the learning. What did you notice differently? What conversation did you prepare differently? What did you change in your response to disagreement?

Select a leadership course for a defined learning need. Before attending, identify a suitable opportunity to apply the learning and obtain feedback. Attendance can support a record of professional development; a claim about leadership practice needs evidence of what the doctor subsequently did.

A useful evidence record might connect one learning point to a subsequent service activity and feedback. The certificate can remain supporting material. It should not carry a claim that only applied practice can demonstrate.

Do not collect courses indefinitely because the next step is uncertain. Return to the gap analysis. If the missing element is opportunity or authority, another course may not resolve it.

Leadership includes follow-through

An intervention is incomplete if the concern is raised but no one knows what happens next. Follow-through may involve confirming the decision, checking whether an action occurred or identifying that the problem remains unresolved.

This does not mean taking personal responsibility for every service problem. It means being clear about ownership and ensuring that your contribution reaches a useful conclusion. A record can state that the decision was referred to the appropriate lead and that the outcome remains pending.

Avoid presenting unresolved work as a completed achievement. Equally, do not assume that lack of a favourable outcome makes your contribution worthless. A well-reasoned concern and appropriate escalation can be meaningful evidence even when the organisation has not yet acted.

The reflection should examine what you learned about the system and your own approach, without making unsupported claims about other people's motives.

Fair access to leadership opportunities

Opportunities are not always advertised or allocated transparently. Some doctors are repeatedly invited to contribute while others are told to demonstrate leadership without access to meaningful work. This can create an evidence gap that is actually an opportunity gap.

Make a specific request linked to a service need. Ask what contribution is required, what authority it carries and who will provide feedback. A small, defined responsibility can be a useful starting point if it is real rather than tokenistic.

Working pattern should be considered in the design. If the only meeting occurs outside a doctor's agreed work, explore how participation can be made feasible. Do not equate willingness to attend unpaid with leadership potential.

The service should also avoid giving responsibility without resources. A doctor asked to lead a change needs access to the people and decisions that make it possible.

Writing the leadership evidence record

Use T07 to explain the context, action, contribution, result, limits and learning. Be concrete about the decision. Replace “improved teamwork” with the specific change you observed or the feedback received. If the effect was not measured, say so.

Ask an appropriate colleague to comment on what they actually observed. A useful statement may describe how you clarified a disagreement or coordinated an action. It should not claim a broad transformation on the basis of one meeting.

Map the evidence proportionately. A single project may illustrate collaboration and influence, but it does not establish every leadership capability or all aspects of clinical responsibility.

Show what you did when people disagreed

Imagine a service discussion in which one group requests more information in a handover and another fears duplication. The doctor first clarifies the decision the handover must support, then invites each group to explain the information it needs and already has.

The team distinguishes missing information from information that is difficult to find, proposes a smaller test and identifies who can authorise it. The doctor’s evidence concerns how they clarified the disagreement, changed the proposal after listening and followed through—not a claim to have controlled the whole service.

Seek specific corroboration of the behaviour observed, such as drawing in a quieter colleague, explaining a decision or completing an agreed action. Existing evidence of leadership should be examined before prescribing another course.

What the service needs to arrange

Provide meaningful opportunities, clear authority and relevant feedback. Recognise contribution within the role and working arrangements. Where a doctor is asked to lead a project, identify who can authorise decisions beyond the doctor's remit.

Support should include honest feedback about the approach, not simply praise for volunteering. A doctor needs to know whether their contribution helped the team and where it could improve.