What Does a Good Quality Improvement Project Look Like in Healthcare?

What does a good quality improvement project look like in healthcare?

In practice, high-quality improvement projects share a clear set of characteristics — from well-defined aims and meaningful measurement to structured testing and strong stakeholder involvement. Yet across many organisations, there is wide variation in how improvement work is designed and delivered. Some projects achieve measurable, lasting impact, while others struggle to demonstrate change or lose momentum over time (common reasons QI projects lose momentum). Understanding what “good” looks like is essential for teams looking to move from well-intentioned ideas to reliable, high-impact improvement.

So what does “good” actually look like in practice?

1. A Clear, Measurable Aim

Every strong improvement project starts with a clear aim.

Not a broad ambition, but a specific, measurable objective that defines success.

What good looks like:

• A clearly defined population or setting
• A measurable outcome
• A timeframe for delivery

For example:

“Reduce discharge delays on Ward A from 6 hours to 3 hours by September.”

This level of clarity does two things:

• It gives the team a shared direction
• It creates a clear definition of success

Without it, projects drift.

In practice, consistently capturing and structuring aim statements across teams makes a significant difference. When every project starts with the same level of clarity, it becomes much easier to compare, prioritise and support work across an organisation. Learn more about structuring a strong aim statement.

2. A Shared Understanding of the Problem

One of the most common pitfalls in improvement is jumping too quickly to solutions.

But effective change starts with understanding what is actually happening now.

What good looks like:

• A clear definition of the problem
• Insight into current processes
• Input from those doing the work
• Use of simple tools like process maps or driver diagrams

This doesn’t need to be complex — but it does need to be deliberate.

When teams take the time to build a shared understanding, they are far more likely to design changes that work in practice.

Having a structured place to capture this thinking — not just in conversations, but in a shared, visible format — helps ensure that understanding is retained and built upon over time.

3. Meaningful Measurement

Improvement without measurement is guesswork.

But in healthcare, measurement can easily become a burden: too many metrics, too much complexity, not enough clarity.

High-quality projects keep it simple.

What good looks like:

• 1–2 outcome measures (what you’re trying to improve)
• 1–2 process measures (what you’re changing)
• Regular data collection
• Trends tracked over time

The goal isn’t perfect data. It’s useful data.

When teams can see progress as it happens, it creates momentum. It turns measurement into a learning tool, not a reporting exercise.

Making these measures visible, to the team and beyond, is critical. When data is embedded within the project itself, rather than stored separately, it becomes part of the improvement process rather than an afterthought. How to simplify measurement in QI projects.

4. Structured Testing of Change

Improvement is not about implementing solutions. It’s about testing them.

This is where structured methods like PDSA (Plan-Do-Study-Act) cycles come in — but only when used properly.

What good looks like:

• Small, rapid tests of change
• Clear hypotheses (“We think this will…”)
• Documented results and learning
• Iteration based on what is learned

For example:
Testing a new discharge checklist on one bay for one shift — rather than rolling it out across an entire ward.

This approach reduces risk, accelerates learning, and builds confidence.

The challenge is consistency. Without a structured way to plan, document and review tests, PDSA can quickly become informal and lose its value.

Embedding testing cycles into a shared system helps teams move from intention to disciplined experimentation.

5. Stakeholder Involvement

Very few improvement projects sit neatly within one team.

Changes to flow, safety, or experience almost always affect multiple roles, departments, or services.

What good looks like:

• Early identification of stakeholders
• Involvement of those affected by the change
• Multidisciplinary collaboration
• Ongoing communication

When stakeholders are brought in early, resistance is reduced and solutions improve.

When they are brought in late, progress slows.

Capturing who is involved — and ensuring that collaboration is visible and structured — helps avoid one of the most common causes of stalled projects.

6. Clear Ownership and Sponsorship

Improvement work needs both energy and authority.

What good looks like:

• A named project lead responsible for day-to-day progress
• A named sponsor who can remove barriers
• Clear roles and responsibilities

Without this, projects can become everyone’s responsibility — and no one’s priority.

Clear ownership ensures momentum.

Clear sponsorship ensures progress isn’t blocked. Learn about leadership behaviours that promote effective improvement.

When these roles are visible — not just understood locally but seen across the organisation — it becomes much easier to support teams and intervene when needed.

7. Visibility and Shared Learning

One of the biggest risks in improvement is invisibility.

When projects are tracked in isolated spreadsheets, documents or local systems:

• Progress is hard to see
• Learning is hard to share
• Support is hard to target

What good looks like:

• A central, accessible record of the project
• Clear documentation of aims, measures, tests and progress
• Visibility beyond the immediate team

This is where infrastructure matters.

When improvement work is captured in a shared platform, it becomes:

• Easier to manage
• Easier to support
• Easier to learn from

And critically, it becomes less dependent on individuals.

This is where software like Life QI shins - enabling teams to collaborate and execute their projects, whilst simultaneously providing complete visibility across the entire organisation.

8. A Clear Path to Completion and Sustainability

Many projects start. Fewer finish.

Often because “done” is never clearly defined.

What good looks like:

• Clear success criteria
• Evidence of improvement over time
• A plan to embed changes into routine practice
• A defined point of completion or transition

Sustainability doesn’t happen automatically. It needs to be designed.

That means thinking beyond the test phase:

• How will this become standard practice?
• How will it be monitored?
• Who owns it long-term?

When this thinking is built into the project from the start — and documented clearly — improvement is far more likely to stick.

Bringing It All Together

High-quality improvement projects are not defined by complexity.

They are defined by consistency.

A strong project includes:

• A clear aim
• A shared understanding of the problem
• Simple, meaningful measurement
• Structured testing
• Stakeholder involvement
• Clear ownership and sponsorship
• Visibility and shared learning
• A plan for sustainability

Individually, none of these elements are complex.

But together, they create a system that supports progress.

From Good Ideas to Real Impact

Healthcare does not lack ideas. It does not lack motivation. What it sometimes lacks is the infrastructure to turn those into consistent, reliable improvement.

When teams are supported with:

• Clear structure
• Shared visibility
• Simple tools
• And a consistent way of working

…improvement becomes more than a series of projects.

It becomes a system.

And when that happens, the gap between starting and finishing begins to close — and more ideas turn into meaningful, lasting change.