{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/69810d312c62bf72e54d82a7/6ab2ad06325534dc4f36ad8e?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"Ep. 30: The Middle Manager Problem Nobody Talks About","thumbnail_width":200,"thumbnail_height":200,"thumbnail_url":"https://open-images.acast.com/shows/69810d312c62bf72e54d82a7/1790094591939-56e71178-f33f-4a7c-bc33-760f6b60092f.jpeg?height=200","description":"<p>A healthcare CEO can approve a new initiative. Frontline clinicians might even agree that it’s a good idea. And six months later, it can still be completely dead.</p><p><br></p><p>What happened in between?</p><p><br></p><p>In Episode 30 of Viral Healthcare, Dr. Bruce Spurlock examines one of the most overlooked forces in healthcare implementation: middle managers.</p><p><br></p><p>Nurse managers, department directors, medical directors, clinic managers, quality leaders, and operational managers sit between strategy and execution. They’re often responsible for translating an organizational priority into something that actually works on Monday morning—while balancing staffing shortages, competing initiatives, workflow limitations, frontline resistance, and pressure from senior leadership.</p><p><br></p><p>Bruce introduces the concept of virga—rain that falls from a cloud but evaporates before reaching the ground—as a metaphor for healthcare initiatives that leave the executive suite but never truly reach the frontline. He explores why middle managers can become accelerators, translators, filters, or even quiet veto points, often without anyone recognizing the influence they have.</p><p><br></p><p>He also introduces the 2 a.m. test: What happens to your carefully designed implementation when staffing is short, resources are limited, and the people who designed the initiative aren&#39;t there?</p><p><br></p><p>The episode closes with a practical framework for bringing middle managers into implementation earlier, pressure-testing new initiatives, defining what can be adapted, and creating feedback loops that allow operational intelligence to travel back up the organization.</p><p><br></p><p>Because approving change isn&#39;t implementing it—and implementing it isn&#39;t sustaining it.</p>","author_name":"Bruce Spurlock"}