Case Study 23-01: Priya and the Counterattack

Background

Dr. Priya Okafor has been building toward this conversation for three weeks. The issue — first raised in Chapter 5 — is that Dr. Harmon, the hospital's chief of medicine, reassigned three of Priya's high-complexity patients to a less experienced team without consulting her, citing "resource optimization." Two of those patients experienced measurable care disruptions in the two weeks following the transfer. One required re-intervention.

Priya's concern is not merely procedural. She believes the reassignment was made without adequate clinical consideration, that the resulting harm was foreseeable, and that the lack of consultation with her — as the department head directly responsible for those patients — represents a systemic failure in decision-making protocol.

She has documentation. She has spoken with the two affected patients' families. She has three colleagues who share her view. She has rehearsed this conversation multiple times. She has prepared a two-page summary of the clinical and administrative concerns, organized around specific events and outcomes.

She has asked for thirty minutes of Dr. Harmon's time, framing the meeting as a "clinical review of the patient reassignment process." She knows that naming it a confrontation would cause Harmon to become defensive before they even sat down.

What she has not fully prepared for is what Harmon does when cornered.

The Conversation

Harmon opens the meeting by checking his phone twice before Priya finishes her first sentence. She notes this. She continues.

Priya: "I wanted to talk through the outcome data from the three patient transfers in October. I've put together a summary — two of the three patients experienced complications in the two weeks following the transfer that I believe were attributable to the transition itself. I want to understand how the transfer decision was made and how we can prevent similar outcomes."

She slides the summary across the table. Harmon glances at it without picking it up.

Harmon: "These complications happen. Transfers carry risk. That's medicine."

Priya: "I understand that. What I'm asking about is whether the clinical complexity of these specific patients was fully evaluated before the decision was made."

Harmon: "I think what this is really about is that you weren't consulted. And that's a management issue, not a patient care issue."

Attack type: Personal attack (questioning her motives) combined with a reframe that minimizes her concern.

This is the first move: Harmon has translated Priya's clinical concern into a professional ego complaint. If she defends herself against the ego complaint ("No, this really is about patient care"), she has already moved away from the clinical data. If she accepts the reframe, she has accepted that this conversation is about her feelings about being left out rather than about patient outcomes.

Priya's response: "My concern is the patient outcomes, which are documented in that summary. Whether I was consulted is a secondary concern. Can we start with the outcomes?"

She does not say "that's not what this is about." She does not defend herself. She returns to the data. The broken record, executed without telegraphing that she is using a technique.

Harmon picks up the summary. He looks at it for forty-five seconds — long enough that Priya wonders if the meeting is turning. Then:

Harmon: "Your team's metrics from last quarter were concerning too. I've been meaning to raise that. Response times were up, patient satisfaction scores down. If we're going to talk about how departments are performing..."

Attack type: Deflection — counter-complaint about her own team's performance.

This is deflection in its clearest form: meet my concern about your decision with a concern about my performance. Priya now feels the pull she has felt in other conversations with Harmon: the compulsion to defend her team, to explain the metrics, to establish that she is a good department head before she has any standing to raise concerns about his decisions. If she defends her team, the conversation is now about her team.

Priya's response: "Those metrics are worth discussing, and I'm happy to schedule time for that review. I want to make sure we don't lose what we're talking about today." She writes "Q3 metrics — schedule review" on her notepad and places it where Harmon can see it. "The question I need answered is how the clinical complexity evaluation was done before the October transfers."

The parking lot, executed visibly and specifically: she writes it down where he can see, commits to a follow-up, and returns to the original concern.

Harmon's posture shifts. He leans back. His voice gets quieter — and Priya has learned, over four years of working with him, that quiet is not calm. Quiet is when Harmon stops being defensive and starts being deliberate.

Harmon: "I'm going to be honest with you, Priya. I've had several conversations over the last few weeks about the dynamic in your department. The feedback I'm getting is that things are tense. That there are concerns about your leadership approach. And I wonder if those concerns are affecting your read on situations like this."

Attack type: Personal attack (questioning her competence and leadership) combined with a veiled threat (implied that her standing is uncertain) and a gaslighting element (suggesting her perception of the situation is distorted by her own problems).

This is the escalation. Harmon has moved from "your motives are wrong" to "your judgment is impaired." He has introduced unnamed third parties who have unnamed concerns. He has implied that the problem is not the October transfers — the problem is Priya. And he has done it quietly, almost kindly, which makes it significantly harder to address than if he had shouted.

This is also where many people collapse. Priya feels the pull: Who said what? What are they saying about her? What did she do? The unnamed accusation is a trap: if she asks who said what, she is now defending herself against an unverifiable claim, and the October transfers are history.

