My leadership identity: a view from the front line

My leadership identity has not emerged from choosing a theoretical model and trying to inhabit it. It has developed through caring for patients, working alongside colleagues and learning what matters when organisational complexity threatens to obscure the purpose of healthcare.

I have spent increasing amounts of time over recent months thinking about leadership: what it means, what it demands and, more personally, what kind of leader I am becoming.

It would be easy to answer that question through the familiar language of leadership theory. I could ask whether I am a transformational, collaborative, adaptive, servant or distributed leader. Each model offers something useful. Yet none of them, on its own, adequately describes leadership as I experience it from the front line of general practice.

My identity has been shaped by the practical realities of caring for patients, encountering organisational complexity, questioning decisions, building relationships and trying to turn ambitious ideas into better care. It has also been shaped by the tension between strategy and delivery, authority and influence, patience and urgency, and the desire to collaborate without surrendering the responsibility to challenge.

Through these experiences, my thinking has begun to converge around a simple philosophy:

Patients before organisations.
Clinical purpose before structure.
Relationships before pathways.
Collaboration rather than organisational control.
Distributed rather than concentrated clinical leadership.
Delivery rather than endless structural discussion.

These are not slogans. They are becoming the tests against which I judge proposals, relationships, decisions and my own leadership.

Patients before organisations

The first responsibility of healthcare leadership is to remember why the system exists.

In meetings about governance, contracts, neighbourhoods, integrated teams, organisational form and funding flows, the patient can become strangely absent. We may speak about populations, pathways and outcomes while losing sight of the person who must actually navigate the services we design.

From the consulting room, the system looks very different. Patients do not experience care as an organisational chart. They experience whether someone listens, whether professionals communicate, whether help arrives in time and whether they are passed repeatedly between services. They experience the gaps between organisations far more acutely than the organisations themselves often do.

For me, therefore, leadership must begin with a deceptively simple question:

How will this make care better for the patient?

If a proposed structure cannot answer that question convincingly, it is not yet a strategy. If organisational interests begin to outweigh clinical need, leadership must be willing to bring the conversation back to its moral centre.

Putting patients before organisations does not mean that governance, finance or organisational sustainability are unimportant. They are essential. But they are means, not ends. The organisation must serve the clinical purpose, and the clinical purpose must serve the patient.

Clinical purpose before structure

Healthcare systems are often drawn towards structural solutions. When a problem is complex, the instinct is to create a new board, role, committee, pathway or governance layer. Structures can provide clarity and accountability, but they can also create the appearance of progress while clinical reality remains unchanged.

My instinct is increasingly to begin elsewhere: with the clinical problem.

What are patients experiencing? Where is care fragmented? Which clinicians need to be in the same room? What capability already exists? What would a better service look like, and what support would allow us to test it?

Only then should we ask what structure is needed.

This principle has become particularly important in discussions about neighbourhood health and integrated working. Neighbourhoods will not succeed merely because boundaries are agreed or roles are named. They will succeed if they enable primary care, community services, secondary care, mental health services, local authorities and the voluntary sector to act together around the needs of a population.

The form should follow the purpose. When form becomes the dominant conversation, transformation risks becoming organisational rearrangement rather than clinical improvement.

Relationships before pathways

Pathways matter. They help to clarify responsibilities, reduce unwarranted variation and make care more reliable. But pathways do not collaborate. People do.

Behind every effective pathway are relationships strong enough to support honest conversation, shared problem-solving and mutual accountability. Without those relationships, a pathway may exist on paper while patients continue to encounter delay, duplication and disconnection.

This has been one of the clearest lessons of my recent work across general practice, community services and the acute sector. Progress often begins with clinicians and managers meeting each other, understanding one another's pressures and discovering a shared clinical purpose.

The language of leadership matters here. The way I speak with a GP colleague cannot simply be reproduced in a conversation with a hospital consultant, a community leader, a manager or a system executive. This is not inconsistency. It is the work of translation: finding language that allows different professional worlds to recognise their common interest without losing honesty or clinical clarity.

Relationships are part of the infrastructure of delivery. Trust allows uncertainty to be discussed. Respect makes challenge possible. Repeated contact turns institutional interfaces into human connections. Only then can pathways become living agreements rather than diagrams.

Collaboration rather than organisational control

The next phase of healthcare cannot be built by one organisation attempting to control all the others.

The challenges facing our patients, including frailty, multimorbidity, cardiovascular disease, mental ill health, deprivation and avoidable hospital use, do not sit neatly within institutional boundaries. No single organisation possesses all the knowledge, resources or relationships required to address them.

Collaboration is not the same as superficial agreement. It requires organisations to share influence, tolerate ambiguity and sometimes place collective benefit ahead of institutional preference. It also requires transparency. Collaboration becomes fragile when decisions are made elsewhere, participation is symbolic or the language of partnership conceals concentrated control.

My own leadership stance is collaborative but not passive. I want to build bridges, but I do not believe collaboration requires silence. Constructive challenge is not opposition to partnership. When exercised responsibly, it is one of the conditions that makes genuine partnership possible.

