TRANSKRIBEERI 🔗
WEBVTT
00:01:01.709 --> 00:01:06.295
Hello, Healthcare Leaders, and welcome back to the Healthcare Excellence Framework Masterclass.
00:01:06.295 --> 00:01:07.399
I'm your host, Jarvis T.
00:01:07.399 --> 00:01:15.873
Gray, and today we're moving into another incredibly important domain of the Healthcare Excellence Framework: Data, Analytics, and Digital Excellence.
00:01:15.873 --> 00:01:18.754
Now let's quickly connect this to where we've already been.
00:01:18.754 --> 00:01:24.250
In episode one, we established that Excellence is not an initiative, it's a system.
00:01:24.250 --> 00:01:27.850
In episode two, we explored leadership and governance excellence.
00:01:27.850 --> 00:01:31.971
In episode three, we moved into strategic alignment and execution.
00:01:31.971 --> 00:01:35.312
In episode four, we talked about operational excellence.
00:01:35.312 --> 00:01:39.133
In episode five, we explored workforce and culture excellence.
00:01:39.133 --> 00:01:44.094
And in episode six, we focused on patient, resident, and community excellence.
00:01:44.094 --> 00:01:47.828
So now we arrive at a question that touches every one of those domains.
00:01:47.828 --> 00:01:50.209
How do leaders actually know what's happening?
00:01:50.209 --> 00:01:53.330
How do leaders know whether strategy is working?
00:01:53.330 --> 00:01:55.632
How do they know if performance is improving?
00:01:55.632 --> 00:01:58.072
How do they know where the risk is growing?
00:01:58.072 --> 00:02:00.834
How do they know whether employees are struggling?
00:02:00.834 --> 00:02:03.637
How do they know whether patient outcomes are getting better?
00:02:03.637 --> 00:02:06.198
How do they know whether access is improving?
00:02:06.198 --> 00:02:09.562
How do they know whether a problem is isolated or systemic?
00:02:09.562 --> 00:02:11.103
That's where data comes in.
00:02:11.103 --> 00:02:13.245
And today's big idea is simple.
00:02:13.245 --> 00:02:26.997
Great leaders don't guess, they learn, they look for evidence, they ask better questions, they test assumptions, they pay attention to patterns, they use information to reduce uncertainty, and then they act.
00:02:26.997 --> 00:02:30.699
That's what data analytics and digital excellence is really about.
00:02:30.699 --> 00:02:36.620
Not simply collecting more data, not building more dashboards, not buying more technology.
00:02:36.620 --> 00:02:40.401
It's about creating intelligence so leaders can make better decisions.
00:02:40.401 --> 00:02:41.851
So let's get into it.
00:02:42.128 --> 00:02:44.570
Healthcare has no shortage of data.
00:02:44.570 --> 00:03:02.191
We have clinical data, financial data, quality data, workforce data, patient experience data, access data, operational data, claims data, community health data, digital data, benchmark data, real-time data, historical data.
00:03:02.191 --> 00:03:06.639
And yet many leaders still struggle to answer relatively simple questions.
00:03:06.639 --> 00:03:08.691
What is really
Load full transcript
driving this problem?
00:03:08.691 --> 00:03:10.111
Where should we focus?
00:03:10.111 --> 00:03:11.853
Is performance improving?
00:03:11.853 --> 00:03:13.793
Which intervention is working?
00:03:13.793 --> 00:03:16.094
Which population is being affected?
00:03:16.094 --> 00:03:17.275
What changed?
00:03:17.275 --> 00:03:18.615
Why did it change?
00:03:18.615 --> 00:03:20.276
And what should we do next?
00:03:20.276 --> 00:03:22.298
That tells us something important.
00:03:22.298 --> 00:03:25.810
Having data is not the same as having intelligence.
00:03:25.810 --> 00:03:29.110
That is one of the central ideas of this episode today.
00:03:29.110 --> 00:03:32.032
I call this the data to intelligence gap.
00:03:32.032 --> 00:03:39.372
The data to intelligence gap is the difference between having information and actually understanding what the information means.
00:03:39.372 --> 00:03:48.144
red, yellow, green, trend lines, percentages, comparisons, targets.
00:03:48.144 --> 00:03:50.043
It may look sophisticated.
00:03:50.043 --> 00:04:03.622
But if the leadership team looks at it and still doesn't know what changed, why it changed, and what matters most, or what decisions need to be made, Then we do not yet have intelligence, we simply have information.
00:04:03.622 --> 00:04:06.500
And information alone does not improve performance.
00:04:06.500 --> 00:04:10.364
Data tells you what happened, analytics helps explain why.
00:04:10.364 --> 00:04:14.848
Intelligence helps you decide what to do next, and that distinction matters.
00:04:14.848 --> 00:04:20.053
measurement should create decisions.
00:04:20.053 --> 00:04:30.901
That doesn't mean every number needs an immediate action, but data should help leaders to understand, prioritize, question, learn, and then decide.
00:04:30.901 --> 00:04:39.108
If the same dashboard appears every month, people review it, someone says that number is still red, and then the meeting moves on.
00:04:39.108 --> 00:04:40.869
That's not performance management.
00:04:40.869 --> 00:04:42.090
That's reporting.
00:04:42.090 --> 00:04:44.170
And I call that reporting theater.
00:04:44.170 --> 00:04:45.699
Lots of information.
00:04:45.699 --> 00:04:48.140
Very little learning, very little action.
00:04:48.140 --> 00:04:51.002
A healthy data culture asks, what does this mean?
00:04:51.002 --> 00:04:52.264
Why is it happening?
00:04:52.264 --> 00:04:53.463
What changed?
00:04:53.463 --> 00:04:54.963
Where should we look deeper?
00:04:54.963 --> 00:04:56.335
What do we need to test?
00:04:56.335 --> 00:04:58.880
And what decision does this information require from us?
00:04:58.880 --> 00:05:00.459
And again, that's different.
00:05:00.459 --> 00:05:02.990
Think about your last executive performance meeting.
00:05:02.990 --> 00:05:05.770
How much time did you spend reading the numbers?
00:05:05.770 --> 00:05:13.513
And how much time did you spend interpreting them, challenging the assumptions, identifying root causes, and then
making decisions?
00:05:13.513 --> 00:05:17.103
That ratio tells you a lot about the maturity of your data culture.
00:05:17.103 --> 00:05:22.932
One of the biggest challenges that leaders face today is not the lack of information, it's too much information.
00:05:22.932 --> 00:05:25.552
I call this the signal-to-noise problem.
00:05:25.552 --> 00:05:29.764
When everything gets measured, everything starts competing for attention.
00:05:29.764 --> 00:05:35.505
And if everything receives equal attention, then leaders can easily miss what actually matters.
00:05:35.505 --> 00:05:39.746
And that's why more metrics do not automatically produce better management.
00:05:39.746 --> 00:05:42.168
Sometimes they produce distraction.
00:05:42.168 --> 00:05:45.429
So the mature question is not what else can we measure?
00:05:45.429 --> 00:05:50.532
The mature question is what information do we actually need in order to make better decisions?
00:05:50.532 --> 00:05:52.493
This is a much stronger question.
00:05:52.493 --> 00:05:54.474
Think back to episode three.
00:05:54.474 --> 00:05:56.735
We talked about strategy execution.
00:05:56.735 --> 00:06:04.937
If the organization has three major strategic priorities, You should not need 100 strategic measures to understand whether those priorities are moving.
00:06:04.937 --> 00:06:10.038
You need the right measures, the ones that tell you are we achieving the outcome?
00:06:10.038 --> 00:06:11.578
Is the system moving?
00:06:11.578 --> 00:06:13.379
Are the actions occurring?
00:06:13.379 --> 00:06:14.509
Where are the risks?
00:06:14.509 --> 00:06:18.140
that's why good measurement requires discipline, not volume.
00:06:18.140 --> 00:06:23.153
Another important distinction is the difference between lagging metrics and leading metrics.
00:06:23.153 --> 00:06:25.716
A lagging measure tells you what already happened.
00:06:25.716 --> 00:06:38.993
Turnover, mortality, readmissions, revenue, patient experience scores, length of stay, those are important, but by the time some of those numbers move, the underlying conditions may have existed for months.
00:06:38.993 --> 00:06:41.894
Leading indicators help you see earlier signals.
00:06:41.894 --> 00:06:49.561
For turnover, maybe employee engagement, manager effectiveness, stay interview themes, or vacancy trends.
00:06:49.561 --> 00:06:56.245
For patient flow, maybe pending discharge barriers, early discharge planning, bed turnaround, or consult delays.
00:06:56.245 --> 00:07:01.774
For financial performance, maybe volume, denials, productivity, or payer mix.
00:07:01.774 --> 00:07:08.317
Great leaders need both, Because if you only manage lagging indicators, you're driving while looking in the rearview mirror.
00:07:08.317 --> 00:07:13.480
Lagging measures tell you where you've been, Leading measures help you influence where you're going.
00:07:13.480 --> 00:07:15.801
So now let's talk about data quality.
00:07:15.801 --> 00:07:20.463
Because a beautiful dashboard built on unreliable data is still unreliable.
00:07:20.463 --> 00:07:23.025
So leaders need healthy skepticism.
00:07:23.025 --> 00:07:25.126
Where did this one number come from?
00:07:25.126 --> 00:07:26.487
How is it defined?
00:07:26.487 --> 00:07:28.588
Is the definition consistent?
00:07:28.588 --> 00:07:30.110
Is the data complete?
00:07:30.110 --> 00:07:31.389
Is there a delay?
00:07:31.389 --> 00:07:34.270
Are teams entering the information differently?
00:07:34.270 --> 00:07:36.903
Are we comparing the same things across departments?
00:07:36.903 --> 00:07:38.866
Has the measure changed over time?
00:07:38.866 --> 00:07:40.830
Those questions they all matter.
00:07:40.830 --> 00:07:43.494
Because false precision can be dangerous.
00:07:43.494 --> 00:07:50.153
A number displayed to two decimal places can look incredibly authoritative even when the underlying data is weak.
00:07:50.153 --> 00:07:52.856
so data excellence begins with something simple.
00:07:52.856 --> 00:07:54.489
Can we trust the information?
00:07:54.489 --> 00:07:56.509
I call this the data trust test.
00:07:56.509 --> 00:07:58.610
So ask five questions.
00:07:58.610 --> 00:08:01.381
First, do we know where the data comes from?
00:08:01.381 --> 00:08:04.523
Second, is the measure defined consistently?
00:08:04.523 --> 00:08:08.154
Third, is the data timely enough to support decisions?
00:08:08.154 --> 00:08:10.689
Fourth, do the people using the data trust it?
00:08:10.689 --> 00:08:13.654
And fifth, can we explain significant changes?
00:08:13.654 --> 00:08:19.926
If the answers to those questions is no, you may have a data governance problem, not a performance problem.
00:08:19.926 --> 00:08:22.628
This is where data governance becomes important.
00:08:22.628 --> 00:08:26.931
Data governance sounds technical, but the basic idea is straightforward.
00:08:26.931 --> 00:08:28.331
Who owns the data?
00:08:28.331 --> 00:08:29.452
Who defines it?
00:08:29.452 --> 00:08:30.933
Who can access it?
00:08:30.933 --> 00:08:32.745
How is quality maintained?
00:08:32.745 --> 00:08:34.684
How is privacy protected?
00:08:34.684 --> 00:08:37.245
How are completing versions reconciled?
00:08:37.245 --> 00:08:50.091
Because if finance has one definition, operations has another, quality has another, and leadership has another, then the organization can spend more time arguing about the number than improving the performance.
00:08:50.091 --> 00:08:54.240
So data governance creates trust, and trust creates speed.
00:08:54.240 --> 00:08:59.778
Analytics maturity is not only about technology, it's also about leadership curiosity.
00:08:59.778 --> 00:09:03.721
The quality of the answer is often influenced by the quality of the question.
00:09:03.721 --> 00:09:08.322
So instead of asking why is turnover high, ask where is turnover highest.
00:09:08.322 --> 00:09:12.794
Which roles, which managers, which tenure groups, which shifts?
00:09:12.794 --> 00:09:15.035
what changed before turnover
increase?
00:09:15.035 --> 00:09:17.096
What are the stay interviews telling us?
00:09:17.096 --> 00:09:19.236
What are the exit interviews telling us?
00:09:19.236 --> 00:09:20.456
Now we can learn.
00:09:20.456 --> 00:09:31.081
So instead of asking why is access bad, ask which services, which patient populations, which days, which locations, where is demand exceeding capacity?
00:09:31.081 --> 00:09:33.602
Where does the scheduling process break down?
00:09:33.602 --> 00:09:36.694
Because better questions create better analysis.
00:09:36.694 --> 00:09:39.658
This leads to something that I call the learning question.
00:09:39.658 --> 00:09:45.406
Whenever you look at performance data, ask, what is this telling us that we did not know before?
00:09:45.406 --> 00:09:48.977
If the answer is nothing, then ask why are we reviewing it?
00:09:48.977 --> 00:09:52.639
Data should help you learn, not simply confirm what you already know.
00:09:52.639 --> 00:09:56.060
This is especially important because leaders are human.
00:09:56.060 --> 00:10:00.781
We all have assumptions, preferences, past experiences, beliefs.
00:10:00.781 --> 00:10:04.882
And sometimes we use data not to learn but to prove ourselves right.
00:10:04.882 --> 00:10:10.284
We notice information that supports our theory and discount information that challenges it.
00:10:10.284 --> 00:10:12.025
That's confirmation bias.
00:10:12.025 --> 00:10:17.757
Mature organizations create enough psychological safety That data can challenge leadership assumptions.
00:10:17.757 --> 00:10:19.418
Remember episode five?
00:10:19.418 --> 00:10:21.079
Culture matters here too.
00:10:21.079 --> 00:10:28.134
If analysts know leadership only wants to hear the good news, the analytics function will eventually become a reporting function.
00:10:28.134 --> 00:10:31.716
if leaders welcome challenge, analytics becomes intelligence.
00:10:31.716 --> 00:10:34.088
So let's talk about analytics maturity.
00:10:34.088 --> 00:10:39.911
one simple way to think about it is through four levels, and I call this the analytics learning ladder.
00:10:39.911 --> 00:10:42.052
The first level is descriptive.
00:10:42.052 --> 00:10:43.193
What happened?
00:10:43.193 --> 00:10:46.716
Volume drop, turnover increase, length of stay rows.
00:11:31.015 --> 00:11:32.996
The next diagnostic.
00:11:32.996 --> 00:11:34.206
Why did it happen?
00:11:34.206 --> 00:11:36.107
which factors contributed?
00:11:36.107 --> 00:11:37.638
Where did the pattern begin?
00:11:37.638 --> 00:11:41.008
Next predictive What is likely to happen next?
00:11:41.008 --> 00:11:43.187
Which patients may be at greater risk?
00:11:43.187 --> 00:11:45.469
Where could demand exceed capacity?
00:11:45.469 --> 00:11:48.331
Which employees may be at higher risk for turnover?
00:11:48.331 --> 00:11:50.232
And finally, prescriptive.
00:11:50.232 --> 00:11:51.654
What should we do about it?
00:11:51.654 --> 00:11:52.955
we intervene?
00:11:52.955 --> 00:11:55.918
What action
is most likely to improve the outcomes?
00:11:55.918 --> 00:12:08.073
Not every organization needs sophisticated predictive modeling for everything, But the broader point here is that data maturity should move the organization from reporting the past towards learning fast enough to influence the future.
00:12:08.073 --> 00:12:10.905
So let's move into the digital side of this domain.
00:12:10.905 --> 00:12:14.918
Digital excellence doesn't mean how much technology do you own?
00:12:14.918 --> 00:12:19.941
It does not mean how many systems you purchase or how many apps are available.
00:12:19.941 --> 00:12:24.225
Does technology make the work better?
00:12:24.225 --> 00:12:25.706
Does it improve access?
00:12:25.706 --> 00:12:27.348
Does it reduce friction?
00:12:27.348 --> 00:12:29.390
Does it support better decisions?
00:12:29.390 --> 00:12:31.221
Does it connect information?
00:12:31.221 --> 00:12:33.402
Does it improve the patient experience?
00:12:33.402 --> 00:12:35.963
Does it improve the employee experience?
00:12:35.963 --> 00:12:37.924
Does it strengthen performance?
00:12:37.924 --> 00:12:43.365
And if not, then technology may simply be digitizing complexity, and that's a problem.
00:12:43.365 --> 00:12:46.146
Remember operational friction from episode four?
00:12:46.146 --> 00:12:48.408
There's a digital version of this as well.
00:12:48.408 --> 00:12:50.108
I call it digital friction.
00:12:50.108 --> 00:13:07.158
Too many logins, poor system integration, duplicate documentation, alerts that no longer mean anything, multiple platforms performing similar functions, systems that don't communicate, manual data transfer, slow technology, confusing interfaces.
00:13:07.158 --> 00:13:14.071
Those things consume time, they create frustration, they increase risk, and eventually they affect patient care.
00:13:14.071 --> 00:13:16.416
So when organizations invest in technology,
00:13:16.416 --> 00:13:19.542
can the system do this?
00:13:19.542 --> 00:13:22.467
Also ask, what will this make easier?
00:13:22.467 --> 00:13:23.739
That's a better test.
00:13:23.739 --> 00:13:26.091
Here's a principle that I believe strongly.
00:13:26.091 --> 00:13:28.513
Technology should serve the work.
00:13:28.513 --> 00:13:31.655
The work should not consistently serve the technology.
00:13:31.655 --> 00:13:36.399
If clinicians spend more time feeding systems than caring for patients, something is wrong.
00:13:36.399 --> 00:13:42.712
If employees have to create spreadsheets to compensate for expensive enterprise systems, something is wrong.
00:13:42.712 --> 00:13:48.544
If leaders cannot obtain basic intelligence despite millions of dollars of technology, something is wrong.
00:13:48.544 --> 00:13:54.807
Digital transformation should simplify, connect, and strengthen, not simply add another layer.
00:13:54.807 --> 00:13:59.571
And of course, we cannot talk about data analytics and digital excellence today.
00:13:59.571 --> 00:14:01.940
Without talking about artificial intelligence.
00:14:01.940 --> 00:14:18.220
AI is creating enormous opportunity across healthcare from documentation, analytics, Workflow support, patient communication, decision support, administrative automation, predictive modeling, education, research, and many other areas.
00:14:18.220 --> 00:14:23.622
we cannot confuse new with valuable.
00:14:23.622 --> 00:14:26.423
The question is not where can we use AI?
00:14:26.423 --> 00:14:33.735
where can AI help us create meaningful value, better outcomes, less administrative burden?
00:14:33.735 --> 00:14:43.305
Faster decisions, better access, lower costs, improved employee experience, stronger patient experience, that's where the conversation should start.
00:14:43.305 --> 00:14:45.786
I call this the digital value test.
00:14:45.786 --> 00:14:50.148
before investing in a major digital tool, ask five questions.
00:14:50.148 --> 00:14:52.629
First, what problem are we solving?
00:14:52.629 --> 00:14:54.470
Second, who benefits?
00:14:54.470 --> 00:14:57.391
Third, what outcome should improve?
00:14:57.391 --> 00:15:00.272
Fourth, what new burden could this create?
00:15:00.272 --> 00:15:02.593
Fifth, how will we know if it worked?
00:15:02.593 --> 00:15:04.874
Those questions, they sound simple.
00:15:04.874 --> 00:15:09.212
But they can prevent organizations from purchasing technology in search of a problem.
00:15:09.212 --> 00:15:20.670
AI also introduces important leadership responsibilities privacy, security, access, bias, transparency, human oversight, clinical judgment, ethics.
00:15:20.670 --> 00:15:23.993
These issues cannot simply be delegated to IT.
00:15:23.993 --> 00:15:31.779
Leadership has to understand enough to govern the risk because the more powerful the technology, the more important good governance becomes.
00:15:31.779 --> 00:15:34.131
So innovation needs guardrails.
00:15:34.131 --> 00:15:42.395
Not barriers that make progress impossible, But responsible guardrails that keep progress aligned with the mission, safety, and trust.
00:15:42.395 --> 00:15:44.056
Here's another important point.
00:15:44.056 --> 00:15:47.238
Analytics cannot only live at the executive level.
00:15:47.238 --> 00:15:50.100
Frontline teams need useful information too.
00:15:50.100 --> 00:15:53.502
A nurse manager needs information relevant to the unit.
00:15:53.502 --> 00:15:56.253
A clinic leader needs access and flow data.
00:15:56.253 --> 00:16:00.068
A physician leader may need quality and utilization information.
00:16:00.068 --> 00:16:03.703
A department manager may need workforce and productivity information.
00:16:03.703 --> 00:16:08.747
But it needs to be timely, understandable, actionable, and relevant.
00:16:08.747 --> 00:16:14.811
If the frontline sees the data six weeks after the problem occurred, we've lost valuable learning time.
00:16:14.811 --> 00:16:17.693
I call this idea democratizing insight.
00:16:17.693 --> 00:16:24.338
The goal is to move the right information to the
right people at the right time in a form that they can use.
00:16:24.338 --> 00:16:29.565
Not everybody needs every dashboard, but everybody responsible for performance.
00:16:29.565 --> 00:16:32.787
Should have access to enough information to manage it.
00:16:32.787 --> 00:16:35.257
That's how data becomes part of daily management.
00:16:35.257 --> 00:16:42.009
data should never make us forget Remember a lesson from earlier in this masterclass?
00:16:42.009 --> 00:16:44.550
Eventually, every number has a name.
00:16:44.550 --> 00:16:47.472
Behind every readmission number is a patient.
00:16:47.472 --> 00:16:50.684
Behind every turnover statistic is an employee.
00:16:50.684 --> 00:16:53.985
Behind every access measure is someone who needed care.
00:16:53.985 --> 00:16:58.226
Behind every financial number is a decision with consequences.
00:16:58.226 --> 00:17:02.687
So quantitative data matters, but qualitative information matters too.
00:17:02.687 --> 00:17:10.509
The stories, the comments, the observations, interviews, patient feedback, employee experience, community voice.
00:17:10.509 --> 00:17:12.171
Data tells us what.
00:17:12.171 --> 00:17:15.251
Stories often help us understand why.
00:17:15.251 --> 00:17:16.306
Great leaders.
00:17:16.306 --> 00:17:17.629
They learn from both.
00:17:17.629 --> 00:17:19.295
Numbers tell you where to look.
00:17:19.295 --> 00:17:21.460
People help you understand what you're seeing.
00:17:21.460 --> 00:17:23.510
So now let's bring this all together.
00:17:23.510 --> 00:17:28.474
I think about data, analytics, and digital excellence through six connected disciplines.
00:17:28.474 --> 00:17:31.096
Discipline one, data trust.
00:17:31.096 --> 00:17:36.080
Is the information accurate, consistent, secure, and trustworthy?
00:17:36.080 --> 00:17:38.643
Discipline two, meaningful measurement.
00:17:38.643 --> 00:17:40.104
What are we measuring?
00:17:40.104 --> 00:17:42.224
Are we measuring what actually matters?
00:17:42.224 --> 00:17:45.116
Discipline three, analytics and learning.
00:17:45.116 --> 00:17:49.098
Are we moving beyond reporting toward understanding and prediction?
00:17:49.098 --> 00:17:52.300
Discipline four, decision intelligence.
00:17:52.300 --> 00:17:55.702
Does information actually improve leadership decisions?
00:17:55.702 --> 00:17:58.203
Discipline five, digital enablement.
00:17:58.203 --> 00:18:03.146
Does technology reduce friction, connect information, and improve work?
00:18:03.146 --> 00:18:05.949
Discipline six, responsible innovation.
00:18:05.949 --> 00:18:09.471
Are we using emerging technologies, including AI?
00:18:09.471 --> 00:18:14.434
in ways that create value while protecting trust, privacy, safety, and judgment.
00:18:14.434 --> 00:18:23.661
Put those together and data stops becoming a reporting function, technology stops becoming just an IT function, they become organizational capabilities.
00:18:23.661 --> 00:18:27.189
So now let's connect this into the full healthcare excellence framework.
00:18:27.189 --> 00:18:32.968
Leadership and governance excellence determines what leaders pay attention to and how that data is governed.
00:18:32.968 --> 00:18:36.633
Strategic alignment and execution determines what should be measured.
00:18:36.633 --> 00:18:41.750
Operational excellence creates the processes and performance data that we need to understand.
00:18:41.750 --> 00:18:54.386
Workforce and culture excellence affects whether people trust information and feel safe raising concerns, Patient, resident, and community excellence provides outcomes, experience, access, and community insights.
00:18:54.386 --> 00:19:00.488
Financial sustainability and value excellence require strong financial and value intelligence.
00:19:00.488 --> 00:19:07.689
Innovation and transformation excellence depends on technology, experimentation, learning, and adaptation.
00:19:07.689 --> 00:19:09.889
And again, everything connects.
00:19:09.889 --> 00:19:11.869
Let me give you a quick diagnostic.
00:19:11.869 --> 00:19:16.158
Organizations collect too much data and use too little of it.
00:19:16.158 --> 00:19:18.181
Dashboards can become cluttered.
00:19:18.181 --> 00:19:20.855
Different departments use different definitions.
00:19:20.855 --> 00:19:23.377
Leaders debate the numbers instead of the problem.
00:19:23.377 --> 00:19:25.139
Data arrives too late.
00:19:25.139 --> 00:19:28.019
Metrics are reviewed, but no decisions follow.
00:19:28.019 --> 00:19:31.342
Technology is purchased without workflow redesigns.
00:19:31.342 --> 00:19:34.903
Employees create workarounds around the digital systems.
00:19:34.903 --> 00:19:38.967
And then AI is introduced without clear value or governance.
00:19:38.967 --> 00:19:42.709
Frontline teams do not have access to useful information.
00:19:42.709 --> 00:19:45.452
Organizations focus on what is easy to measure.
00:19:45.452 --> 00:19:54.438
rather than what's important to understand, and perhaps most dangerous, leaders become so confident in the dashboard that they stop asking questions.
00:19:54.438 --> 00:19:56.471
That is not data excellence.
00:19:56.471 --> 00:20:04.154
If I removed every dashboard from your executive team tomorrow, which 10 metrics would you immediately ask to have back?
00:20:04.154 --> 00:20:05.235
Think about that.
00:20:05.235 --> 00:20:08.415
Not 50, not 100, just ten.
00:20:08.415 --> 00:20:13.557
What information is so critical that you would not want to run the organization without it?
00:20:13.557 --> 00:20:17.998
If that question is difficult to answer, you may have a measurement volume problem.
00:20:17.998 --> 00:20:21.778
Let's imagine an organization experience rising patient wait times.
00:20:21.778 --> 00:20:25.160
Leadership sees the number, average wait time is increasing.
00:20:25.160 --> 00:20:38.171
The easy response might be we need staff to move faster, but the team digs deeper, they look at the data by location, by day, by time, by provider, by
appointment type, by patient volume.
00:20:38.171 --> 00:20:42.784
Then they combine that with frontline observations, And they discover something.
00:20:42.784 --> 00:20:46.204
The biggest delays are concentrated during certain periods.
00:20:46.204 --> 00:20:49.066
Scheduling templates don't match the demand.
00:20:49.066 --> 00:20:52.477
certain appointment types consistently run longer than planned.
00:20:52.477 --> 00:20:55.296
Late arrivals create downstream disruptions.
00:20:55.296 --> 00:20:58.112
Some providers are using different workflows.
00:20:58.112 --> 00:21:00.514
Now the organization has intelligence.
00:21:00.514 --> 00:21:09.840
The solution might involve schedule and redesign, capacity adjustments, standardized workflows, better demand forecasting, different appointment templates.
00:21:09.840 --> 00:21:12.361
That's better than telling everyone to hurry.
00:21:12.361 --> 00:21:16.202
The data help leadership learn, and learning change the decision.
00:21:16.202 --> 00:21:18.855
That's data analytics and digital excellence.
00:21:18.855 --> 00:21:21.165
So here's a simple tool that I want you to use.
00:21:21.165 --> 00:21:24.087
I call it the decision intelligence test.
00:21:24.087 --> 00:21:27.509
take one dashboard that your leadership team uses regularly.
00:21:27.509 --> 00:21:30.470
For each major measure, ask three questions.
00:21:30.470 --> 00:21:34.192
First, what decision could this measure influence?
00:21:34.312 --> 00:21:37.294
Second, who's responsible for making that decision?
00:21:37.294 --> 00:21:41.576
And third, what happens when the measure moves outside of expectations?
00:21:41.576 --> 00:21:46.513
If nobody can answer those questions, Ask whether the measure belongs on the dashboard.
00:21:46.513 --> 00:21:49.134
Take these five questions back to your team as well.
00:21:49.134 --> 00:21:54.975
First, what are the 10 most important measures that we use to understand organizational performance?
00:21:54.975 --> 00:21:59.816
Second, which important decisions are we currently making with weak information?
00:21:59.816 --> 00:22:03.497
third, where do leaders or departments disagree about the data?
00:22:03.497 --> 00:22:09.558
Fourth, what technology is creating unnecessary friction for our workforce or our patients?
00:22:09.558 --> 00:22:14.440
And finally, what are we currently measuring that nobody is actually using?
00:22:14.440 --> 00:22:17.278
That last question can be surprisingly powerful.
00:22:17.278 --> 00:22:19.678
So I want to leave you with four assignments.
00:22:19.678 --> 00:22:22.438
Assignment one, the dashboard test.
00:22:22.438 --> 00:22:32.990
Choose one dashboard, remove every measure that does not clearly support a decision, a priority, or a meaningful performance question, and see what remains.
00:22:32.990 --> 00:22:35.624
Assignment two, the data trust test.
00:22:35.624 --> 00:22:39.496
Pick one important metric And ask where does the data come from?
00:22:39.496 --> 00:22:40.876
How is it defined?
00:22:40.876 --> 00:22:42.437
How timely is it?
00:22:42.437 --> 00:22:44.038
Do people trust it?
00:22:44.038 --> 00:22:46.199
Can we explain measure changes?
00:22:46.199 --> 00:22:49.120
the digital friction hunt.
00:22:49.120 --> 00:22:54.543
Ask one frontline team member what technology makes you work harder than it needs to be?
00:22:54.543 --> 00:22:56.113
And then listen carefully.
00:22:56.113 --> 00:22:59.134
Then identify one friction point worth fixing.
00:22:59.134 --> 00:23:01.476
Assignment for the learning question.
00:23:01.476 --> 00:23:07.360
At your next performance review for every major metric, ask what do we learn from this?
00:23:07.360 --> 00:23:11.342
Not just are we red or green, but what do we learn?
00:23:11.342 --> 00:23:15.375
So as we close today, I want you to imagine two healthcare organizations.
00:23:15.375 --> 00:23:18.487
Both have access to enormous amounts of information.
00:23:18.487 --> 00:23:29.031
The first organization collects it, reports it, builds dashboards, sends the spreadsheets, leaders review the numbers, but the organization does not consistently learn.
00:23:29.031 --> 00:23:37.447
Definitions vary, data arrives late, technology creates friction, meetings become reporting exercises, problems remain.
00:23:37.447 --> 00:23:53.918
Now imagine another organization where the information is trusted, measures are focused, leaders ask better questions, analytics help to explain variation, frontline teams can see performance, technology simplifies the work, AI is adopted thoughtfully.
00:23:53.918 --> 00:24:00.401
Data challenges assumptions, insights create decisions, and every decision creates new learning.
00:24:00.401 --> 00:24:06.024
Both organizations have data, but only one has built intelligence, and that's the difference.
00:24:06.024 --> 00:24:19.230
And this takes us directly into our next domain because every decision that we make, every technology we invest in, every workforce strategy, every operational improvement ultimately requires resources.
00:24:19.230 --> 00:24:24.890
So in episode eight, We'll move into financial sustainability and value excellence.
00:24:24.890 --> 00:24:36.240
We'll talk about mission, margin, stewardship, value, productivity, financial resource, and why financial strength is not separate from mission sustainability.
00:24:36.240 --> 00:24:43.317
Because organizations can't create excellent care indefinitely without the financial capacity to continue doing the work.
00:24:43.317 --> 00:24:46.749
So before we close, I want you to make one commitment.
00:24:46.749 --> 00:24:51.269
The next time someone presents you with a number, Don't immediately accept the conclusion.
00:24:51.269 --> 00:24:53.990
Go ahead and ask, what does this tell us?
00:24:53.990 --> 00:24:55.611
What doesn't it tell us?
00:24:55.611 --> 00:24:56.971
Why did it change?
00:24:56.971 --> 00:24:58.972
What else do we need to understand?
00:24:58.972 --> 00:25:01.134
What decisions should this influence?
00:25:01.134 --> 00:25:03.355
And most importantly, what can we learn?
00:25:03.355 --> 00:25:06.827
Because leadership is not about pretending we have every answer.
00:25:06.827 --> 00:25:10.651
Great leadership is about building the discipline to keep learning.
00:25:10.651 --> 00:25:15.654
Thank you for joining me for episode seven of the Healthcare Excellence Framework Masterclass.
00:25:15.654 --> 00:25:19.347
Today we explore data, analytics, and digital excellence.
00:25:19.347 --> 00:25:22.210
and I want you to remember, great leaders don't guess.
00:25:22.210 --> 00:25:27.257
They learn, data creates visibility, analytics creates understanding.
00:25:27.257 --> 00:25:29.720
Intelligence strengthens decisions.
00:25:29.720 --> 00:25:32.203
Digital systems should reduce friction.
00:25:32.203 --> 00:25:34.186
Technology should serve the work.
00:25:34.186 --> 00:25:39.190
And emerging tools like AI should Create meaningful value, not simply novelty.
00:25:39.190 --> 00:25:40.871
As always, remember this.
00:25:40.871 --> 00:25:44.553
Healthcare excellence isn't achieved through isolated initiatives.
00:25:44.553 --> 00:25:53.937
It's achieved when leaders intentionally align people, purpose, processes, performance, and innovation across the eight domains of healthcare excellence.
00:25:53.937 --> 00:25:58.169
Because better healthcare doesn't happen by chance, it happens by design.
00:25:58.169 --> 00:25:58.980
I'm Jarvis T.
00:25:58.980 --> 00:26:04.184
Gray, and I'll see you in episode eight, Financial Sustainability and Value Excellence.
00:26:04.184 --> 00:26:11.662
Until next time, keep leading, keep questioning, keep learning, and keep building healthcare excellence.