Ep. 039 The Dance Begins: Curing Operational Blindness in Healthcare
47 min
•Feb 24, 2026about 2 months agoSummary
Dr. Jake Taylor Jacobs introduces his new book 'Operational Blindness' and defines a systemic condition where healthcare leaders cannot see dysfunction in their operations because measurement systems and reporting structures fail to surface critical problems. He argues that organizational failures stem from broken systems, not incompetent people, and demonstrates how visibility, proper metrics, and feedback loops enable transformation across industries.
Insights
- Operational blindness is a systemic architectural problem, not a people problem—replacing leaders without fixing systems produces identical failures repeatedly
- Measurement systems create invisible blindness by directing attention to activity metrics while masking outcome failures that matter to the organization
- Upstream functions (SPD, manufacturing, IT) cannot see their downstream impact because reporting structures create information silos between interdependent departments
- Organizations adapt to dysfunction rather than fixing it, making workarounds standard procedure and embedding blindness across generations of employees
- Transformation requires connecting upstream activity to downstream outcomes, building systemic feedback loops, and restructuring how information flows across departments
Trends
Healthcare organizations cycling through leadership without improvement signals systemic rather than personnel failuresShift from activity-based metrics (turnaround time, output volume) to outcome-based metrics (readiness, customer impact, value creation)Growing recognition that military-influenced hierarchical structures in healthcare are outdated and require systemic redesignIncreasing need for cross-departmental visibility systems that connect upstream operations to downstream organizational outcomesMovement toward feedback mechanisms that enable organizational learning rather than blame-driven problem-solvingRecognition that development pathways and people investment are strategic, not optional, for organizational performanceExpansion of operational blindness diagnosis beyond healthcare to manufacturing, technology, professional services, and retail sectors
Topics
Operational Blindness Definition and DiagnosisSystemic vs. Personnel-Based Problem SolvingMeasurement Systems and Metric SelectionSterile Processing Department (SPD) OperationsHealthcare Supply Chain and OR EfficiencyReporting Structure and Information SilosFeedback Mechanisms and Organizational LearningLeadership Development and People InvestmentCross-Functional Visibility and Downstream ImpactOrganizational Transformation MethodologyHealthcare Cost Overruns and Root Cause AnalysisSurgical Services and Instrument ManagementQuality Metrics and Risk ManagementSystem Redesign vs. Personnel ReplacementBelief Systems and Organizational Culture
Companies
Sims Healthcare
Dr. Jacobs' consulting firm that developed the Operational Blindness framework and Stereo by Design operating system
IBM
Referenced as case study where Lou Gerstner proved stuck organizations can transform by changing systems, not just pe...
People
Dr. Jake Taylor Jacobs
Host and author discussing operational blindness in healthcare and other industries; operational turnaround specialist
Lou Gerstner
IBM CEO cited as example of leader who proved 'elephants can dance'—that stuck organizations can transform through sy...
Quotes
"You've been operating inside of a system that makes success impossible. You've been measured on things that don't reflect your real impact. That's not a personal failing, that's a system failing."
Dr. Jake Taylor Jacobs
"They couldn't fix what they couldn't see, and they couldn't see what this system didn't show. This is operational blindness."
Dr. Jake Taylor Jacobs
"What you measure shapes what you see. What you see shapes what you manage. And if your measurements are disconnected from outcomes that matter, you're optimized for things that don't matter."
Dr. Jake Taylor Jacobs
"If the people change and the system stays the same and you keep getting the same results, odds are it's not the people, it's the system."
Dr. Jake Taylor Jacobs
"The elephant can dance, but first you have to see the chains. When you can see the chains holding you back, you realize you're tied to a small stake—you can just pull it apart."
Dr. Jake Taylor Jacobs
Full Transcript
Bridge Builders, before we get started today, I have an announcement. Operational Blindness, the book is officially out. I'm super excited about it. This book right here is our best work here at Sims Healthcare. We talk about why healthcare leaders can't see what's costing a million of dollars and how to fix it and how the industry currently right now is not dealing with a people issue. We're dealing with a system issue. If we're having a hard time keeping our best people, if our most tenured talent are aging out and we continuously deal with shortages, there has to be a systemic root problem and not just what we're visibly seeing. We're not just seeing a shortage. We're seeing something else that we believe that in operational blindness we're going to talk about just a little subsector of the health care space. And we hope that it can be a value add to anyone that is watching or listening. So you can go to bread2lead.com forward slash blind, bread2lead.com forward slash blind. So you can get a copy of this book. And if you find us live, we're speaking on stage somewhere. You invite us to your chapter or we're talking to you one on one. Some of you also are awarded a free copy of Operational Blindness. If you're out and about, if you cannot afford the actual book right now, things are just tight right now. What I would encourage you to do, I would encourage you to just listen to this free podcast. There's so many valuable points that we pull out. And I use the podcast as a microphone to the book that was actually written. And if you're newer to leadership, Bread to Lead is a great book to start with. If you're newer to SPD Management Leadership, Built to Bleed is the next great book. This is actually my, I believe, like 11th or 12th book that I've written. You go to Amazon, you will always see it. And so I know some of you that are listening, you're not in health care. So this book, Operational Blindness, is great for health care. However, there are nuggets that you can pull from it that doesn't necessarily cater to your industry because there are some things that are health care specific. But there are lots of things that you can pull from. And I know that there are tons of listeners that are listening that are not in health care, but you engage with the bridge builders every single week. And some of you are in manufacturing, you're in tech, you're you run a logistics company or professional services firm. You found this podcast because you care about leadership and operational excellence. You might be wondering, is this book for you? What I would tell you is this book does use health care specific studies as a case study. because that's my current world that I'm in. That's where we're spending a lot of our time. However, I need you to know those that are listening that don't know me. I'm an operational turnaround specialist and reengineering inefficient systems and operational structures, some of the things that bring me the most joy. And operational blindness, the condition that we tailored than that we named is in every organization all over the country. So those are things that you can purchase to be able to support. And I'm excited about that. And today we're going into pretty much two things. The last couple of episodes we talked about all types of stuff as far as the diagnosis. And the first thing of today, I'm going to be painting you a picture of what transformation looks like and what becomes possible when you can dream outside of the condition that you're in. And then the second point, I'm going to give you a formal definition, the precise clinical diagnosis of exactly what operational blindness is. It's going to be the vision, then it's going to be precision. And next until then, I will see you all because I'm happy to be back. Let's get it. I don't take the lead Since the age of 12, I've been about my father's business At the age of 30, he sent me to his vineyard Welcome back, Bridge Builders. I am your host, Dr. Jake Taylor Jacobs. And yes, I am excited that you are around. And you're back again. In case you don't know, this is episode 39, season 3. This is the Read and Teach series from my newest book, Operational Blindness, which just launched. It's available on bredtolead.com forward slash blind. This is what I'm reading as we're going through this series. So let me catch you up. Episode 35, we were talking about the IBM lesson of Lou Gertzner and how he proved that elephants can dance, that stuck organizations can transform, and that if you change the system and not just the people, you can see transformation in organization that most people dream of. And then we went on to episode 36 where we talked about the healthcare parallel. We showed how SPD is the upstream constraint everyone ignores and named the conditions operational blindness. Episode 37, we talked about the dangerous comfort of invisible beliefs and why the beliefs you don't know are the ones that are actually controlling you. And we talked about episode 38, the beliefs that bind, four specific beliefs that are chaining health organizations and leaders in every organization to dysfunction. And today we're just bringing it all together. What does the future look like when we break free? And what exactly is the condition you're breaking free from? So let's get into it. I want to start off by addressing something directly. some of you are drowning right now you're listening to this podcast because you're looking for a lifeline you're exhausted you're frustrated you're wondering if anything will ever change maybe you're an SPD director you can't understand why your hard work never seems to be enough maybe you're an OR director tired of managing workarounds for problems you didn't create maybe you're a COO who's invested in efficiency initiatives uh that keep hitting the same ceiling and maybe you know you're you're a plant manager maybe you're a CTO whatever your role whatever your industry if you're stuck if you keep hitting that same wall I want you to know something it's not your fault you've been operating inside of a system that makes success impossible you've been measured on things that don't reflect your real impact you've been held accountable for outcomes that you couldn't see or control and that's not a personal failing that's a system failing but here's the other side of the coin now that you know it's a system problem you have a responsibility you can't just throw up your hands and say it's the system while continuing to operate the same way once you see the cage you have to work to escape it and today's episode is about what escape looks like and what exactly you're escaping from and I'm gonna read to you a section in the book that's called the dance begins it starts on page 30 I'm going to read from page 30 to page 32 and the dance begins it says let me return to that hospital conference room where we started picture the CFO with unexplained cost overruns the COO fielding complaints from surgical services the CNO worried about quality metrics the SPD director offering explanations that explain nothing now picture something different picture an SPD leader who can see downstream impact, who knows exactly how the department's operations affect OR efficiency, surgical outcomes, and organizational costs. Picture a team that operates proactively rather than reactively, anticipating needs instead of responding to crisis. Picture a department that speaks the language of outcomes, not activities, that can translate what they do in terms the C-suite understands and values. Picture the surgeon who stops hoarding instruments because they trust the system to deliver. Picture the CFO who can finally trace costs to root causes. Picture the CNO who sees quality risk declining instead of accumulating. This isn't a fantasy. It's what's possible when operational blindness is cured. and everyone told Gerstner that IBM was too far gone to save everyone told him the culture was too entrenched the bureaucracy too thick and the problems too deep everyone said elephants can't dance well Lou Gerstner proved them wrong and your hospital can prove them wrong too let's begin what is operational blindness I want to tell you about two SPD directors I've worked with I'll call them Maria and David the stories illustrate something important about the problem we're trying to solve Maria ran the sterile processing department of a 400 bed regional medical center she had been in the role for eight years her team respected her her metrics were solid and when I first met her she walked me through her operation with obvious pride the turnaround times the productivity numbers the process improvements she had implemented over the years by any conventional measure she was doing her job well then I spent a day in the OR what I what I saw didn't match what Maria had shown me cases were delayed waiting for instruments. Surgeons had personal stashes of equipment. They've accumulated because they didn't trust the system. Circulating nurses spent a significant amount of time hunting down missing items, and the OR director was frustrated. And when I asked about the relationship with SPD, she just shook her head. They tell us everything is fine, she said. The numbers look good, but we're struggling every day. When I shared these observations with Maria, she was genuinely surprised, not defensive, surprised. She had no idea. The dysfunction I witnessed in the OR simply didn't appear on any reports she received or any dashboard she monitored. From where she sat, the operations was working. David's situation was a bit different. The details, but identical in the pattern. He directed SPD at a large academic medical center, a complex operation with high volume and demanding surgeons. David was sharp, experienced, and genuinely committed to excellence. His department had invested in new technology implemented lean processes and tracked dozens of metrics And yet the CFO kept asking why instruments costs were climbing The quality team kept flagging near events The surgical services leadership kept complaining about reliability. David had all the answers for it. Staffing challenges, physician behavior, supply chain issues, volume growth. But the answer never seemed to resolve the problem. When I analyzed this operation, I found the same thing I found with Maria. A profound disconnect between what the department could see and what the organization was experiencing. David's metrics measured activity. The organization's pain came from the outcome. And there was no bridge between them. Maria and David weren't bad leaders. They weren't lazy or incompetent or dishonest. They were experienced professionals doing their best inside a system that kept them blind to their own impact. They couldn't fix what they couldn't see. and they couldn't see what this system didn't show. This is operational blindness. And once you understand it, you will see it everywhere. I want to expand on what you just heard. What transformation actually looks like. I painted a picture in that section. but I want to be more vivid. I want you to imagine an SPD leader who can answer with data whether the OR got what it needed yesterday. Not we processed 400 trays, but we achieved 97% first case readiness, contributed to zero instrument-related delays, and supported 52 surgical cases with 99.8% tray accuracy. that's a different conversation that's outcome language that's visibility imagine a surgical services team that actually trusts the SPD the surgeon who used to hoard instruments in their office they stopped because they don't need to the system delivers what they need when they need it the OR director who used to spend half their day managing workarounds they're focused on strategic initiatives now because the upstream constraint has been relieved. I want you to imagine a CFO who can trace costs to their root causes. The instrument replacement budget that used to be a mystery. Now there's data showing exactly why those costs are climbing and what operational changes would reduce them. The premium labor that used to be just how things are. Now there's visibility into what's structural and um and what's needed to be addressed immediately imagine the cno who sleeps better the quality risk they used to accumulate invisibility invisibly now they're surfaced early addressed systematically and prevented rather than caught the near misses that used to go unreported now there's a culture where reporting drives improvement this isn't fantasy i want to be clear about it what i just described isn't fantasy it's not motivational vision designed to make you feel good it's real and it's happening in healthcare organizations right now i've built these operations we've seen these transformations the same people who are struggling become successful the same departments that were failing become reliable the same relationships that were adversarial become collaborative nothing magical happened the system changed and and i want to pull you back to the universal principle here because this applies far beyond health care every organization has some version of this story manufacturing imagine a plant manager who can finally see how upstream production decisions affect downstream quality metrics who stops getting blamed for defects that originated three steps early in the process. In technology, imagine the infrastructure team that can demonstrate with data how reliability investments prevented outages that would have cost the company millions who moves from call center to strategic enabler in the leadership box. In professional services, imagine back office operations team that can show exactly how their processes accelerate or constrain client delivery. Who gets investment instead of cuts because their value is finally visible. In retail, imagine the supply chain team that can connect their inventory decisions to same store sales performance. Who stops being squeezed for efficiency and starts being optimized for revenue impact. The specifics vary. the principle is constant when you make the invisible visible everything changes when upstream functions can see their downstream impact and communicate the impact in terms leadership understands they stop being overhead and they become strategic when leadership can see the true cost of underinvestment not just the line item savings but the downstream consequences they make different decisions when the system enables a success instead of guaranteeing failure the same people produce different outcomes that's the dance that's what becomes possible now what i just described was destination but you need the map to get there and that's what the book provides it's not just a diagnosis it's the complete framework the cost the cost quantification the transformation methodology the road specific playbook that's what this book does go to bread to lead.com forward slash blind the second portion that I want to read of the book is pages 33 through 35. And then 33 to 35 is the formal definition. It says, let me be precise about what I mean by operational blindness because precision matters. You're naming a problem that most people don't know exists. Operational blindness is a systemic condition in which leaders cannot see the dysfunction in their own operations because the measurement systems, reporting structures, and feedback mechanisms they rely on do not surface them. Several elements of this definition are important. First, it's systemic. Operational blindness isn't a person failing or a personal failing. It's not about individual incompetence or lack of effort. It emerges from the structure of the operation itself, from how information flows, what gets measured, and what gets reported. You can replace every person in the department and still have operational blindness if the system remains unchanged. The leaders affected by operational blindness, this is the second definition, especially with visibility and capability, is that the leaders affected by operational blindness often have the skills, experience, and motivation to fix problems. If only they could see them. The limitation isn't their ability to act, it's their ability to perceive. They're making decisions in the dark. They don't even know that the lights are off. Third, it operates through measurement systems. What you measure shapes what you see. What you see shapes what you manage. And if your measurements are disconnected from outcomes that matter you're optimized for things that don't matter while critical problems go unaddressed the metrics become a kind of camouflage making dysfunction invisible by directing attention elsewhere fourth is self-perpetuating because leaders can't see the dysfunction they don't know what to fix and how to fix it because they don't fix it it persists And because it persists, it becomes normal. Because it becomes normal, it stops registering as a problem even when its effects are felt through the organization. The blindness sustains itself. It's almost like you're having a headache, but you've been having the same headache for a decade. At first, it was an issue you wanted to fix, but you didn't fix it the right way or using the remedy that you thought would work. You just figured that you would just live with a headache for the rest of your life versus going to get an expert and figuring out what's going on and fixing that problem. You live with a headache for the remainder of your life without even knowing what triggers it. It's exactly what this is. And this is why operational blindness is so dangerous. It's so difficult to address. It's not a crisis that announces itself. It's a slow leak that everyone gets used to. The organization adapts to the dysfunction rather than fixing it. And the adaption itself makes the dysfunction harder to see. All right. let's break this down piece by piece, the form of definition. The form of definition, the operation of blindness is a systemic condition in which leaders cannot see the dysfunction in their own operations because the measurement systems, reporting structures, and feedback mechanisms they rely on do not surface it. So we talk about the systemic conditions, which is element one. is talking about how operational blindness isn't a personal failing it's not about individual incompetence or lack of effort it emerges from the structure of the operation itself from how information flows what gets measured and what gets reported and this is critical and crucial you can replace every person in the department and still have operational blindness if the system remains unchanged. I've watched the organizations literally cycle through directors, cycle through consultants, cycle through technology implementation, cycle through technicians, cycle through supervisors, cycle through chief executives, and end up right where they started. Because they kept trying to fix people and replace people and remove people, but nobody actually said wait a minute our system is still the same so it's it's producing brokenness because our system was built in broken parts and people come and go but if the system is broken the outcome remains broken regardless of who's operating within it let me make this universal in any organization manufacturing tech services retail healthcare you find functions where leadership has cycled through managers repeatedly and nothing improves the instinct is to say we keep hiring the wrong people or people aren the same anymore the reality is usually we keep putting people in the same broken system systemic means the problem is the architecture not the individual and the issue that we're dealing with in health care is that we're just throwing people into broken systems and wondering why they're even coming out broken. I want my leader to do more, but I have nothing to actually give them to help them do more. They just need to already have more. From broken system to broken system to broken system, and everyone's just plugging the little spark of little successes you're having. You're taking these little sparks and you're just putting it together with missing parts. Imagine putting a car together with all different parts that don't even fit each other. does the car drive yes it drives does it stop yes it stops but all those parts are built to actually work together no but it's okay because this is something that we've always done and these are the issues that we deal with in organizations in every industry where we stop trying to find the truth because we want to stand on our version of the truth that fits our narrative of our story of our position versus allowing the truth to say hey what may have worked in the past doesn't work in today's time so it's okay to evolve and get better yes your idea was a great idea 10 years ago three years ago two years ago but when the idea or the truth changes the facts change so do you as a leader what I believed in a decade ago after evolution of engineering and process improvement and and in system um um and system manipulation you begin to realize with the more data sets you have the more you can get actual truth and the more truth you have the more efficient and productive you can become at the thing that you do but if I don't have any progression in that stage or in that phase and I'm staying 20 years ago today you're the bottleneck of your organization you're causing the harm and the concern and no I guess I'm saying people first systems always I'm saying people first yes I'm not saying that people don't need development what I am saying is that if your organization has no development structure from beginning to end to actually improve your organizational growth or your actual people in your organization it's kind of funny it's funny that it seems as though when you're farming farmers care more about the well-being of their animals than just the output of the work that they can do for them but if we go into the workforce we say hey man I pay you to do your job yes you're paying them to do the job but the extra additive is that you as an executive as a leader you're also paying extra investing and also the future of that person you're paying them for the job they're doing now the investment is in the growth that they'll have in your organization for later the investment in your people never stop the problem is is that there are leaders in every organization i've ever been to in every industry that i've been to that says hey i pay you for your job so do your job so you want to pay somebody for their job but they have to invest in their own future but you want them to take the investment of their own future and put it in your organization when you put nothing into them that's what a development pathway says it says hey i'm invested in your future i'm paying you for today but i'm investing in you staying so i need to develop you i need to curate you and i need to show you that within our organizational structure we do have room for you and even if you don't have a position for them you can have development for them at least while they're there can they get everything that they can get this is the big piece systemically that we're missing because historically health care has used of the military um as as a big piece of their their recruitment meal mule so a lot of people that were in health care came from the military so they naturally had order structure and system but you forget that somebody invested in that development someone invested in those skill sets someone invested in those soft development skills that are needed that brought structure to health care because historically health care didn't have systemic or systematic structure until the military came back the uh the vets came back from the military and nurses and surgeons and a lot of the surgeries we know today actually were founded and created on the battlefield of war so they brought those mechanisms to the hospital system thus making the hospital system a revenue driver i.e 60 to 70 percent of revenue of hospitals are made up of surgeries surgeries that were created in in things that were built or the industry that was created from being at war so knowing that history now we can understand okay we're we're outdated our system our system is outdated and that is what that's the solution that we're bringing health care we're saying hey We have such great talent here. But has anyone just actually looked at the system? It doesn't matter. The new body set that you put on that car is still a 1920 Camaro. You can put the new kit on a 1920 Camaro. It's still going to drive like a 1920 Camaro. in element two the leaders cannot see this function this is about visibility and capability the leaders affected by operational blindness often have skills experience and motivation to fix problems if only they could see them the limitation isn't their ability to act it's their ability to perceive think about it like this you may have a brilliant SPD director or a talented plant manager a skilled IT leader that knows how to solve the problem they've done it before they want to succeed but they're making decisions in the dark they don't even know that the lights are off because they've been in the dark their entire life like my brother has been blind since birth literally my little brother has been blind since birth he has never seen a light a day so he doesn't know how to operate in the night or the day so when the lights are off and he's making decisions he doesn't even know that the lights are off because his lights have always been off do you all get it so a lot of leaders are are being asked to make decisions based on the the darkness that they're already used to so so so so they see what the measurement system shows them and they manage whatever is seen whatever is in the darkness that they're used to you create the metrics around that and because those metrics are disconnected from outcomes that matter they optimize for the wrong things while critical problems go unaddressed and here's what makes this so insidious the leaders don't know that they can't see they they think they're seeing clearly they have dashboards they have reports they have data um but what they don't have is the connection between what they are measuring and what the organization actually is experiencing they're measuring activity the organization is experiencing outcomes the gap between them is blindness like for an example it's kind of like um in sports in the nba right people that have played ball you know the feel of a game you know the look of a player you can see it because you you were you were you you you played in those shoes but you have people that are really great at analytics that have that brought analytics to the game of basketball and those analytics yes it does work but it doesn't tell you the full story the analytics yes if i'm measuring wingspan and speed gaps and in closing gaps and where i shoot best on on what days yes that has an element to it but the data the true read of that data is what I'm physically seeing it's kind of like the data can show you you have a star but only a feeling can let you know if that person can feel stardom like I can look at data and say oh this guy should be a star but when I look and I feel them when I and I think about the magnetic pull it's not that of a star it's the exact same thing data can only show you data based on the data that you want to see not on the measurements that that need to be seen so it's all subjective and your data can be subjective based on what you choose to see but it doesn't mean what you choose to see is the right data that you should be looking at so you have the measurements you have the systems you have the reporting strokes you have the feedback mechanisms and these are all the the machineries of blindness the measurement system determines what you track what you measure shapes how what you see what you see shapes what you manage and if you if you measure turnaround time but you're but not readiness you're optimized for turnaround time even if faster processing of the wrong things makes readiness worse if you measure output per labor hour but not downstream impact you're optimizing for speed even if speed creates quality problems that cost more than efficiency gains if you measure cost per transaction but not value enabled you cut costs you'll cut costs even if those costs reduce value that exceed the savings the measurement system creates the frame everything outside of the frame now becomes invisible that's why we have to be careful even what we measure when we talk about reporting structures the reporting structure determines what information flows where who sees what what gets elevated and what gets buried and if SPD reports through operations while surgical service reports through clinical there's no structural connection the information doesn't flow between them the upstream can't even see the downstream and the downstream can't see the upstream if the it reports through finance while product reports through the ceo there's a structural gap it becomes a cost to be minimized rather than enabler to be optimized because the ceo is not seeing both sides the reporting structure creates information silos and what happens in one silo it stays invisible to the other unless the other wants to interpret or want to include now if you talk about the feedback mechanisms feedback mechanisms determine whether systems learn does surgical services have a way to provide systemic feedback to spd about their experience not complaints when things go wrong systematic data about what's working and what isn't does the customer facing team have a way to provide systemic feedback to the back office about how their processes affect customer experience if the feedback loop doesn't exist the system can't learn it can't adapt and it can't improve the absence of feedback mechanisms is itself a form of blindness you're not just unable to see the problem you're unable to see whether the solutions are working so we talk about technology ai algorithms that read and talk back to each other and get smarter well what does the algorithm of ai mimic it mimics humans it mimics biology it mimics how things can duplicate itself one to another so our feedback mechanism doesn't have to start with technology our feedback mechanisms can start with process and systems that hold everyone accountable to these feedback mechanisms to get smarter and the only thing different about technology versus humans is that technology doesn't get frustrated when technology forces itself to get smarter because it read new data it fixes the data it recodes it retrains itself now it operates on new data with the human component humans get frustrated when there's a course correction or new data that states that what we've been doing is no longer the most efficient or the best way so we need to counsel those things humans say hey I've been doing it this way even with this new data this way works best for me so I refuse to get better and thus the conflict happens there that's the only difference between technology and humans but the humans that can actually progress and process like technology your system becomes technology without the electronics that's what i'm trying to tell you technology doesn't make elect electronics are what make technology technology is built through people that's why we say people first systems always so now we have a self-perpetuating system that doesn't know how to fix itself so dysfunction that begets dysfunction that begets dysfunction that happens over and over again and that's exactly how blindness sustains itself so if we think about those implications the organization adapts to the dysfunction rather than fixing it the workarounds become standard operating procedure and firefighting becomes the job complaints becomes the background noise new employees join and learn how things work here they absorb the dysfunction as normal they stop questioning what veterans stopped questioning years ago and the system perpetuates itself across generations of employees the beliefs are hardened the assumptions calcify the blindness deepens and this is why operational blindness is so dangerous it doesn't announce itself it doesn't create visible crisis it's slow leaks that every it's a slow leak that everyone gets used to until the building floods and there's mold everywhere and this is the thing that we have to see and have to understand so if you want to look at Some of the reports that we've done, our newest and latest report is our operational blindness index, where we personally 101 surveyed 189 periopileters. And I think that you will be surprised about the report that we received about how many hospitals were actually operating in the blind. Go to SipsHealthcare.com forward slash OBI 10. SipsHealthCare.com forward slash OBI 10 to get access to that report. So here's the teaching part. And here's the application across all industries. I want you to pull this. I want you to take this. I want you to mull it away. And this is how to spot operational blindness in any organization. Before I close, I want to give you something that you can actually use. I got you. I got you. Five questions. Five questions. First question. can your upstream functions tell you with data how their work affects downstream outcomes can SPD tell you how their operations affects OR efficiency can manufacturing tell you how production decisions affect quality customer quality scores Can IT infrastructure tell you how their investments affect application performance? If the answer is no, if the upstream can only report on their internal activity, you have a visibility gap. Question two, do your measurement systems track activity or outcomes? Are you measuring turnaround times or readiness? Are you measuring output volume or customer impact? are you measuring cost per transaction or value creation if you primarily measuring activity you're probably optimizing for the wrong things because if you you can't just look at someone's activity and then decide based on activity that they're a value enabler when somebody can stay busy 40 hours a week and that makes you happy because you're looking at productivity but they created no new value for the company they just appease your productivity log this is why it's very important to be careful what you pay attention to will be what you measure and what you measure will be what you manage what you manage will be what you have to grow question number three do systemic feedback loops exist between interdepartment functions interdependent functions the surgical services provide regular structure feedback to spd not just complaints but data and how does SPD receive it does customer success teams provide regular input to product development product development not just escalation or patterns and how do they receive it the sales provide systemic feedback to operations about what's affecting those close rates and how is it received if feedback is ad hoc as I want to or complaint driven or absent the system can't learn itself you have to build a culture that's okay with short being short sometimes because that's what makes the system get better what i always state problems create new policies that we can now govern and regulate so if a problem is new and we don't have a policy or process for it i can now put a process together for it in a policy to regulate the process therefore we now have a governing loop now we're protected on that end what was now a lot once was once a liability is now a legal strength question four when things go wrong do you look for people to blame or systems to fix when the OR is pressure with SPD do you fire the director or do you examine the measurement the measurement systems when production quality drops do you retain the workers or redesign the process when IT projects fail do you blame the team or do you investigate the structural constraints and if your instinct is to blame people you're probably missing systems you're probably missing system problems and the last question how many times have you replaced leadership in a function without seeing sustained improvement if you cycle through multiple directors managers of vps and the outcomes stay the same you don't have a people problem you have a system problem the people keep changing the system stays the same and the results stay the same that's the clearest diagnosed diagnostic indicator of operational blindness right there people keep changing the system stays the same but the result is the same so if the people change and the system that has stayed the same the entire time and i keep getting the same results odds are it's not the people, it's the system. Fix the system, new people, same results. So your system is what produces your same results, not people. But here's the good news. I want you to take this away. Operational blindness is common. It's pervasive. It exists in organizations, across every industry, but it's also curable. You can build visibility systems, you can connect upstream activity to downstream outcomes you can change measurement systems to track what actually matters you can create feedback loops to enable organizational learning you can structure reporting relationships to bridge information silos you can challenge the beliefs that have calcified over years the elephant can dance bridge builders but first you have to see the chains and when you can see the chains that's holding you back and holding your organization back you're going to realize you're tied to a small stake you can just pull it apart you can do that okay so now that you have a vision of what transformation looks like you have the definition of exactly what operational blindness is the question now becomes how do you actually cure it That's what Stereo by Design is. Stereo by Design is our operating system that we built specifically to cure operational blindness. It addresses every element of the definition. It's systemic. It changes the system, not just the people. It creates visibility, connecting upstream operations to downstream outcomes. It builds measurement systems that track what matters. It establishes feedback mechanisms that enable learning. It breaks the self-perpetuating cycle by surfacing what's been invisible. We've implemented it across healthcare organizations, and the principle applies beyond healthcare, but specifically for the OR and Sterile Processing Department. If you want to see a demo of what this looks like and you're running a hospital that has a surgical department, please go to civshealthcare.com forward slash demo. Let's talk about what the operational blindness has cost the organization. and what it would look like to cure it. Everyone, this is Dr. Jake of Bread to Lead, the business of healthcare. And we're talking about operational blindness today. And we pulled a little bit out the book. I hope you took some of these nuggets. This is a pod class, not a podcast. Our whole purpose is to educate and train you, not to just entertain you. Most importantly, I love you. There's absolutely nothing you can do about it. And I'll see you on the very next show. Peace. I don't take the lead I don't take the lead Since the age of 12 I've been bout my father's business at the age of 30 he sent me to his vineyard