Case Study 25-1: Dr. Priya and the Budget

Background

Dr. Priya Okafor had been head of the Department of Hospital Medicine at Meridian Health for four years. In that time, she had managed to grow the department's patient volume by 22 percent, reduce average length of stay by half a day, and maintain a physician satisfaction score that ranked in the top quartile for academic medical centers of comparable size.

She had done this with a budget that had not increased in three years.

The resource crunch had become genuinely untenable. She was short one full-time hospitalist — Dr. Vasquez had been covering double shifts for six weeks, and two other physicians were making noises about burnout. The department's scheduling software was three versions out of date and creating administrative friction. The single patient liaison position she'd requested for two years remained unfilled. And her department's administrative support had been absorbed into a shared services model that gave her access to 0.4 FTE of administrative help per week — roughly two hours a day.

Dr. Harmon, the Chief Medical Officer, was not hostile. He was genuinely kind, genuinely overextended, and genuinely focused on a capital campaign for the new surgical wing that was consuming most of the organization's financial bandwidth. He responded to Priya's budget concerns with sympathy and with inaction. For two years, "I hear you, let's revisit this next quarter" had been his operative response.

Priya had reached the point where the next quarter had arrived too many times. She requested a formal meeting.

Priya's Preparation: Separating the Person from the Problem

The week before the meeting, Priya sat with her notebook and did something she had not done before: she separated her frustration with Dr. Harmon from the resource problem she needed to solve.

Her frustration with Dr. Harmon was real and legitimate. She felt repeatedly dismissed. She felt that her department's work — unglamorous, high-volume, high-stakes medicine — was less visible than the surgical specialties that generated more revenue and more prestige. She suspected, though she could not prove, that she would have gotten the patient liaison position years earlier if her department were not primarily internal medicine. She was tired of being patient and professional while her physicians burned out.

All of that was real. And none of it would help her in the meeting.

The problem — the separable, addressable problem — was this: her department was operating below safe capacity, the consequences were measurable, and the resource gap was documented. That was not a grievance. That was a solvable organizational problem. And Dr. Harmon was not the enemy; he was the person who had the authority and (she believed) the genuine concern to help solve it.

Priya wrote at the top of her preparation notes: I am not going in there to finally make him see how unfair this has been. I am going in there to solve the resource problem.

This was harder than it looked. She'd been managing her frustration for two years, and there was a part of her that wanted the conversation to be a reckoning as much as a negotiation. She kept returning to her written note.

Identifying Interests: Hers and His

Priya spent an hour on the interests question.

Her stated position: Give me a full-time hospitalist, fill the liaison position, and update the scheduling software.

Her actual interests (what the three whys revealed):

• Why do I need the hospitalist? Because Dr. Vasquez is burning out and if she leaves, I lose an irreplaceable senior physician and the department is in crisis.
• Why does that matter? Because I cannot maintain patient safety and care quality below a certain staffing threshold, and we're approaching it.
• Why does that matter? Because patient outcomes are the thing I'm actually responsible for, and because a care quality incident would be catastrophic for the department and the hospital.

Underlying interest: Maintain patient safety and care quality at a level I can professionally stand behind.

• Why do I need the liaison position? Because physicians are handling navigation tasks that don't require a physician, which is a massive efficiency loss.
• Why does that matter? Because it's burning out my team and adding cost per patient above what it needs to be.
• Why does that matter? Because my department's cost-per-case is higher than it needs to be, which makes us a financial liability to the organization.

Underlying interest: Operate my department efficiently enough to be financially defensible to administration.

Dr. Harmon's likely interests (Priya's best analysis):

Harmon was not simply obstinate. What were his real constraints and concerns?

• Budget pressure: the hospital was in a capital campaign. Every operational dollar allocated to her was a dollar not available for the surgical wing.
• Precedent concerns: if he funded her request, every other department head would have a case for why their situation was equally urgent.
• CMO reputation: he needed to demonstrate good stewardship to the board. Operational crises were CMO problems; quiet underfunding was not.
• Patient safety concern: genuinely shared. Harmon was not the kind of physician-executive who dismissed safety concerns. He needed to be sure problems were real.

