65. Bouncing Back After a Tough Case

<p><span style="font-weight: 400;">The nature of medical practice dictates that we will have tough cases. Patients will die, we will have to deliver bad news, and we will, at some point, make mistakes. We have high expectations of ourselves so when we get figuratively knocked down, how do we get back up? In this episode, performance coach Jason Brooks guides us through strategies for dealing with the emotional and intellectual fallout of a bad case as well as how to re-engage during a shift when the last thing we feel like doing is seeing the next patient.  </span></p> <p><strong>Guest bio: </strong> <span style= "font-weight: 400;">Jason Brooks Ph.D. is a performance coach helping healthcare providers, athletes, and other high-level performers live better, work better, and be better. Check him out at</span> <a href="https://phenomenaldocs.com/"><span style= "font-weight: 400;">Phenomenal Docs</span></a> <span style= "font-weight: 400;">and connect with Jason:</span> <a href= "https://www.facebook.com/jason.brooks.7393"><strong>Facebook</strong></a><strong>,</strong> <a href= "https://twitter.com/phenomenaldocs"><strong>Twitter</strong></a><strong>,</strong> <span style="font-weight: 400;">email doctorjbro@Gmail.com</span></p> <p>We discuss:</p> <ul> <li>The fact that no matter how good you are in your medical practice, you are not immune to a bad outcome [02:20];</li> <li>How to manage the sense of failure and the anxiety that naturally occurs when you’re faced with the same situation again [04:00];</li> <li>The importance of getting prepared ahead of time and expecting bad things to happen [06:00];</li> <li>Channeling the experience into something positive [08:25];</li> <li>Learning to live with and honor these experiences, rather than dread them [10:00];</li> <li>Drawing a lesson from a bad event and making a commitment to apply that lesson [16:30];</li> <li>The value of talking to someone who is able to receive your emotional turmoil in the immediate aftermath of a bad outcome [18:40];</li> <li>Why we shouldn