Hey, welcome to the briefing. What I'm going to cover with you today is this. Four patients, one error. Where did the failure stop? Finding an error tells you something failed. It does not automatically tell you how far that failure reached. That distinction matters because the second a serious error becomes visible, everybody wants movement. People want containment. Teams want direction. Patients and families deserve answers. Leadership wants to know what happened, what remains at risk, and what has to change. All of that pressure is legitimate. The problem starts when urgency creates confidence faster than the evidence does. On August 14th, 2026, Ascension St. Thomas Hospital, Midtown in Nashville, identified a pharmacy medication error affecting four joint replacement patients. Ascension later publicly stated that those patients received potassium phosphate instead of the intended anesthetic medication, Mepavacaine. The hospital said all four patients experienced adverse health reactions and received immediate medical care. That is serious. And I want to be careful with how we handle it, because it would be easy to take a serious event, look at the pieces that became public, and start pretending we know exactly how the entire failure happened. We do not. Based on what is publicly known, we do not have Ascension's complete internal root cause chain. We do not have every conversation, every decision, or every condition investigators examined inside the workflow. So I'm not going to manufacture those details just to make the story cleaner. What we do have is enough to examine a very important leadership problem. Ascension said it conducted a comprehensive review and confirmed that no other patients were affected. The organization also publicly described additional safeguards involving medication storage, scan alert verification, pharmacist verification, and independent outside review of its mitigation plans. Something went wrong. The organization had to determine how far the known failure reached before corrective changes could be aimed at a clearer operating picture. The error tells you where to start looking, it does not tell you where to stop. A serious error creates understandable pressure for visible action. Somebody wants the workflow stopped, somebody wants medications moved, and somebody wants retraining. Somebody wants another verification step, somebody wants instructions out before the next case begins, and some of those things may end up being exactly right. But uh the harder question is what evidence supports them, because a correction can look decisive and still be aimed at the wrong boundary. You can correct too narrowly, correct too broadly, or add a control that looks impressive and does not actually address the condition that produced the exposure. You can also add so much process that the correction creates new handoffs, new delays, and new opportunities for confusion. At that point, the corrective action has started breeding in captivity. The leader still has to find the bound the actual failure boundary. I mean I want to separate something here. This is not criticism of Ascension for moving quickly. Based on its public statement, the organization reviewed the scope, reported the event, implemented additional safeguards, and brought in independent quality experts to review and validate the mitigation plans. The leadership lesson is in what had to happen between discovering the error and trusting the correction. That is where in-depth analysis lives. The public record gives us the event, the later scope determination, the corrective controls, and continuing outside and regulatory review. It does not give us every internal reasoning step connecting those things. If I look at the corrective actions and declare that storage, a scan alert, or one individual explains the entire event, I would be filling an incomplete read with confidence. That is not analysis. That is storytelling with operational consequences. And in healthcare, fan fiction is a terrible root cause method. You do not get to invent the missing chapter because the ending made you uncomfortable. Let's bring this down to a level you can actually use. Imagine you are a pharmacy operation supervisor supporting the response after a serious medication error has been identified. This is an illustrative scenario, and I am not saying this is how Ascension handled the event internally. You are not diagnosing patients, you are not determining treatment, you are not independently conducting the regulatory investigation, you are not redesigning pharmacy safety policy by yourself. Qualified pharmacy, clinical, quality, safety, and regulatory professionals own those responsibilities. Your responsibility is narrower, but it is still real. You are responsible for helping control the affected workflow, while the people with the appropriate expertise determine what happened, what remains uncertain, and what needs to change. Now you are under pressure. The error is identified. Leadership needs information. Staff need direction. People need to know what work can continue, what has to stop, what records and process information need to be preserved, and what has actually been confirmed. The visible problem is obvious. The wrong medication reached patients. That is enough to demand immediate attention. It is not enough to answer every question that comes next. Was this limited to one preparation or one storage location? And did another workflow share the same exposure? Was the issue limited to those four known patients? Which safeguard was supposed to prevent this? And which proposed correction actually addresses the condition? Those questions matter because the answers can change the move. If the boundary is narrow, the correction may be narrow. If the boundary is wider, the correction has to account for that. If you do not know the boundary yet, going directly from discovery to final correction is premature. That does not mean do nothing. I want to be very clear about that. Healthcare does not stop operating because leadership wants another meeting. Immediate protective action may be necessary through the organization's approved process, and that is immediate protection. But immediate protection and final correction are not automatically the same thing. The first move may be the Cori, it may control exposure while the team builds a better read. That does not make it the finished answer. This is where in-depth analysis becomes relevant. In-depth analysis is used when the action path reaches a point where a critical variable is missing, and continuing confidently would risk making the wrong move. The question is not whether the team would like more information. Of course they would. The part that matters is whether the missing information can change the decision. That is the threshold. If it cannot change the move, you may not need to stop. If it can materially change what action is responsible, then ignoring it is not decisiveness. It is guessing with authority behind it, and that can become dangerous very quickly. Go back to the supervisor. The visible event is known. Leadership is asking what needs to change before the affected workflow can be trusted again. One person says move the medications. Another says retrain everybody, and someone else wants another verification. Another person wants to stop a broader set of activity until the review is complete. I understand every one of those instincts. Nobody has to be incompetent for this problem to develop. The pressure itself creates the danger. People want to prevent another event. That is a good instinct. But good intent does not remove the requirement for a sufficient read. If the team does not know whether the condition was isolated or systemic, that unknown can change the correction. If another workflow may share the same exposure, that can change the correction too. If the team does not know what part of the process failed to prevent the event, that can change the correction. That is where the action path hits the hard stop, not because people are afraid to make a decision, because the next decision depends on something they do not yet know. And this is where leaders get uncomfortable because stopping can look weak. The event is serious. People expect movement. Leadership wants an update. The team wants to know what to do. Somebody's going to ask, what are we changing? And the honest answer may be we know something has to change, but we do not yet have enough evidence to define the final boundary of that change. I respect that answer and I respect it because it tells the truth about the operating condition. There is a major difference between saying, I do not know, so I am avoiding the decision, and saying this specific variable can change the decision, so I'm stopping this action long enough to resolve it. One is avoidance and the other is disciplined analysis. And ah, let me sharpen that because analysis gets blamed for a lot of bad leadership. People hear analysis and picture three committees, four dashboards, two consultants, and a decision that somehow died of natural causes six weeks ago. That is not in-depth analysis. That is bureaucracy conducting an autopsy on a decision nobody had the courage to make. If nobody can tell me what variable we are trying to resolve, who owns the analysis, what evidence matters, or what allows us to move again, then we are not analyzing. We are drifting. A disciplined halt has a reason, a missing variable, an owner, and an evidence requirement. Most importantly, it has a point where the team knows enough to make the next decision. The Ascension response gives us a clean example. Ascension said its comprehensive review confirmed that no additional patients were affected. Think about what that does operationally. Before that determination, the organization has a known event affecting four patients and an open question about how far the known patient impact extends. After that review, the publicly reported scope is narrower. That does not tell us everything. It does not close every investigation. It does not establish every cause. But it changes what the organization knows. That is what useful analysis is supposed to do. It should reduce an uncertainty that matters and make the next decision more precise. It should change the quality of the move. Now look at the safeguards ascension publicly described. The organization said medications would be stored separately and distinctly marked. It described a mandatory hard stop with independent verification for certain spinal medication scan alerts. It described a second trained pharmacist conducting final visual and physical verification for spinal medicine workflows. It also said independent third-party quality experts were engaged to review and validate the mitigation plans. Those are defined controls, and so they are more specific than telling everyone to be more careful or simply retraining the whole team. Because one of the weakest things leadership can do after a serious failure is make the corrective language broader than the analysis. Everybody pay more attention. Everybody double check everything. Everybody slow down, everybody owns safety. Okay. If the corrective plan is everybody be extra careful forever, congratulations. You have invented anxiety as a control measure. What specifically failed? What are you asking people to do differently? What evidence tells you that change addresses the condition? Because if the answer is everybody and everything, I want to know whether the evidence actually supports a boundary that large. Every new control carries cost. It consumes attention, time, and capacity, and it can add handoffs, delays, or new variation. But that does not mean avoid controls because they are inconvenient. It means the control should earn its place and the evidence should support why it exists. The objective is not to look aggressive after a failure. The objective is to prevent recurrence without damaging parts of the operation that were not part of the problem. Back to our illustrative supervisor. Your team needs direction. One group is focused on immediate containment. Quality and pharmacy leaders are reviewing the event. Clinical owners are handling patient-related responsibilities. Leadership wants to know whether other patients or workflows could be involved. Your responsibility is not to take all of that over. Your responsibility is to understand where your part of the operation intersects with the missing variable. Maybe the same storage configuration exists somewhere else. Maybe another team uses the same verification path. Maybe staff have already started acting on informal information before verified direction reaches them. Those are operating questions, and they matter because people inside the workflow need one shared version of what is known. Think about what happens when leadership moves before that exists. A broad correction goes out. Medications get moved. New verification requirements appear across multiple workflows. People start following temporary instructions created under pressure. One department interprets the direction one way, another interprets it differently. Someone builds a local workaround. Somebody else stays with the original process because they never received the same update. Now the organization is investigating the original failure while simultaneously introducing new variation into the workflow. Five departments can leave the same meeting with six versions of the new rule, which is impressive if the goal was to franchise the confusion. That makes the read worse. Because now when you see something different, you have to ask whether it belonged to the original condition or whether the emergency correction created it. That is overcorrection. The event is serious, so leadership acts everywhere. It looks forceful. It may actually make the operating picture harder to control. Now look at the opposite. Leadership changes only the most visible point. The known medication is moved. The immediate location is checked. Everybody decides the event was isolated. Normal work resumes. But nobody has confirmed whether another part of the workflow shared the same exposure. Now the correction looks clean. The risk may not be. That is under correction. The organization moved quickly and stopped asking questions too early. Both failures come from the same mistake. Leadership selected the correction before understanding the boundary. And then we get to accountability. This is where I care a lot about getting the read right. A serious medication error creates emotion. It should. People were harmed. Nobody should sanitize that. But emotional seriousness does not lower the standard for assigning responsibility. It should raise it. Before leadership decides who failed, leadership needs to understand the authority, information, safeguards, instructions, resources, workload standards, and operating conditions around the event. That does not protect someone from legitimate accountability. It protects accountability from becoming inaccurate. If someone had clear standards, proper training, usable safeguards, and deliberately ignored them, that matters. If the workflow created conditions where a reasonable person could make the same error, that matters too. Justice requires you to connect accountability to what the person actually controlled. And I do not care how emotionally satisfying the fast answer is. Find the person closest to the event. Correct them, retrain the team, send the memo, close the incident. That can create closure very quickly. It can also leave the failure exactly where it was. Accountability improves after the read improves. That does not mean wait forever. It means know what you are holding someone accountable for. I have made versions of this mistake. Not this specific kind of event. I mean the leadership mistake of seeing a visible failure, feeling pressure to correct it, and wanting to move directly to the thing that looks like the answer. The work teaches you that the first answer can feel clean because it removes uncertainty from your head. That does not mean it removed uncertainty from the operation. Pressure makes people want one answer. One cause, one person, one fix. It makes the situation feel controllable. Some operating failures do not arrive in that shape. They arrive as one visible event, followed by several unknowns that have to be narrowed. The disciplined leader does not make the problem more complicated than the evidence requires, but they also do not make it simpler than the evidence allows. Overanalyze everything and the organization freezes. Act on the first plausible explanation every time and the organization becomes confidently wrong. In-depth analysis sits between those failures. It is not about knowing everything. It is about knowing what you must know before the next move becomes responsible. That is the better better read. The question is not do we have every answer? The question is what missing variable could change the action we are about to take. That is much more useful. Suppose your team knows the immediate event, has protected the affected workflow, and now needs to decide whether a broader process change is necessary. One variable may control that decision. Does the same exposure exist somewhere else? If the answer is no, a targeted correction may be appropriate. If the answer is yes, the organization may need a wider response. That variable changes the move. That is when the halt earns its place. Now suppose somebody wants information that sounds useful but will not change what happens next. Maybe it matters later. But if it does not change the action in front of you, do not let interesting information masquerade as necessary information. Pull what changes the decision. That is discipline. And this helps explain the value of outside validation. Ascension said it engaged independent third-party quality experts to review and validate the mitigation plans. That does not mean an outside expert automatically understands the organization better than the people inside it. It means the plan is being exposed to another qualified review. Somebody else gets to chow gets to test the assumptions and ask whether the controls actually align with the risk being addressed. A team working under the same pressure can share the same blind spots. Sometimes you need qualified friction. A room full of people nodding at the same mitigation plan is not validation. It is synchronized agreement with hospital badges. You need somebody capable of saying, show me why this control addresses that condition. Now connect this to the larger direct action system. In-depth analysis sits inside deepen, but it depends on a cleaner CSA read. Before a leader can determine whether deeper analysis is required, they have to separate what is confirmed from what is assumed. What happened? What do we actually know? What is still unverified? What part of the workflow remains reliable? If you cannot separate those things, you cannot identify the right missing variable. CSA improves the read. Deepen helps determine what kind of problem you are dealing with and what kind of movement makes sense. In-depth analysis becomes relevant when you reach a point where action depends on an unknown capable of changing the decision. And notice that does not mean the entire organization freezes. Some immediate protective actions continue. Patient responsibilities continue through the appropriate clinical channels. Investigation continues. Work outside the affected boundary may continue, if it can do so safely, under the organization's approved process. The halt should stop the decision that cannot responsibly move. Not everything. A controlled halt isolates the uncertainty. It does not spread paralysis through the organization. Then pro matters because action and delay both carry consequences. What happens if you move too soon? Could the correction be too narrow? Could it create unnecessary workflow burden? Could you communicate something that later has to be reversed? What happens if you wait? Does the current condition remain exposed? Does workload accumulate? Does uncertainty create different local responses? Does patient access suffer somewhere else? Those are real trade-offs. Then TMC becomes important because once the direction is clear, the operation needs one version of that direction. Who owns the change? Who needs to know what changes now, what stays the same, what is still being reviewed? When is the next update? A strong analysis can still fail in execution if every department walks away with a different interpretation. The larger system supports the tool. But in-depth analysis remains the center. The question is whether the missing variable can break the decision. Now bring this into your own environment. You do not need a medication error to recognize this pattern. Maybe your patient access team is considering changing a callback workflow because patients are waiting too long. The first read says staffing. Okay, what variable could change that decision? Maybe the backlog is concentrated in one specialty. Maybe two task pools are receiving the same work and creating duplication. Maybe the team is measuring open tasks but not completed patient contact. Those are completely different problems. Different variable, different correction. Maybe you have a referral problem. The first instinct is add another coordinator. Before you add headcount, what would change the decision? Is it actually volume? Is the documentation incomplete? Is the receiving office rejecting referrals? Is the system status wrong? Is ownership unclear? Again, you do not need every answer. You need the answer that changes the move. Different conditions create different actions. The discipline is the same, and when pressure tells you to act, inspect what you are about to assume, then ask whether that assumption could change the decision. If it cannot, keep moving. If it can, that is where you may need to stop the action path long enough to get the answer. And remember the halt has to end. This is where analysis can become its own failure. The team identifies the question, the review begins, data gets collected, experts get involved. Then everyone becomes strangely comfortable staying inside analysis because nobody ever defined what answer was sufficient. That is drift. If the analysis has no end condition, eventually the dashboard is just keeping the decision as a pet. The purpose of in-depth analysis is not to make the leader better informed forever. It is to improve the next decision. So what must be true before you move again? What evidence is enough? What finding changes the path? That is the decision condition. In the ascension event, one publicly reported scope question received a clear answer. The organization said the comprehensive review confirmed no additional patients were affected. That is decision-relevant information. The mitigation plan also moved into defined safeguards and outside review. That does not mean every investigation is closed. It does not mean every operational decision has to wait until every investigation ends. Different decisions require different levels of understanding. You may know enough to protect one workflow while the broader investigation continues. You may know enough to implement one verified safeguard while another question stays open. You may know enough to resume one activity while another remains paused. The analysis should match the decision. That is what keeps it disciplined. Here is what right looks like to me. When a serious problem becomes visible, separate the known event from the unknown boundary. Ask what has actually been confirmed. Ask what you're assuming because the event is serious, visible, or emotionally charged. Then identify the unknown that could change the next move. Not every unknown. The one that matters. Ask what happens if your assumption is wrong. Does the correction become too narrow? Does it become too broad? Does another workflow remain exposed? Do you create unnecessary burden? Do you assign responsibility inaccurately? Do you communicate something you later have to reverse? If the answer is yes, that variable deserves your attention before the next move, and then decide what evidence is enough, not perfect certainty. Enough understanding for responsible action. That is where in-depth analysis earns its place. It keeps urgency from becoming false readiness. It keeps visible activity from becoming a substitute for understanding. It keeps accountability attached to evidence, and it gives the corrective action a better chance of actually matching the failure boundary. Four patients were known to be affected. One serious error had become visible. The next leadership question could not stop at how do we fix what we just saw. It had to include where did the failure stop? And Ascension said its comprehensive review confirmed that no additional patients were affected. That finding mattered because it narrowed what the organization knew about the reach of the event. The organization then publicly described additional safeguards and outside validation. That progression is worth paying attention to. Something went wrong. The organization needed to understand enough about the scope to move responsibly. Corrective controls followed, review continued. That is not a story about perfect people in a perfect system. Things happen in complex operations, people make honest mistakes, processes, fail. Safeguards sometimes do not prevent the event they were supposed to prevent. And sometimes conduct may eventually warrant stronger accountability. But you do not get to skip the read just because the consequence is serious. The leadership standard is what happens next. Do we react to the first visible point and declare the problem understood? Do we assign blame before the operating condition is clear? Do we add controls because visible action feels safer than uncertainty? Or do we identify the variable that can change the decision? Build enough understanding to resolve it, and then move with a correction supported by evidence. That is in-depth analysis. The error tells you something failed. The analysis tells you what you still need to understand before the correction can be trusted. When you are ready to go deeper with this tool, go to www.direct action dot io slash course dash directory. Open the course directory, find the course connected to in depth analysis and deepen, and start there. That is where the deeper application belongs. Thanks for listening to the briefing.