How to Scope a Quality Improvement Project Effectively

Introduction

Starting a Quality Improvement (QI) project requires more than just a good idea; it demands careful planning and clear definition. Project scoping is the initial, vital phase where you delineate the boundaries of your work. It involves clearly articulating what your project will achieve, for whom, and within what constraints. Without robust scoping, projects can suffer from 'scope creep' – expanding beyond initial intentions – leading to delays, resource strain, and ultimately, a failure to meet objectives.

Why This Topic Matters

In the busy NHS environment, resources are always precious – time, staff, and funding. A poorly scoped QI project can waste these resources, demotivate teams, and miss opportunities for genuine improvement. Conversely, a well-scoped project provides a clear roadmap, fosters team engagement, enables efficient resource allocation, and increases the likelihood of sustainable positive change. For trainees, mastering scoping skills is invaluable for career development, portfolio building, and demonstrating leadership in quality improvement.

Key reasons why effective scoping is critical:

• Clarity of Purpose: Ensures everyone involved understands the project's 'why' and 'what'.
• Resource Management: Helps in estimating and allocating necessary resources (time, people, data).
• Risk Mitigation: Identifies potential challenges early and allows for proactive planning.
• Stakeholder Engagement: Provides a clear narrative to engage and secure support from key stakeholders.
• Measurable Success: Facilitates the definition of clear metrics and evaluation criteria.
• Maintainability: Keeps the project focused and prevents it from becoming unmanageable.

Practical Explanation: Defining Your Scope

Scoping involves narrowing your focus from a broad area of concern to a specific, actionable project. It's an iterative process, often requiring discussion and refinement with your team and supervisor. Think of it as drawing a clear box around your problem and your proposed solution.

Key Elements of Project Scope

1. Problem Statement: What is the specific issue you are trying to address? This should be clearly articulated, often using data or observed deficiencies.
2. Aim Statement: What do you intend to achieve? A good aim statement should be SMART (Specific, Measurable, Achievable, Relevant, Time-bound).
3. Target Population/Setting: Who or what will be affected by your intervention? (e.g., 'all patients admitted to Ward 3A with community-acquired pneumonia').
4. Boundaries: What is included and excluded from your project? This is crucial for managing expectations and preventing scope creep.
5. Key Stakeholders: Who needs to be involved, informed, or consulted? (e.g., ward staff, consultants, management, patients).
6. Timeline & Resources: A realistic estimate of how long the project will take and what resources (e.g., staff time, access to data, IT support) are required.
7. Measures of Success: How will you know if your intervention has led to an improvement?

Common Pitfalls

Even with good intentions, several common pitfalls can derail a QI project during the scoping phase:

• Over-ambition: Trying to solve too many problems at once. This leads to an unmanageable project that is unlikely to achieve any of its goals effectively.
• Vague Goals: An aim statement that is not specific or measurable makes it impossible to know if you've succeeded.
• Lack of Data: Not having a baseline understanding of the problem or how to measure it.
• Ignoring Stakeholders: Failing to engage key individuals or groups who will be affected by or need to support the project.
• No Clear Boundaries: Not defining what is out of scope, leading to 'scope creep' where the project expands beyond its original intentions.
• Lack of Sponsorship/Supervision: Without adequate support from senior colleagues or managers, projects can lose momentum or face unexpected barriers.

Step-by-Step Approach to Scoping

Use this systematic approach to scope your next QI project:

1. Identify a Broad Area for Improvement

Start with an observation or concern. It might be a recurring patient safety incident, an inefficient process, or a guideline not being followed. Gather initial thoughts and anecdotal evidence.

2. Gather Initial Data and Evidence

Before narrowing your focus, collect some preliminary data. This could involve looking at existing audit reports, incident logs, patient feedback, or simple observations. This helps confirm that your perceived problem is real and significant.

• Is there a national guideline (e.g., NICE, Royal College) being underutilised?
• Are there local audit findings indicating a gap?
• What do staff or patient surveys suggest?

3. Define the Specific Problem Statement

Refine your broad area into a concise, focused problem statement. For example, instead of 'A&E is busy,' consider 'Patients with non-traumatic chest pain presenting to ED between 10 am-2 pm experience an average door-to-ECG time exceeding 20 minutes, compared to the target of 10 minutes.'

4. Develop a SMART Aim Statement

Translate your problem into a measurable aim. Use the SMART criteria:

• Specific: What exactly do you want to achieve?
• Measurable: How will you quantify success?
• Achievable: Is it realistic given your resources and timeframe?
• Relevant: Does it address an important local or national priority?
• Time-bound: When do you expect to achieve this by?

