How to build a healthcare QI project team: roles and responsibilities

Build a healthcare quality improvement (QI) project team by bringing together people who deliver the process, people who experience it, and people who can help change it. Agree a day-to-day lead, clear responsibilities, access to improvement and measurement support, and a sponsor who can resolve barriers.

This article covers team formation in the setup stage of our guide to running a successful QI project. Use the role guide, outpatient example and first-meeting checklist below to turn a list of names into a team ready to work together.

Who should be on a healthcare QI project team?

Choose members around the process you want to improve. Include the staff who do the work, patients or carers affected by it, relevant clinical or technical expertise, and someone who can support testing and measurement. Secure sponsorship with enough authority to address the barriers the team cannot resolve itself.

The Institute for Healthcare Improvement’s guidance on forming a team emphasises process knowledge, lived experience, day-to-day leadership, improvement expertise and sponsorship. The exact mix depends on the project; one person may cover more than one area.

Start by sketching the steps in the process. For each step, ask: who does this work, who receives it, and who understands why it sometimes goes wrong? This helps reveal missing perspectives that an organisation chart alone may overlook.

QI project team roles and responsibilities

Use the following roles as a starting point for discussion. They describe work that needs an owner, rather than a requirement to appoint a separate person to every title.

Project lead: coordinate the day-to-day work

The lead keeps actions moving, prepares reviews and checks that the team records what it learns. Choose someone who understands the process and has time to coordinate the work. Agree a deputy or handover arrangement so progress does not depend on one person being available.

Process owner: take responsibility for the service

The process owner is responsible for how the service operates and how successful changes will be maintained. This may be the project lead, but it need not be. Make the relationship explicit: a rotating trainee might coordinate tests while a service manager remains responsible for the process after the project ends.

Frontline members: explain and test the work

Include colleagues who perform the relevant tasks, including administrative and support roles. Ask them to explain workarounds, test agreed changes and share what happened in practice. If work differs by shift or location, arrange input from those settings before assuming one version of the process represents everyone.

Patients and carers: help define what better looks like

Invite people with relevant experience to shape the problem, aim, measures and changes. Their contribution should influence decisions, rather than only confirm a plan staff have already written. One person’s experience is valuable, but should not be treated as representing every patient.

Improvement and measurement support: help the team learn

Identify who can help frame a small test, define a measure and interpret data over time. This may be a QI coach, analyst or colleague with improvement experience. Agree specific tasks and availability; a name on the project brief is not the same as support the team can use.

Clinical or technical specialists: advise where needed

Bring in expertise relevant to the proposed work, such as pharmacy, informatics, facilities or a clinical specialty. Some specialists can contribute to particular decisions without attending every meeting. Keep their advice and any conditions attached to it in the project record.

Sponsor: remove barriers and support decisions

The sponsor provides a route to decisions about resources, priorities and issues crossing team boundaries. Agree how often to review progress and how to raise an issue between reviews. A useful escalation describes the barrier, its effect, the options and the decision needed.

How to form a QI project team: four practical steps

1. Match the membership to the project scope

Review the problem and initial boundaries before inviting people. A project about arrival-to-consultation waits needs different expertise from one about referral triage. If the scope is unclear, revisit how to choose a QI project before building a large group.

2. Agree what each person is being asked to contribute

Explain the problem, why their perspective matters and what participation involves. Discuss time for meetings, testing, data collection and preparation with members and their managers. Make space for people who question the proposed approach, as well as enthusiastic volunteers.

3. Keep a manageable working group and a wider support network

There is no single ideal team size. Keep the regular working group small enough to make decisions while covering the perspectives the project needs. Record who will be consulted at particular points and who needs updates. Revisit the membership when the work moves into another part of the pathway.

4. Set clear ways of working

Agree where actions and decisions will be recorded, how people will contribute between meetings and which changes need approval before testing. Give each action one named owner and a due date. Decide how the team will handle disagreement and invite quieter members to contribute before closing a discussion.

How to involve patients and carers meaningfully

