Moving from Project Participant to Project Lead: A Guide for UK Clinicians

Introduction

Many clinicians start their quality improvement (QI) journey by participating in projects led by others. This hands-on experience is invaluable, providing insight into methodologies, data collection, and the practicalities of change within the demanding NHS environment. However, the step up to leading a project brings a different set of challenges and responsibilities.

This resource is designed for clinicians across all grades – from junior doctors and trainees seeking to enhance their CVs and contribute more meaningfully, to SAS doctors and consultants looking to formalise their leadership in improvement. We will explore the critical differences between participation and leadership, and provide a structured approach to equip you for success as a QI project lead.

Why This Topic Matters

Developing leadership skills in quality improvement is crucial for several reasons within the NHS:

• Driving Sustainable Improvement: Effective project leaders are essential for translating ideas into sustainable change, which is vital for patient safety, efficiency, and staff well-being.
• Career Progression and Portfolio Development: Leading a QI project demonstrates initiative, leadership, and a commitment to improving healthcare delivery – all highly valued attributes for career progression, annual reviews, and consultant appraisal.
• Empowerment and Engagement: Taking ownership of a project can be highly rewarding, fostering a sense of empowerment and deeper engagement with the wider organisational goals.
• Addressing Local Challenges: Clinicians often identify areas for improvement within their own departments or trusts. Leading a project allows them to directly address these issues, tailoring solutions to local contexts.

Moving into a leadership role requires not just an understanding of QI methodology, but also a grasp of project management, stakeholder engagement, and team dynamics. It’s an opportunity to shape your clinical environment and make a lasting positive impact.

Practical Explanation: The Shift from Participant to Lead

The fundamental difference between a participant and a lead lies in responsibility and scope. While participants focus on specific tasks, a lead is accountable for the entire project's success or failure.

As a Participant, you typically:

• Execute assigned tasks (e.g., data collection, literature search, attending meetings).
• Contribute ideas and insights.
• Follow the project plan and timelines set by the lead.
• Report progress and challenges to the project lead.
• Focus on your specific area of involvement.

As a Project Lead, you are responsible for:

• Defining the Project: Identifying the problem, setting clear aims, and defining the scope with input from stakeholders.
• Team Formation and Management: Recruiting, motivating, and managing a multidisciplinary team.
• Stakeholder Engagement: Identifying key stakeholders, communicating effectively, and securing buy-in and resources.
• Project Planning: Developing a detailed project plan, including methodology (e.g., PDSA cycles), timelines, resources, and risk assessment.
• Data Management and Analysis: Ensuring robust data collection, analysis, and interpretation to demonstrate impact.
• Communication and Reporting: Regularly communicating progress, challenges, and successes to the team, stakeholders, and relevant governance bodies.
• Troubleshooting and Problem Solving: Addressing unexpected issues, adapting plans, and maintaining momentum.
• Sustainability and Spread: Planning for the long-term sustainability of the changes and identifying opportunities for wider spread.
• Governance and Approval: Navigating local governance processes, including audit department, clinical governance, and information governance requirements.

This shift demands a broader skillset encompassing leadership, communication, organisation, and problem-solving, alongside your clinical expertise.

Common Pitfalls for New Project Leads

Transitioning to a leadership role can be challenging. Awareness of common pitfalls can help you navigate them more effectively:

• Lack of Clear Aim/Scope: Starting without a well-defined problem statement and project aim can lead to 'scope creep' and a lack of focus.
• Insufficient Stakeholder Engagement: Failing to involve key individuals or departments early on can result in resistance, lack of resources, and ultimately, project failure.
• Over-reliance on Self-Sourcing: Assuming you must do everything yourself. Delegating and empowering team members is crucial.
• Poor Communication: Inadequate or infrequent communication with the team and stakeholders can lead to misunderstandings, disengagement, and missed opportunities.
• Neglecting Data: Not collecting enough baseline data, using inappropriate metrics, or failing to regularly analyse data means you won't be able to demonstrate impact or understand what is working.
• Ignoring Local Governance: Bypassing or not understanding local audit, clinical governance, or information governance processes can stall or even halt a project.
• Sustainability Blind Spot: Focusing only on the initial change without considering how the improvements will be maintained long-term.
• Burnout: Attempting too much too quickly without adequate support can lead to exhaustion and demotivation.

Step-by-Step Approach to Becoming a Project Lead

Here’s a practical framework to guide your transition:

1. Identify Your Project Idea

• Look for Pain Points: What frustrates you or your colleagues? Where do you see inefficiencies or patient safety concerns? (e.g., delayed discharges, medication errors, communication breakdowns).
• Align with Strategic Goals: Does your idea align with departmental, trust, or national priorities (e.g., targets from GIRFT, NHS England, CQC themes)? This helps secure buy-in.
• Start Small: Begin with a manageable project. A focused, small-scale improvement with tangible results is more achievable and builds confidence.

2. Initial Scoping and Groundwork

• Define the Problem: Clearly articulate what the problem is, who it affects, and why it matters. Use data where possible (e.g., local audit data, incident reports).
• Formulate an Aim Statement: Use the SMART (Specific, Measurable, Achievable, Relevant, Time-bound) framework. For QI, a common format is 'We aim to [achieve what] by [how much] by [when] for [who/where]'.
• Identify Key Stakeholders: Who will be affected? Who has power/influence? Who has resources? (e.g., ward managers, consultants, pharmacists, IT, patients, commissioners).
• Literature Review: What has been done elsewhere? Can you adapt existing solutions? Look at NICE guidance, Royal College publications, and specialist society recommendations.