Priya's response: "I hear that there's feedback about my department's culture, and I take that seriously. I'd like to know the specifics so I can address them. And I don't want to let that conversation be a substitute for this one. The patient outcomes I'm describing are documented. I'd like to know how the clinical evaluation was conducted."

She holds the thread. She does not chase the unnamed accusers. She expresses genuine willingness to hear the feedback (not dismissal) and declines to let it displace the current conversation. This is possibly the hardest response in the case study to execute — because the threat about her leadership is real, and her instinct is to handle the real threat first.

Harmon: "You've always been very invested in your patients, Priya. Sometimes that investment makes it hard to see the bigger picture. The reassignment was done for capacity reasons that affect the whole hospital, not just your department."

Attack type: Condescending personal attack ("very invested... makes it hard to see the bigger picture") combined with scope expansion (a form of whataboutism — the bigger picture of the whole hospital).

This is perhaps the most calculated move: framing her clinical advocacy as a limitation ("hard to see the bigger picture") while expanding the frame to hospital-wide capacity concerns she cannot possibly contest without more data. If she argues with the framing, she sounds defensive and self-unaware. If she accepts it, she has accepted that her clinical concerns are the product of emotional over-investment rather than professional judgment.

Priya's response: "I understand this was a capacity decision. What I'm asking about is whether the clinical complexity of these specific patients was part of the capacity calculation. A capacity decision that results in patient harm is still a harm that we need to learn from. Can you tell me what the evaluation process looked like?"

She refuses the "over-invested" frame without contesting it directly. She narrows the scope back to the specific: not the capacity policy generally, but the evaluation of these specific patients. And she asks the question she has been trying to ask since she sat down.

What Harmon Does Next

What happens next matters, because Priya has done everything right and the conversation is still not resolved.

Harmon tells her that the evaluation process "followed standard protocol" and that he would be "happy to have his team pull the relevant documentation." This is an implicit concession: if the process followed protocol, documentation exists. Priya thanks him, notes that she will send a formal request for the documentation through the appropriate channel, and confirms the Q3 metrics meeting.

She gets up to leave. Harmon says: "Priya. I hope you understand that raising things this way — going up the chain, pushing on decisions — it creates a perception. I'm not threatening you. I'm telling you as a colleague."

Attack type: Veiled threat, delivered as friendly warning.

She turns. She holds his gaze. She says: "I appreciate that. I'm going to keep doing my job." And she leaves.

Analysis: Priya's Toolkit

What Priya Did Not Do

Just as important as what Priya did is what she did not do.

She did not defend her team's metrics. Even though the Q3 metrics attack was genuinely concerning to her — she knew the numbers were complicated by factors outside her control — she did not take the bait. She would have to mount an entire argument about staffing shortfalls and a flu season spike to defend those numbers fairly. That argument, in this meeting, would have cost her everything she came for.

She did not ask who made the leadership complaints. Even though the unnamed-accusers move was destabilizing, asking "who said that?" would have led her into a conversation about named or unnamed colleagues, about interpersonal dynamics, about whether the feedback was fair. None of that conversation would have recovered the patient outcomes question.

She did not match Harmon's condescension. When he implied her clinical advocacy was emotional limitation, her instinct — she would report later — was to say something biting. Something that would establish, in no uncertain terms, that she was not someone to be patronized. She did not. That restraint was discipline, not weakness.

She did not leave without the commitment she came for. Documentation of the evaluation process — that was what she needed. She got a commitment to provide it. The conversation did not end in agreement or resolution. It ended in a commitment. That is sometimes the best outcome available.

What She Would Do Differently

Priya's debrief, shared with a trusted colleague afterward, identified one thing she would change: she let Harmon see that the unnamed-accusers move landed. A brief pause, a slight shift in her posture, a moment of something that read as uncertainty. She recovered quickly, but she would have preferred not to give him that.

This is the nature of real-world application: even when you know the techniques, even when you have prepared and rehearsed, a well-placed attack can still find the gap between your preparation and your nervous system. The goal is not to be invulnerable. The goal is to recover quickly and return to the thread.

She recovered. She returned. She got what she came for.

Reflection Questions

1. Which of Harmon's attacks do you think was most difficult for Priya to handle? Why?
2. At what point, if any, would it have been appropriate for Priya to name the dynamic explicitly (e.g., "I notice that every time I raise a patient concern, the conversation becomes about my leadership")?
3. Priya chose not to name the "veiled threat" at the end of the meeting as a threat. Was that the right call? What are the arguments on both sides?
4. How does the power differential between Priya and Harmon change the calculus for each of the techniques she used?
5. Priya's final line — "I appreciate that. I'm going to keep doing my job" — is eight words. Analyze what those words accomplish and what they do not say.