Watford General — How West Hertfordshire Eliminated Corridor Care
The reported achievement is striking: corridor care eliminated through a winter of intense demand. The practical lesson is about connecting front-line information, authority to act and shared responsibility for patient care.
☰ Contents
What Watford achieved
West Hertfordshire Teaching Hospitals NHS Trust, serving Watford, St Albans and Hemel Hempstead, reported eliminating corridor care and maintaining that position through a winter of record demand. Its account emphasises changes to how the hospital coordinated care, used information and empowered staff.
Maintaining the outcome under pressure makes this a valuable case to investigate. It is more informative than a brief improvement during a quieter period. But rising demand is context, not a control group: it does not, by itself, rule out other explanations for the result.
What changed in practice
Four connected features stand out in the account of Watford’s approach. They are useful questions for other hospitals to explore, rather than a package whose independent effects have been established.
- Senior management where problems occurred. A senior manager was present on the floor around the clock, bringing decision-making closer to the point where patient flow was obstructed. This was continuous operational involvement rather than an occasional walkaround.
- Authority across departmental boundaries. The role could coordinate action across teams, rather than leaving front-line staff to escalate each blockage through separate management chains. Information was connected to someone able to act on it.
- Shared responsibility for patient flow. Departments organised around the hospital-wide problem of corridor care, rather than treating their own activity or targets as the whole task. A data-driven control centre supported coordination with timely information.
- Staff able to raise problems safely. Empowerment was central to the stated approach. Staff needed to feel trusted and listened to so that operational information reflected what was happening, not only what people felt comfortable reporting.
Chief Executive Matthew Coats described three priorities: a data-driven organisation, operational excellence focused on patient care, and an empowering culture. His emphasis on the third is important:
“An organisation whose team feels trusted, feels connected to the organisation and feels listened to is most likely to deliver further improvement.”
— Matthew Coats CB, Chief Executive
Why this matters
The proposed mechanism is straightforward: bring together information about the problem, authority to respond and responsibility for the shared outcome. A blockage visible to one team becomes actionable across the hospital. Staff confidence in speaking up helps that information travel.
This is a system-level interpretation of the case, not proof of which component caused the outcome. The transferable question is not simply “Should we put a senior manager on the floor?” It is “Can the people who see a problem connect promptly with those who can resolve it, across departmental boundaries?”
For the underlying ideas, see Joiner’s Levels of Fix, the Joiner Triangle and Going to the Gemba. These explain the frameworks without adding another layer to the case itself.
What remains unproven
The evidence presented here is operational; it has not been tested to a pre-committed Bootstrap CUSUM evaluation standard. Two questions remain: whether the improvement is sustained and what caused it.
- Are the arrangements embedded? Are the operational role, cross-departmental authority and shared accountability part of normal governance, or dependent on particular leaders?
- Does speaking up remain safe under pressure? Recruitment, management practice and responses to incidents matter more than a statement of cultural intent.
- What do outcomes show over time? Monthly corridor-care data should be considered alongside demand, intervention dates and balancing measures such as readmissions, safety incidents and staff experience, including after leadership or support changes.
Bootstrap CUSUM can help assess the timing, magnitude and persistence of a change in the measured outcome. It cannot, by itself, establish that Watford’s approach caused that change. Nor does a sustained signal alone distinguish embedded improvement from continuing leadership attention or a Hawthorne Effect.
How to take this further
Use Watford as a starting point for investigation, not a ready-made prescription.
- Investigate and replicate: Bright Spot Analysis explains how to confirm a signal, investigate what changed, separate transferable features from local context and test replication.
- Connect to patient-safety learning: PSIRF and Systemic Learning links incidents to patterns, structural causes and evaluation.
- Connect local learning to national evaluation: Corridor Care 2029 explores how to assess whether wider programmes improve outcomes — and what the results can establish.
- Check the improvement approach: Why Improvement Programmes Fail asks whether you have the right problem, intervention and measures.
Test your own trust’s data
If you have monthly corridor-care data, the StepChange Analyzer is an optional tool for assessing whether a change in the outcome is visible. Interpretation still requires context and evidence about causes.
▶ Open the StepChange Analyzer