Why Clinicians Don't Use Hospital Analytics Dashboards

I was in a hospital last month where the After-Hours Nurse Manager opened a spreadsheet to discuss bed pressure with the floor leads. Behind them, on a wall-mounted screen, a dashboard the operational team had built years earlier was still running, still showing yesterday's data. The tool built for exactly this moment was on the wall. They reached for the spreadsheet instead.

That choice, repeated quietly across a health service, is where platform value actually goes.

I've watched the same story play out time and time again. Operational teams build dashboards in silos. What looks right at an operational level often doesn't translate to how clinicians need to see or use the data in practice. There's no clear visibility on who owns the maintenance, and nobody schedules the review, so the team quietly reverts to the old way of working because the new way doesn't fit how they actually work. The platform is technically excellent and the data is real, but the people it was built for were never at the centre of how it was designed and deployed.

We often put this down to a technology failure, when in reality it is an operating model failure. And it isn't a future risk; it's already on the floor: in the patient who was clinically fit to leave this morning and is still in a bed this afternoon because no one could see the discharge was blocked, in care that loses continuity at handover, in the flow that stalls because the people moving patients can't see where the pressure actually is.

It shows up in the ordinary parts of the day. A theatre coordinator runs the list off Excel because the dashboard hasn't refreshed. An access block flagged at 11am can't be evidenced in the 4pm executive flow review. The platform is excellent; your operating rhythm is just running on a parallel track.

The Analytics Graveyard

Most hospital analytics platforms follow the same lifecycle. Year one is the implementation. Year two is the silence. By year three the executive sponsor has changed roles, the original use cases have drifted, and someone in finance is asking why the platform shows up on the asset register but not in any of the operational reviews. By the back end of year three the conversation about replacement is well underway.

It's the predictable end state of any analytics deployment that treats the platform as the deliverable. The cost lands in two places: in the licences and analyst hours spent on tools nobody runs from, and in the productivity the clinical team loses every shift as they work around those tools instead of from them.

This isn't only what I see in the field. A 2025 systematic review in JAMIA Open¹, led by Macquarie University's Centre for Health Informatics, screened more than 5,700 studies and analysed 70 on digital dashboards in inpatient care. Dashboards were associated with real gains: shorter length of stay, lower costs, better patient and carer satisfaction. But the review's central finding was that whether those gains show up at all depends on local factors, workflow integration chief among them. The benefit was never in the dashboard. It was in whether the dashboard was built into how the work actually runs.

England's Federated Data Platform shows the same gap at national scale. By November 2025, 157 NHS trusts had signed up. In the same month, the platform's products were live and delivering measurable benefits across roughly 73². That isn't a critique of the FDP. It's the structural pattern I see in almost every analytics deployment. Signing up is the easy part. Adoption is the work nobody puts in the business case.

Why adoption fails

Across the customers I work with, the same four things break, and they are the four things a dashboard needs to earn its place: insight, workflow, a KPI that means something, and governance. They tend to fail in that order, each one undoing the last.

1. Insight: the data is in the wrong tense, or built for the wrong reader

Most hospital dashboards report yesterday's data into today's workflow. A theatre coordinator running a list needs to know what's happening right now, both upstream in ED and on the floor in theatre. A daily refresh is past-tense intelligence in a present-tense job. When a senior nurse picks up Excel instead of the dashboard the hospital paid for, this is almost always why: the dashboard is correct, it just isn't current.

The same pillar fails a second way, when the data is current but built for the wrong reader. Clinicians are cognitively loaded, and the last thing a team needs is a dashboard built like an analyst's exploration tool, with dozens of metrics behind drill-downs and a learning curve before any of it is useful. A theatre dashboard for the team running the list shouldn't show utilisation percentages and historical trends. It should show capacity status and next-case readiness on one screen, blockers obvious, thresholds clear enough to act on without a meeting. When I ask hospital leaders who their dashboards were designed for, the honest answer is usually "everyone". A dashboard for everyone is a dashboard for no one in particular.

2.  Workflow: the data sits outside the conversations that matter

Hospitals run on alignment conversations: huddles, handovers, ward rounds, theatre briefs. Data becomes useful the moment it enters those conversations, and useless the moment it requires walking away to check a screen. A theatre coordinator in a 7am huddle can't manage flow if they have to step away to cross-reference a platform. An ED clinical lead running a bed-pressure huddle won't open a dashboard if it takes 30 seconds to load on a busy network. The 2025 CHIME/KLAS Digital Health Most Wired report³ found that the digitally mature organisations share one operating choice: they embed analytics directly into clinical and operational workflows. That isn't a technology choice. It's a design choice about where the data has to live.

3. KPI: the numbers don't trigger anything

A dashboard can be current, and live right inside the huddle, and still change nothing, because it shows numbers without saying which one matters or when. A screen displaying ED length of stay at six hours is data. It becomes a KPI only when the team has agreed what good looks like and at what point the number demands a response. Without that threshold, the dashboard generates activity but no accountability: everyone sees it, nobody is bound by it.

4. Governance: no one owns the response

This is the uncomfortable one. Even a sharp KPI in the right workflow dies if no one is accountable for acting on it. If the six-hour length of stay is visible but nobody has the authority or the standing cadence to respond, the number gets seen and ignored, and clinicians quietly learn not to trust it. The dashboard becomes a status report no one reads, attached to a contract no one wants to renew.