3. Secure Support and Resources

• Engage Your Supervisor/Manager: Discuss your idea, seek their guidance, and gain their explicit support. This is often the first and most critical step.
• Consult Your QI/Audit Department: Seek advice on methodology, governance requirements, and potential support (e.g., statistical help, project templates).
• Recruit Your Team: Identify enthusiastic colleagues from different professional groups who can contribute. A multidisciplinary team is often more effective and resilient.
• Build the Business Case (Informally): Be ready to articulate the 'why' – in terms of patient benefit, safety, efficiency, or cost-effectiveness.

4. Plan Your Project in Detail

• Choose a Methodology: Adopt a recognised QI methodology (e.g., Model for Improvement with PDSA cycles). Lazomis has resources on these.
• Develop a Driver Diagram/Logic Model: Map out the link between your aim, primary drivers (what needs to change), and secondary drivers (specific interventions).
• Select Measures: Define clear process measures (how well is the new process working?), outcome measures (what is the ultimate impact on patients/service?), and balancing measures (are there any unintended negative consequences?).
• Create a Timeline: Break down the project into manageable phases with realistic deadlines for each PDSA cycle.
• Risk Assessment: What could go wrong? How will you mitigate these risks?

5. Implement, Test, and Adjust

• Start Small (PDSA Cycle 1): Test your changes on a small scale (e.g., one patient, one shift, one ward). This minimises risk and allows for rapid learning.
• Collect and Analyse Data: Regularly review your chosen measures. Is the change having the desired effect? Use run charts or control charts to visualise data over time.
• Learn and Adapt: What did you learn from the first cycle? Refine your intervention based on the data and feedback. Then, plan the next PDSA cycle.
• Document Everything: Keep a clear record of your plans, actions, data, and learning.

6. Sustain and Spread

• Standardise the Change: Once the improvement is robust and tested, embed it into routine practice (e.g., update protocols, change workflows, provide training).
• Monitor Long-term: Continue to monitor key measures to ensure the improvement is sustained.
• Share Your Success: Present your findings at local meetings, trust-wide events, or national conferences. Consider publishing your work as a service evaluation or audit.
• Identify Opportunities for Spread: Could this improvement benefit other areas or departments?

Example in Clinical Practice: Improving Discharge Summaries

A Registrar on a Cardiology ward identifies that discharge summaries are often delayed, incomplete, or contain errors, leading to readmissions and frustrated GPs. Their current role is a participant in a larger trust-wide project, but they decide to lead a focused improvement within their own department.

1. Identify Project Idea: Improving the quality and timeliness of discharge summaries for Cardiology patients.
2. Initial Scoping:
   • Problem: 25% of discharge summaries for cardiology patients are sent to GPs >48 hours post-discharge, and 15% contain significant errors (e.g., wrong medication, missing follow-up plan) based on a local audit.
   • Aim: To reduce the proportion of cardiology discharge summaries sent >48 hours post-discharge to <10% and reduce significant errors to <5% within 6 months.
   • Stakeholders: Cardiology consultants, junior doctors, ward managers, medical secretaries, pharmacists, GPs.
3. Secure Support: They discuss with their supervising consultant, who is supportive. They meet with the Clinical Governance lead and the Audit Department, who provide advice on data collection and local pathways for project registration.
4. Plan: They form a small team including a junior doctor, a medical secretary, and the ward sister. They decide on a PDSA cycle approach:
   • P (Plan): Introduce a 'Discharge Check-list' to be completed by the discharging doctor and cross-checked by the ward sister before final sign-off. Test this on one consultant's patients for two weeks.
   • D (Do): Implement the checklist.
   • S (Study): Collect data on summary timeliness and errors for these patients. Hold a debrief meeting with the team and participating doctors/nurses.
   • A (Act): Initial data shows minor improvement but feedback highlights the checklist is too long. They adapt the checklist to be more concise and integrate it better into existing EHR templates. They plan the next PDSA cycle for all cardiology patients on one side of the ward.
5. Implement, Test, Adjust: They continue iterative PDSA cycles, using weekly data from the audit department to track progress. They present their progress at the departmental mortality and morbidity meeting.
6. Sustain and Spread: After 6 months, the aim is met. They work with IT to embed the revised checklist into the electronic health record and produce a brief training session for all new junior doctors. They present their findings at the trust's QI conference and submit an abstract to a national cardiology meeting.

How Lazomis Can Help

Lazomis provides a range of tools and resources to support clinicians stepping into project leadership:

• QI Project Setup Guides: Our structured templates guide you through defining your project, setting aims, and identifying stakeholders, ensuring you start on a solid foundation.
• Data Collection and Visualisation: Tools for systematic data collection and creation of run charts or control charts help you monitor progress effectively and understand the impact of your interventions.
• Learning Modules: Access to educational content on core QI methodologies (e.g., PDSA cycles, driver diagrams, stakeholder analysis) can deepen your understanding and equip you with the necessary skillset.
• Collaboration Features: Facilitate communication and document sharing within your project team, streamlining workflows and enhancing team cohesion.
• Resource Library: Explore examples of successful projects and practical advice from other clinicians, offering inspiration and guidance.

Lazomis supports your journey by providing the frameworks and practical support needed to manage your project efficiently, allowing you to focus on leading your team and making meaningful improvements.

This resource supports, but does not replace, clinical judgement. Local policy, formulary and specialist advice should be followed.