Why Dashboards Don't Always Improve Patient Care: Practical Insights for NHS Teams

Introduction

Dashboards have become ubiquitous in healthcare, offering a visual summary of performance across various metrics. From clinical outcomes to operational efficiency, they are often seen as a cornerstone of modern quality improvement and performance management. The promise is clear: provide easy access to data, and improvement will follow.

However, the reality in many NHS settings often falls short of this expectation. Teams invest significant time and resources into developing and maintaining dashboards, yet tangible improvements in patient care or operational flow remain elusive. This resource explores why this disconnect occurs and provides practical strategies for NHS teams to get more out of their data visualisations.

Why This Topic Matters

In an increasingly data-rich NHS, the ability to translate raw data into actionable intelligence is paramount. Wasted effort on ineffective dashboards not only drains valuable time and resources but also leads to 'data fatigue' among staff, making future improvement initiatives harder to land. Understanding the pitfalls of dashboard design and implementation is crucial for ensuring that these tools genuinely support, rather than hinder, the drive for better patient care and more efficient service delivery. Ultimately, well-designed and utilised dashboards can empower staff to make informed decisions, identify variations, and celebrate successes, fostering a culture of continuous improvement.

Practical Explanation: The Dashboard Disconnect

Many dashboards fall short not because the data is wrong, but because they fail to bridge the gap between information and action. Here are common reasons for this disconnect:

• Lack of Clear Purpose: Is the dashboard designed to monitor, inform, or drive specific action? Without a clear objective, dashboards become data dumps, making it difficult to discern what is important.
• Audience Misalignment: Who is the dashboard for? A ward manager needs different information from a divisional director. Tailoring content, granularity, and visualisations to the specific needs and decision-making context of the intended audience is critical.
• Information Overload: Too many metrics, complex charts, or an overwhelming amount of data can paralyse users. Simplicity and focus are key.
• Poor Data Quality/Accessibility: Dashboards are only as good as the data they display. Inaccurate, incomplete, or delayed data undermines trust and usefulness. If the underlying data sources are difficult to access or integrate, maintaining the dashboard becomes a significant overhead.
• No Link to Actionable Insights: A dashboard might show a problem, but does it signpost why the problem exists or what could be done? Without providing context or encouraging investigation, dashboards are merely indicators, not enablers of change.
• Lack of Training and Support: Users need to understand how to interpret the data, what the metrics mean, and how to use the dashboard effectively. Without adequate support, even a well-designed dashboard can be underutilised.
• Static vs. Dynamic: Many dashboards reflect 'what happened' rather than supporting 'what is happening now' or 'what should happen next'. Real-time or near-real-time data, where appropriate, can be far more impactful.
• Focus on Outcomes, Not Processes: While outcome measures are important, dashboards that focus solely on these without also tracking key process measures make it difficult to understand the levers for improvement.
• Absence of an Improvement Framework: A dashboard without an accompanying QI framework (e.g., Model for Improvement, Lean) can lead to data being observed rather than acted upon. Dashboards should be tools within a wider improvement effort.

Common Pitfalls

• Vanity Metrics: Displaying metrics that look good but don't genuinely reflect performance or drive decision-making.
• Comparison Without Context: Presenting performance data against benchmarks without considering local population differences, case mix, or specific operational challenges.
• 'Green is Good, Red is Bad' Simplification: Over-simplifying complex clinical or operational scenarios into traffic light systems without underlying explanation can lead to misinterpretation or inappropriate actions.
• Build It and They Will Come: Assuming that simply making a dashboard available will lead to its adoption and effective use without active promotion, training, and integration into existing workflows.
• Ignoring User Feedback: Failing to iteratively refine the dashboard based on feedback from the people who are meant to use it.

A Step-by-Step Approach to Effective Dashboards

To create dashboards that genuinely drive improvement, consider the following approach:

1. Define the Problem and Purpose

• What specific problem are you trying to solve or question are you trying to answer? Start with the 'why'.
• What decision or action should result from viewing this dashboard? If no action is anticipated, rethink. For example, 'reduce emergency readmissions for heart failure' or 'improve theatre utilisation'.

2. Identify the Audience and Their Needs