What actually drives adoption

When I look at the customers getting genuine value from their analytics, what they share is an operating pattern, not a technical one. The platform matters. The model around it matters more.

What has to exist doesn't install. It gets built, and the customers who get there build it the same way every time. Three practices do the work.

The conversation starts with the decision, not the dashboard. The first question isn't about the platform. It's about the work. The right opening question is what decision does this team make at the start of the shift that they don't currently have good information for, and what are they running off Excel because the platform doesn't fit. The dashboard gets built around the answer, not around the data the platform happens to expose.

There's a named person inside the work for months. Not a project manager on a fortnightly check-in or a vendor responding to tickets. A relationship-owner who attends the huddles, watches the workflows, sits with the floor coordinators, and keeps designing until the dashboard is the thing the team reaches for first. In our model that's a Customer Success Manager whose job isn't to deliver the platform but to make sure the team is using it, supported by a Clinical Solutions team that brings clinical expertise into the work and shows up at every Monthly Operational Review and Quarterly Business Review the customer runs.

The dashboards belong to the customer's team, not the vendor. The point of the dashboard isn't to demonstrate vendor capability. It's to give the clinical team something they can run from after the vendor leaves. We call our custom views Hubs, but the artefact matters less than the principle: each one is shaped around a specific decision and owned by the people who use it, and it has to keep evolving as the work does. If the team can't run with it after the vendor steps back, the engagement was a demo, not a deployment.

The frame I keep coming back to with my own team is that adoption rests on four things working together, none of them software. Insight without workflow is a poster on a wall. Workflow without a KPI is activity without accountability. A KPI without governance is a number no one defends. Governance without insight is a meeting that runs on opinion. Most implementations build the first and stop.

What this looks like when it works

The best example of what good looks like in practice is Bayside Health Peninsula (formerly Peninsula Health) in Victoria.

In January 2026, Peninsula transferred approximately 220 patients from the former Frankston Hospital into the new 12-storey Peninsula University Hospital.⁴ The move was completed smoothly and ahead of schedule. The first surgical procedure was finished before 10am, and the first baby was born in the new hospital that same morning.⁴

A move at that scale doesn't run on planning alone. It runs on confidence in the data the team is using to make decisions in real time. Peninsula's Customer Success Manager spent the months before the move partnering with the team to make sure the right people had accurate, real-time data when it mattered most: patient locations, movement patterns, and service pressures, made visible in the views the operational team would actually open when the pressure hit.

"SystemView played a critical role during our recent transition to the new hospital. The platform gave us live visibility of patient locations, movement patterns, and service pressures, allowing us to coordinate the transfer safely and efficiently. From an operational standpoint, it became our single source of truth, helping us anticipate bottlenecks, deploy resources proactively, and ensure continuity of care throughout the move." -  Jana Gazarek,  Chief Operating Officer

The addition of SystemView on our "Move Day" was a game changer for our paitent flow team and the Hospital Icident Command. It provided real time visability of patient movements, which was used to inform move status and analysing if the schedule was on track. It also have visability of all patients whose move was not linear - for example, old ward, theatre, new ward. The use of the SystemView Hub pages and Paitent Lists resulted in no manual data collection, which was not only accurate but also efficent. - Michelle Vuat, Patient Services Manager 

That's the Success Program running as intended: a relentless focus on what the health service actually needed. The move was the stress test, but the work that made it possible had been done month by month, well before anyone moved a bed.

Analytics adoption is not a technology problem, and never has been. It's an operating model problem. The hospitals seeing genuine value from their analytics aren't smarter than the ones that aren't. They've stopped treating the platform as the deliverable and started treating the operating model around it as the work.

That requires more than software. It requires insight people can trust, built into the workflows where decisions actually get made, measured against KPIs the team has agreed to act on, and held together by governance that turns what the data shows into what the organisation does. Making that happen in our model is a Customer Success Manager working alongside a Clinical Solutions Manager, partnering with the health service so that the way the platform is used aligns with how clinicians work. In yours, it might be structured differently. The job is the same.

If your platform is sitting underused on your network right now, the move worth making this quarter isn't a vendor change. It's a conversation with the people who should be using it about what they actually need to make a decision. Sit with them for a shift before you spend another six figures somewhere else. That's where adoption starts.

Sources

1. Westbrook, J. I., et al. Clinical and economic impact of digital dashboards on hospital inpatient care: a systematic review. JAMIA Open, Volume 8, Issue 4, July 2025, ooaf078. Centre for Health Informatics, Macquarie University. https://academic.oup.com/jamiaopen/article/8/4/ooaf078/8214040 ↩
2. NHS England, Federated Data Platform Programme Board minutes: 6 November 2025 (157 trusts signed up); Federated Data Platform Check and Challenge Group minutes: 19 September 2025 (77 trusts live and reporting benefits). https://www.england.nhs.uk/digitaltechnology/nhs-federated-data-platform/impact/fdp-uptake-and-benefits/ ↩
3. CHIME and KLAS Research, Digital Health Most Wired: National Trends 2025, November 2025. https://klasresearch.com/report/digital-health-most-wired-national-trends-2025/3946 ↩
4. Peninsula Health, Patients and consumers successfully move into new Peninsula University Hospital, January 2026. https://www.peninsulahealth.org.au/latest-news/patients-and-consumers-successfully-move-into-new-peninsula-university-hospital/ ↩ ↩²