Using Lived Experience Safely in Mental Health Quality Improvement

February 19, 2026

Many services can show they have “listened”, but fewer can show what changed, who authorised it, and whether it improved safety or outcomes. In this series on co-production and lived experience in mental health, we focus on how involvement becomes operational rather than performative. The same standards need to hold across mental health service models and pathways, because quality improvement must work in crisis response, community follow-up and longer-term support. This article explains how providers can use lived experience safely in quality improvement (QI), with clear boundaries, repeatable methods, and evidence that stands up to commissioner and inspector scrutiny.

What “safe use of lived experience” means in QI

Using lived experience safely does not mean avoiding challenge. It means designing involvement so it is:

Boundaried: clarity on what is and is not being discussed (including any individual cases), what information can be shared, and how distress is managed in sessions.
Supported: role descriptions, induction, access to debrief, and a named staff lead who is accountable for safeguarding and wellbeing.
Governed: documented agendas, minutes, actions, decision routes, and escalation where recommendations affect risk, staffing or clinical thresholds.
Tested: changes are trialled, audited and re-audited, with outcomes monitored over time.

Services often fail not because they lack goodwill, but because they cannot demonstrate that lived experience input was processed through governance and resulted in measurable improvement.

Choosing the right QI questions

Lived experience input is most powerful when it focuses on “pressure points” where pathways commonly fail. Examples include: response times and call-backs, crisis transitions, safety planning, medication conversations, and how services respond to disengagement. The QI question should be specific enough to test, such as: “Do people understand what happens after a crisis contact?” or “Can staff evidence that early warning signs lead to timely escalation?”

Operational Example 1: Improving crisis call-back reliability

Context: A provider’s patient experience data showed repeated frustration about missed call-backs after crisis triage. Staff believed call-backs were happening, but records were inconsistent and people reported uncertainty and fear while waiting.

Support approach: A lived experience reference group reviewed the call-back journey end-to-end. Clear boundaries were set: no discussion of identifiable cases; focus on system steps, language used, and what “good” should feel like for the person waiting.

Day-to-day delivery detail: The group co-designed a “call-back standard” with three operational requirements: (1) confirm expected time window; (2) provide a back-up escalation route if the window is missed; (3) document the attempt, outcome and next step in a consistent field. Team leaders added a daily shift checklist: outstanding call-backs at 12:00 and 17:00, with escalation to the duty lead if not completed. Supervisors used weekly spot-checks to confirm documentation quality.

Evidence of effectiveness: The provider tracked the percentage of call-backs completed within the agreed time window, plus complaints and incidents linked to “no response”. A six-week audit showed improved compliance and clearer records. Follow-up feedback from people using the service reported reduced uncertainty and better understanding of escalation options.

Operational Example 2: Co-producing safer transition information at step-down

Context: People discharged from crisis support reported confusion about ongoing contacts, medication changes, and what to do if risk increased. This created avoidable re-presentations and safeguarding concerns during the first week post-discharge.

Support approach: Lived experience contributors worked with clinicians and safeguarding leads to redesign the step-down information pack. The safeguarding lead held accountability for ensuring advice was safe and consistent with local pathways.

Day-to-day delivery detail: The pack was rewritten in plain English and structured around the first seven days: who contacts the person, when, what to expect, what “getting worse” can look like, and exactly how to seek urgent help. Staff were trained to complete a short “teach-back” prompt (asking the person to explain the plan in their own words) and record whether understanding was confirmed. A weekly MDT review included a standing agenda item to check whether step-down packs were completed for all discharges and whether any “teach-back” issues needed follow-up.

Evidence of effectiveness: The provider monitored 72-hour post-discharge contact completion, re-referrals within 14 days, and safeguarding alerts linked to missed follow-up. Re-audit demonstrated improved completion rates and fewer “unknown status” cases in the first week post-discharge.

Operational Example 3: Making complaints learning usable in practice

Context: Complaints were logged and responded to, but learning was not consistently embedded into frontline practice. People said the same issues recurred: feeling dismissed, unclear plans, and poor explanations of decisions.

Support approach: A lived experience panel helped convert complaints themes into practical “learning statements” for teams, while managers retained responsibility for investigating and closing actions.

Day-to-day delivery detail: The panel co-produced a monthly one-page learning brief: what happened, what should have happened, and what staff should do differently next time. The brief was used in team huddles and supervision. Managers were required to record two examples per month of how learning had been applied (for example, improved documentation of rationale for decisions; clearer communication of waiting times). Quality leads carried out spot-checks to confirm learning was visible in records.

Evidence of effectiveness: Repeat complaint themes reduced over two quarters. Supervision audits showed improved reflective discussion of communication and shared decision-making. Staff survey feedback indicated greater clarity about expected practice.

Commissioner Expectation: Evidenceable improvement cycles

Commissioner expectation: Commissioners expect lived experience to feed structured improvement cycles: plan, test, measure, and embed. They will look for action logs, responsible owners, timescales, and performance indicators showing whether changes improved pathway reliability, engagement, safety or outcomes.

Regulator / Inspector Expectation: Safeguarding oversight and accountability

Regulator / Inspector expectation: Inspectors will test whether involvement is safe, inclusive and governed. They will expect clear boundaries, support arrangements, and evidence that accountability remains with registered professionals and organisational leaders, especially where changes affect risk assessment, escalation or restrictive practice.

Governance mechanisms that make lived experience “count”

Providers typically evidence safe lived experience involvement through: terms of reference; induction and support arrangements; meeting minutes and decision routes; change control (versioning of documents); audit and re-audit; and a dashboard that links the QI work to measurable outcomes. Done well, lived experience becomes part of quality assurance rather than a parallel activity.