Harmon's underlying interest: Maintain financial stewardship while avoiding any patient safety incident that could become a reputational or regulatory liability.

Priya noticed something important in this analysis: the patient safety interest was shared. She wanted to maintain patient safety because she was the physician responsible for her patients. He wanted to avoid patient safety failures because they were organizational liabilities. Different reasons, same interest. This was a dovetail point.

The Meeting

Priya opened by framing the purpose:

"David, I want to spend this time differently than our previous conversations. I don't want to argue about budget lines. I want to show you the patient safety and operational picture as clearly as I can, and then I want us to figure out together what we can actually do about it."

Harmon's expression shifted slightly. The defensive posture she'd expected — the sympathetic but pre-deflecting look — softened.

"I'm genuinely concerned about your department," he said. "Tell me what you're seeing."

Priya had prepared a single two-page document. Not a budget proposal. A patient picture. On the first page: physician hours, patient volume per physician, double-shift frequency for the past six weeks, and the national benchmark for hospitalist patient loads from the Society of Hospital Medicine. On the second page: cost-per-case for her department versus the national average for comparable departments, a projection of what the liaison position would cost versus what physician time spent on navigation tasks currently cost, and two sentences about Dr. Vasquez that said, without editorializing, that Dr. Vasquez had mentioned burnout symptoms in their last one-on-one and that Priya was concerned about her long-term retention.

"The hospitalist load we're running is above Society of Hospital Medicine's recommended maximum," Priya said. "I know every department has pressures right now. But I want to be clear about where we are: we're not inefficient or overstaffed relative to our volume. We're understaffed relative to safe practice."

Harmon looked at the benchmark data. He asked two questions — both about methodology, both genuine. He was not fighting the data. He was trying to understand it.

"What does Dr. Vasquez's situation look like if she leaves?" he asked.

"A recruitment cycle of four to eight months minimum, a temporary locum tenens arrangement that will cost more than a permanent hire, and a period where the remaining physicians are covering her patients. I'll be honest with you — I think the department can manage a departure, but I think the risk of a quality incident during that transition period is real."

This was the first time Priya had said that directly. She had been softening this point for two years.

Harmon was quiet for a moment.

"What are you asking for specifically?" he said.

Generating Options Together

Priya had prepared for this moment.

"Here's where I want to try something," she said. "Rather than me presenting a request and you saying yes or no, can we spend a few minutes figuring out what options actually exist? I've thought of some, but I'm sure there are things you know about budget flexibility that I don't."

Harmon leaned back slightly — she'd surprised him, she could tell.

"Okay," he said. "What have you got?"

Priya's prepared options:

1. Full request: Full-time hospitalist hire, liaison position filled, software update. Estimated annual cost: $380,000.
2. Hospitalist priority: Fill the hospitalist position only. Address liaison and software in next fiscal year. Annual cost: $260,000.
3. Part-time stopgap: Add 0.5 FTE hospitalist for six months while a full hire is recruited, combined with a part-time (0.6 FTE) liaison. Annual cost: approximately $195,000.
4. Cross-departmental resource sharing: Explore whether the new hospitalist could be shared with another department on a scheduled basis, reducing Priya's cost allocation.
5. Navigation task redesign: A process improvement project to identify which navigation tasks could be handled by existing administrative staff with minimal training — might reduce the urgency of the liaison position.
6. Locum arrangement for Vasquez: If Vasquez needs reduced hours for burnout recovery, a temporary locum could cover her cases at comparable cost to a new hire.

Harmon added two options:

7. Deferred equipment budget: The software update might be fundable from a different budget line — capital versus operational — that had more flexibility.
8. Grant funding: There was a Medicaid quality improvement grant cycle opening in two months for which hospital medicine departments were potentially eligible.

They spent fifteen minutes evaluating these options against each other. Priya had her interests clear: patient safety was non-negotiable, retention of Dr. Vasquez was high priority, and the liaison position was a quality-of-life issue for her team that mattered but could wait.