The task is to challenge without humiliating, to question without becoming cynical and to remain open to persuasion while being clear about principle. That balance is difficult. It demands both courage and self-examination, particularly when relationships, organisational interests and personal ambitions intersect.

Distributed rather than concentrated clinical leadership

Clinical transformation needs more than a single clinical voice.

No individual, however capable, can adequately represent the diversity of practices, professionals, neighbourhoods and communities within a complex health system. Leadership concentrated in too few hands may appear efficient, but it can narrow perspective, weaken legitimacy and distance decisions from the front line.

Distributed clinical leadership is not leadership without accountability. Nor does it mean that everybody decides everything. It means creating clear, connected and accountable roles through which leadership is exercised close to patients and communities. It recognises that expertise is dispersed and that the people closest to a problem often hold knowledge unavailable to those furthest from it.

For general practice, this is especially important. Everyday GPs understand the consequences of fragmented systems because they encounter those consequences repeatedly in the consulting room. Their voice should not be invited only after a model has been designed. They should help shape the model from the beginning.

This conviction informs my support for representative neighbourhood clinical leadership. It is an argument about legitimacy, inclusion, succession and the quality of decisions. A resilient system develops a wider leadership community. A fragile one becomes dependent on a small number of individuals.

Distributed leadership also asks something of me personally. If I seek greater voice, I must also make room for the voices of others. If I argue for accountability from established leaders, I must accept accountability for my own decisions. If I want authority to be shared, I must be willing to share recognition as well as responsibility.

Delivery rather than endless structural discussion

There is a point at which further discussion stops being preparation for action and becomes a substitute for it.

Frontline clinicians are understandably sceptical of transformation language when it is not accompanied by visible change. They have experienced successive initiatives, restructures and new terminology while the pressures within practices continue to rise. Trust will be rebuilt when collaboration produces something useful for patients and staff.

That is why I am increasingly drawn towards practical clinical programmes: bringing general practitioners and specialists together; developing better approaches to heart failure, frailty and complex care; strengthening multidisciplinary working; and testing models at practice level that can be evaluated, improved and, where appropriate, extended more widely.

Delivery does not mean reckless speed. Good governance, evidence, patient involvement and evaluation remain essential. But we should be honest about the difference between legitimate preparation and avoidable delay.

Small, purposeful action can generate learning that prolonged abstract debate cannot. A pilot can expose assumptions. A clinical conversation can reveal a barrier hidden by organisational language. A modest improvement for a defined group of patients can create the trust needed for wider change.

Leadership is not merely the ability to describe the future. It is the discipline of helping people take the next credible step towards it.

Leading from within, not above

Perhaps the strongest influence on my leadership identity is that I remain a practising GP.

I am not observing transformation from a distance. I experience the demand, complexity and moral weight of frontline care. I see the patient whose needs do not fit a pathway, the colleague carrying too much responsibility, the receptionist trying to navigate conflicting instructions and the gap between strategic intention and operational reality.

This creates both an advantage and a responsibility. Frontline experience gives leadership credibility only if it is used to represent more than one's own frustration or organisational interest. The task is to convert experience into insight, insight into relationships and relationships into collective action.

Leading from the front line also means accepting that much of leadership is exercised without formal authority. Influence must be earned through consistency, preparation, integrity and contribution. It means sometimes raising an uncomfortable question, sometimes bringing people together around an opportunity and sometimes stepping back so that another person can lead.

It is leadership from within the work, not leadership above it.

A philosophy still being tested

I do not regard this identity as finished. Leadership identity should not become another rigid structure. It must remain open to challenge, evidence and reflection.

There are tensions within my own philosophy. Distributed leadership can slow decisions. Collaboration can become vague if accountability is unclear. A focus on delivery can undervalue the careful work required to build durable governance. Strong clinical purpose can become paternalistic if patients and communities are not genuine partners. Even the language of patients first can become hollow unless patients have voice, agency and influence.

These tensions do not invalidate the principles. They prevent them from becoming slogans.

My continuing task is to ask whether my behaviour reflects the values I advocate. Do I listen as seriously as I challenge? Do I build trust as well as demand transparency? Do I create space for others? Am I pursuing a shared clinical purpose, or merely my preferred solution? Does my urgency enable progress, or does it sometimes make collaboration harder?

That is the deeper work of leadership identity: repeatedly examining the effect of how I actually lead.

What my leadership identity is becoming

If I had to describe my leadership identity now, I would not begin with a theoretical category.

I would say that I am a frontline clinical leader seeking to hold systems to their purpose: better care for patients and communities. I believe transformation should begin with clinical need, be built through trusted relationships, draw on leadership distributed across the system and prove itself through delivery.

I want to collaborate across boundaries without allowing collaboration to become a reason to avoid difficult questions. I want governance that enables participation and accountability rather than concentrating influence. I want structures that support clinical work rather than clinical work being distorted to fit structures. Above all, I want the patient to remain visible when organisational complexity threatens to obscure them.

This identity is being formed in consulting rooms, meetings, difficult conversations, emerging partnerships and attempts to turn ideas into care.