Embedding Lived Experience in Mental Health Service Design: From Consultation to Operational Change
Embedding lived experience into service design requires more than consultation exercises or feedback sessions. Within co-production, lived experience and personalisation, the real test is whether involvement changes pathways, documentation, thresholds and day-to-day operational decisions. It must also sit coherently within wider mental health service models and pathways, because design choices affect triage, escalation, discharge and risk management. This article sets out how providers move from discussion to demonstrable operational change.
From feedback to structured service design
Consultation often identifies recurring themes: unclear eligibility thresholds, inconsistent communication, confusing handovers between teams, or perceived rigidity in support plans. Embedding lived experience means structuring these themes into formal design cycles. Providers should define:
- A clear design question (e.g. “How can we reduce disengagement during step-down?”).
- Who is involved and why (service users, carers, peer workers).
- Decision-making authority and governance routes.
- How changes will be tested and reviewed.
Without this structure, involvement risks generating ideas without implementation control.
Operational Example 1: Redesigning referral and eligibility explanations
Context: A community mental health service received repeated complaints about “being bounced” between services and unclear explanations of thresholds. Lived experience contributors described frustration at inconsistent messages.
Support approach: The provider ran structured design workshops focused on referral communication and decision explanations. Contributors reviewed anonymised referral letters and scripts used by triage staff. Governance oversight sat with the service manager and quality lead.
Day-to-day delivery detail: The redesign produced:
- Standardised triage call scripts with plain-language explanations of thresholds.
- Letter templates co-written to explain decisions and next steps clearly.
- A short checklist for staff: “Have I explained what happens next? Have I checked understanding?”
Evidence of effectiveness: Repeat clarification calls reduced over two quarters. Complaints coded under “unclear eligibility” declined. Audit scores showed increased consistency in how next steps were explained.
Operational Example 2: Co-producing discharge and step-down pathways
Context: Service users reported feeling “dropped” at discharge. Data showed increased re-referrals within three months.
Support approach: The provider mapped the discharge journey with lived experience contributors, identifying pinch points: abrupt ending conversations, unclear relapse indicators, and weak handover to primary care.
Day-to-day delivery detail: The service introduced:
- A structured discharge planning meeting template including relapse indicators and contact routes.
- A co-produced discharge summary explaining warning signs and self-management steps.
- A follow-up call within two weeks for higher-risk individuals.
Evidence of effectiveness: Three-month re-referral rates reduced modestly but consistently. Audit samples showed clearer documentation of shared discharge conversations. Experience feedback indicated improved clarity about relapse management.
Operational Example 3: Co-designing group programmes
Context: Attendance in a recovery-focused group was inconsistent. Feedback suggested content felt generic and insufficiently personalised.
Support approach: Lived experience contributors reviewed the curriculum and co-designed additional sessions focusing on practical coping strategies and real-world scenarios.
Day-to-day delivery detail: The provider:
- Piloted revised session plans over one quarter.
- Gathered structured participant feedback after each group.
- Reviewed attendance trends and qualitative comments at governance meetings.
Evidence of effectiveness: Attendance stabilised and qualitative feedback referenced relevance and relatability. Governance minutes showed documented decisions to permanently adopt revised content.
Commissioner Expectation: Demonstrable pathway improvement
Commissioner expectation: Commissioners expect co-production to improve pathway flow, clarity and outcomes. Providers should evidence measurable changes linked to involvement themes, particularly in access, transitions and engagement.
Regulator / Inspector Expectation: Person-centred and safe design
Regulator / Inspector expectation: Inspectors will expect evidence that service design supports person-centred care and safe transitions. This includes documented shared planning, clear discharge processes and learning from feedback.
Governance and assurance
Embedding lived experience requires audit trails: workshop records, change logs, revised templates, supervision prompts and outcome data. When governance structures clearly show how involvement influenced operational design, co-production becomes a visible strength rather than a narrative claim.