Example: 'To reduce the average door-to-ECG time for patients presenting with non-traumatic chest pain to the Emergency Department between 10 am-2 pm from 22 minutes to 12 minutes by 31st May 2024.'

5. Identify Key Stakeholders and Form Your Team

List all individuals and groups who are affected by the problem or solution. This includes frontline staff, senior management, patients, and potentially other departments. Identify who needs to be part of your core project team and who needs to be informed or consulted. Secure a project sponsor or supervisor early on.

6. Outline What's Included and Excluded (Boundaries)

Crucially, define the limits of your project. This prevents 'scope creep'.

• Included: Specific patient groups, procedures, wards, timeframes, or interventions.
• Excluded: Other patient groups, different departments, upstream/downstream processes not directly impacted, or interventions requiring significant capital investment beyond your control.

Example: If improving ECG times in ED, you might include 'all adult patients presenting with symptoms suggestive of acute coronary syndrome' but exclude 'patients under 18 years old' or 'ambulatory care pathways for chest pain follow-up'.

7. Determine Key Measures of Improvement

How will you track progress and show that your intervention has made a difference? Typically, you'll need:

• Process Measures: How well are you implementing the intervention? (e.g., percentage of staff trained).
• Outcome Measures: Has the problem improved? (e.g., average door-to-ECG time).
• Balancing Measures: Are you inadvertently causing harm elsewhere? (e.g., increase in cost, staff stress, or delays in other patient pathways).

8. Draft a Project Plan Outline

While a full project plan comes later, you should have a high-level sense of the activities involved, a rough timeline, and the resources you anticipate needing. Discuss this with your supervisor.

9. Review and Refine

Present your preliminary scope to your supervisor, team, and potentially other stakeholders. Be open to feedback and iterate. Is the scope clear? Is it achievable? Is the problem appropriately defined?

Example in Clinical Practice

Initial Observation: Junior doctors on surgical wards frequently miss early signs of sepsis due to delayed vital sign review leading to concerns for patient safety.

Initial Data Gathering: A review of local incident reports and notes from last month shows 4 instances where sepsis was diagnosed late, post-critical care outreach review, in patients with documented early warning scores (EWS) that triggered escalation but were not acted upon promptly by the ward team. Local audit data indicates only 60% compliance with hourly EWS review documentation for patients with an EWS over 4.

Problem Statement: Delayed recognition and escalation of sepsis on General Surgical Ward A is occurring in 2-3 patients per week, attributed to inconsistent hourly monitoring and review of patients with an EWS >4, leading to avoidable critical care admissions.

SMART Aim Statement: To increase compliance with hourly EWS review and documentation for patients with an EWS >4 on General Surgical Ward A from 60% to 90% by 30th September 2024, aiming to reduce critical care admissions for delayed sepsis by 50% in the following quarter.

Boundaries:

• Included: All adult patients on General Surgical Ward A with an EWS >4. Focus on the nursing and junior doctor team's adherence to a modified escalation policy.
• Excluded: Patients in critical care, patients on other surgical wards, or those with EWS scores <4. This project does not aim to redesign the EWS system itself, only compliance with its use on one specific ward.

Key Stakeholders: Ward A nursing staff, General Surgery junior doctors, Surgical Consultants, Critical Care Outreach team, QI lead, Ward Manager.

Measures of Success:

• Process: Percentage of patients with EWS >4 on Ward A receiving documented hourly EWS review.
• Outcome: Number of critical care admissions from Ward A due to delayed sepsis recognition.
• Balancing: Staff satisfaction survey regarding workload, number of critical care outreach referrals for non-sepsis concerns.

How Lazomis Can Help

Lazomis offers several integrated tools that can streamline the scoping and planning of your QI project:

• QI Project Setup Template: Our structured templates guide you through defining your problem, aim, and measures, ensuring all key scoping elements are considered from the outset.
• Data Collection Pathways: Design and implement data collection forms to gather baseline data for your problem statement and ongoing data for your process, outcome, and balancing measures.
• Stakeholder Mapping Tool: Identify and categorise all relevant stakeholders, helping you strategically plan engagement and communication.
• Driver Diagram Creator: Visually represent your theory of change, breaking down your aim into primary and secondary drivers – a process that naturally refines your project's scope and clarifies interventions.

By centralising your project information and providing structured frameworks, Lazomis helps ensure your project is well-defined, robustly planned, and set up for success from day one. This resource supports, but does not replace, clinical judgement. Local policy, formulary and specialist advice should be followed.

Key Takeaways