Harmon's constraints became clearer as they talked: the current fiscal year budget had essentially no room; the next fiscal year budget cycle opened in forty-five days; the capital equipment budget did have some room; and there was genuine concern about Vasquez.

Using Objective Criteria

At two points in the conversation, Priya returned to the external data.

When Harmon questioned whether the hospitalist load was truly above safe levels — "I know it's hard, but medicine is hard" — Priya pointed to the SHM benchmark: "The Society of Hospital Medicine recommends a maximum of fourteen to sixteen patients per physician per day. Our physicians have been averaging nineteen for six weeks. That's not a preference; that's a practice standard."

This was not a debate move. It was a shared reference point. Harmon couldn't contest it, and more importantly, didn't want to — he was a physician. He acknowledged the data.

When they discussed the cost of the liaison position, Priya had comparative data: peer institutions with dedicated patient liaisons in hospital medicine showed cost-per-case reductions of 8-12 percent, which more than offset the liaison salary. "I'm not asking for a line item. I'm asking for a position that will save money on net."

Harmon had not seen this data. He asked to keep her document.

The Outcome

They did not reach agreement in the meeting. This was not a failure.

What they agreed: - Dr. Harmon would bring the physician safety data to the next CMO team meeting in two weeks, with Priya's document attached, and advocate for an immediate supplemental budget allocation for a locum hospitalist to cover while a permanent hire was recruited. - The software update would be explored through the capital equipment budget — Harmon was almost certain this was possible. - Both Priya and Harmon would review the grant criteria when they became available in two months. - They would meet again in three weeks to discuss status.

What Priya got immediately: none of the budget lines she'd requested. What she got that mattered: Harmon's active advocacy, a specific follow-up timeline, and a locum arrangement that addressed the most urgent patient safety risk.

What Harmon got: a resource conversation that was concrete rather than emotional, actionable data he could take to the CMO team, and a department head who left the meeting as a problem-solving partner rather than a grievant.

Three weeks later, the locum arrangement was approved. Six months later, the permanent hospitalist position was added in the new budget. The liaison position came through in the following year's cycle. The software update was handled in capital equipment within sixty days.

Analysis: What Made This Work

Separation of person from problem: Priya's discipline in keeping her two-year frustration out of the meeting changed the conversation's character. Harmon had become accustomed to deflecting her frustration. He had not been prepared to engage with her analysis.

Interest focus: Priya found the shared patient safety interest and used it as the foundation of the negotiation. She wasn't asking Harmon to care about her department's wellbeing — she was showing him a patient safety risk that was his organizational concern as well as her professional concern.

Options generation: By coming in with six options rather than one request, Priya gave Harmon room to say yes to something. The positional version of this conversation — "I need X" / "I can't give you X" — had been played repeatedly with no result. The options-based version gave them something to work with together.

Objective criteria: The SHM benchmark and the cost-per-case comparative data were not rhetorical weapons. They were shared reference points. They moved the conversation from "my judgment vs. your judgment" to "what does the evidence suggest?"

BATNA awareness: Priya had thought clearly about her BATNA before the meeting. If Harmon continued to do nothing, her best alternatives were: build a formal case to hospital administration (bypassing Harmon, risky but possible), document the safety risk formally through the patient safety committee (creating a paper trail), or let Vasquez reduce her hours and let the resulting care gap make itself visible to leadership. None of these were great options, which meant Priya genuinely needed the agreement — and she knew it. This kept her from overplaying her hand or walking away prematurely.

Discussion Questions

1. At what point in Priya's preparation did the conversation change character? What specific action shifted the dynamic?
2. Harmon added two options that Priya hadn't considered. What does this suggest about the value of genuine options generation with the other party rather than arriving with pre-formed solutions?
3. Priya used the phrase "I want to be clear" before her most direct statement about safety risk. What function did that framing serve?
4. The meeting did not produce immediate agreement. How does the outcome — a specific follow-up timeline and an active advocacy commitment — compare to what previous conversations had produced?
5. Identify the dovetailing interest in this negotiation. How did Priya find it and use it?