Ask people how they would prefer to participate and what would make it possible. Offer a clear description of the role, accessible information and preparation before meetings. Discuss practical needs such as timing, remote access, interpreting support and expenses through your organisation’s involvement arrangements.

Use plain language, explain improvement terms and share questions in advance. Offer alternatives to attending every meeting, such as reviewing a proposed change or discussing experience in a smaller conversation. Show contributors what changed because of their input, including when the team could not act on a suggestion and why.

For example, a clinic team might assume that reducing the overall wait is the only priority. Patients may also want clearer updates during delays or a way to tell staff when waiting is difficult. That feedback can shape the project’s measures and tests.

Healthcare example: a team improving outpatient waiting times

This is an illustrative team, not a reported customer project.

A service has selected arrival-to-consultation waits in one outpatient clinic as its initial focus. It could organise the team as follows:

• Clinic manager: leads the project and owns the clinic process, coordinating actions and agreeing how any lasting changes will be maintained.
• Reception colleague: explains arrival recording, checks how timestamps are captured and helps test changes at check-in.
• Clinic nurse: describes preparation and patient flow, and records what happens during agreed tests.
• Clinician: advises on consultation flow and checks the implications of proposed changes for care.
• Patient partners: help identify what matters during the wait and review proposed communication changes.
• QI coach or analyst: helps define the waiting-time measure and supports review of baseline data.
• Service sponsor: helps resolve capacity or cross-department issues and reviews progress at agreed intervals.

At the first meeting, the reception colleague might take responsibility for checking timestamp completeness, the nurse for observing clinic-start routines, and the patient partners for reviewing the feedback questions. The group would agree dates and a review point, rather than assigning “collect data” to the whole team.

A first-meeting checklist for your QI project team

Use the first meeting to agree what happens next. You do not need to solve the problem in that meeting.

1. Confirm the problem: what do we know, what remains uncertain and whose experience is missing?
2. Review scope and aim: which process and population are included, and what improvement are we seeking?
3. Check membership: who can contribute now, and who else needs to be involved?
4. Agree responsibilities: name the lead, process owner, sponsor and owners of the first actions.
5. Plan the next learning step: decide what to observe, check or measure before choosing a change to test.
6. Set the working arrangements: agree the shared record, next review date and route for decisions or barriers.

Copy this simple action format into your project record: Action | Named owner | Due date | Support needed | Result or learning. Keep it current so colleagues can see what is expected and what has already been done.

How to keep the team working between meetings

Choose a review rhythm that matches the pace of testing. A short regular check-in may be enough during a small local test, with separate sponsor reviews for decisions that need wider support. Avoid scheduling meetings that only repeat updates people could read beforehand.

At each review, ask what happened, what the evidence suggests, what remains uncertain and what the team will do next. Record unsuccessful tests as learning, not individual failure. Recognise contributions from data collection, patient feedback and routine coordination as well as visible milestones.

Simana’s collaboration tools let colleagues share updates, comments and mentions alongside their improvement work. Use a shared project record to keep decisions and context available to people who cannot attend every discussion.

Frequently asked questions about QI teams

Can I run a QI project on my own?

You can initiate a project, but involve the people who deliver and experience the process before changing it. Even a small project needs agreement about ownership, support and how the work will continue if you leave.

Does every team member need QI training?

No. People bring different expertise, including lived experience and knowledge of daily work. Arrange access to improvement support and explain the methods needed for the next task, rather than expecting everyone to be an expert before starting.

What is the difference between a project lead and a sponsor?

The lead coordinates the day-to-day work. The sponsor helps with authority, resources and barriers beyond the team’s control. Agree their responsibilities explicitly so routine coordination does not wait for senior approval and major barriers are not left with the lead alone.

What if an important colleague cannot attend meetings?

Agree another way to obtain their input: a short discussion, a written review or attendance at a specific decision point. Record what needs their advice and by when. If the project cannot proceed without their involvement, ask the sponsor to help secure the necessary time.

Next step: agree your aim and measurement plan

With the team and responsibilities in place, work together to write a clear QI aim statement and develop your measurement plan. Return to the QI project guide for the full journey through setup, planning, evidence and close-out.