• Who will be using this dashboard? Clinicians, managers, executives?
• What are their day-to-day responsibilities? How will this dashboard fit into their workflow?
• What level of detail do they require? Aggregate vs. disaggregated data.

3. Select Key Metrics (Measures for Improvement)

• What are the most crucial measures that directly relate to your purpose? Often, fewer, well-chosen metrics are more effective than many.
• Balance outcome, process, and balancing measures. For example, reducing length of stay (outcome), adherence to discharge bundle (process), and patient satisfaction (balancing).
• Ensure data validity and reliability. Can the data be collected accurately and consistently?

4. Design for Clarity and Actionability

• Visualisation: Choose appropriate chart types (e.g., run charts for trends over time, bar charts for comparisons). Avoid overly complex visuals.
• Layout: Organise information logically, using white space effectively. Place the most important metrics prominently.
• Context: Include targets, benchmarks, and brief explanatory notes. Use annotation to highlight significant events or changes.
• Drill-down: Where appropriate, allow users to delve into more detail to understand underlying causes.

5. Build and Test Iteratively

• Start simple. Build a basic version and gather feedback early.
• Pilot with a small group. Observe how they interact with the dashboard, what questions arise, and what challenges they face.
• Refine based on feedback. Dashboards are living tools; they should evolve with user needs and the improvement journey.

6. Implement and Support

• Launch with training. Explain the dashboard's purpose, what the metrics mean, and how to interpret them.
• Integrate into workflows. Discuss how teams can use the dashboard in their daily huddles, team meetings, or QI sessions.
• Promote a culture of inquiry. Encourage staff to ask 'why?' when data points deviate and to use the dashboard to test hypotheses.
• Regularly review and update. Ensure the data remains relevant and accurate.

Example in Clinical Practice

A busy Emergency Department (ED) wanted to reduce patient 'door-to-doctor' time. They initially implemented a dashboard showing average door-to-doctor time, updated monthly. While it displayed the statistic, it didn't lead to significant improvement.

Applying the New Approach:

1. Problem & Purpose: Reduce door-to-doctor time to improve patient flow and safety, specifically for acute medical patients.
2. Audience: ED clinicians and charge nurses, operational managers.
3. Key Metrics:
   • Outcome: Percentage of acute medical patients seen within 15 minutes of arrival.
   • Process: Time from triage completion to doctor assessment; number of doctors on shift vs. patient load by hour.
   • Balancing: Patient satisfaction scores (specific to waiting times).
4. Design: A prominently displayed, real-time dashboard on large screens in the ED. It incorporated color-coding (green/amber/red) indicating adherence to target for current patients, alongside simple line graphs for daily trends. A 'Drill-down' feature allowed nurses to see individual patient arrival/triage/doctor-seen times.
5. Build & Test: A prototype was developed with input from ED staff, tested during a quiet period, and refined based on feedback that included requests for 'patient type' filtering and real-time waiting list integration.
6. Implement & Support: The new dashboard was rolled out with mandatory brief training for all staff. It became a central talking point in daily ED huddles, with teams actively discussing current performance and identifying bottlenecks. The ability to see real-time impact of interventions (e.g., reallocating nurses to triage, earlier doctor shifts) fostered active engagement.

Result: The ED saw a sustained improvement in door-to-doctor times for acute medical patients, alongside a reduction in anecdotal complaints about waiting.\

This resource supports, but does not replace, clinical judgement. Local policy, formulary and specialist advice should be followed.

How Lazomis Can Help

Lazomis provides structured tools and frameworks to support NHS teams in their quality improvement journeys, including the design and implementation of effective data utilisation strategy. Our 'QI Project Setup' module guides teams through defining clear project aims, selecting appropriate measures, and identifying stakeholders – foundational steps for any successful dashboard. The 'Data Collection & Analysis' features can assist in streamlining data capture, ensuring data quality, and visualising trends using appropriate run charts and control charts, making it easier to move beyond static data points to meaningful insights. Lazomis helps connect the dots between your improvement ideas, the data you collect, and the actions you take, ensuring your dashboards serve as powerful catalysts for change rather than mere displays of information. Our platform encourages iterative development and feedback loops, aligning with best practices for dashboard creation and refinement.