Culture Hold

The first 30 days are for mapping the operating reality of the hospital against the four breakdown patterns. Not fixing. Not optimizing. Mapping.

Safety first. If this inventory turns up a patient at risk, a controlled drug discrepancy, or anything with a regulator or reporting clock running, act on it now and log it. Inventory, not intervention applies to everything else.

Watch for: Solved problems in the first 30 days teach the team that the MD's job is to solve their problems. Mapped problems give you the data to define the role structurally in Phase 2.

By the end of the phase: A written, positional read on the four patterns as they exist now. This is the baseline you will define the role against in Phase 2.

Staffing Patterns

1. Map who really decides PTO and coverage. Map who actually decides PTO approvals, callout coverage, and shift swaps over a 30-day window. Note the gap between who has the title authority and who is exercising the decision.
2. Find critical shifts staffed below standard. Identify the critical shifts being staffed with people the team knows are not ready, and the structural reason why.
3. Document where staffing decisions escalate. Document the lead technicians and lead veterinarians the team escalates staffing decisions to. Note which ones are exercising authority and which ones are routing everything to leadership.
4. Review the departures you inherited. Note any key team-member departures from the last 90 days you inherited. The departures, not the explanations given for them, are the data.

Escalation Behavior

1. Observe escalation without changing it. For the first 30 days, do not change the escalation pattern. Observe it. Track which cases the team is handling without escalating, which they are escalating, and what the threshold is for each.
2. Log the cases you hear about too late. Note the cases you are learning about from chart review, clients, or owners rather than from the team in real time. These are signals of where escalation is failing in the upward direction.
3. Log decisions escalated that shouldn't be. Note the decisions the team is escalating to you that they are trained and authorized to make themselves. These are signals of where escalation is failing in the downward direction.
4. Note who escalates, by role. Identify which clinicians and which technicians are escalating in each pattern. The signal is often role-specific, not team-wide.

Decision Latency

1. List the decisions sitting unmade. Map the decisions currently sitting unmade in the hospital that you inherited. Categorize by who actually has the authority to make them.
2. Find the conversations avoided before you. Identify the conversations the previous medical director was avoiding. These are usually visible as unresolved interpersonal friction or unaddressed performance issues.
3. Note the decisions you want to make now. Note the decisions you are tempted to make in the first 30 days. The temptation is the signal. Resist making them until Phase 2.
4. Note decisions the team hasn't executed. Note any decision you have already made in Phase 1 that the team has not executed. This is the earliest signal of the relitigation pattern.

Team Friction

1. Map the recurring complaints. Map the recurring complaints surfacing in the first 30 days. Note which ones repeat, which surface from the same people, and which involve the same workflows.
2. Record the team's baseline tone. Note the team's baseline tone in huddles, group chats, and end-of-shift handoffs. This is your reference point for whether tone shifts in Phase 2 or Phase 3.
3. Map who should resolve each conflict. Identify which layer of the hospital should be resolving each conflict, and which layer is actually resolving it (usually the answer is "no one, it's escalating to me").
4. Identify the quiet stabilizers. Note which team members are absorbing interpersonal friction informally. These are usually the quiet stabilizers the hospital is currently dependent on.

The second 30 days are for making the role's structural authority explicit. Not unilateral imposition. Clarifying, in writing, in meetings, and in operational structure, what the role owns, what the layers beneath it own, and what the standards are.

Watch for: The clarification reads as orientation in the first 60 days. It reads as reaction after. Define standards because the role requires them, not to assert authority.

By the end of the phase: Written or clearly communicated definitions of role authority, escalation standards, and ownership layers. One unmade decision made. One avoided conversation had.

Staffing Patterns

1. Define staffing authority for the layer below. In writing or in clearly communicated structure, define what lead technicians and lead veterinarians have authority to decide on staffing: PTO approval thresholds, callout coverage authority, shift swap approvals.
2. Re-route one staffing decision. Identify one staffing decision that has been routing to you that should not be. Re-route it to the appropriate layer. Have the conversation that re-routes it explicitly. Do not just stop responding.
3. Fix why critical shifts are under-staffed. Identify any critical shifts being staffed with people the team knows are not ready. Address the structural reason (training, hiring, or scheduling architecture), not the symptom.
4. Open the staffing conversation with ownership. Schedule the first conversation with ownership about staffing architecture. It does not need to produce a change in Phase 2. It needs to put the architecture on the table. If you are also running Clinical Cadence, bring its schedule and case volume data.

Escalation Behavior

1. Define what gets escalated to you. Define the standard for what gets escalated to you. Be specific: case acuity thresholds, clinical incident criteria, complaint thresholds.
2. Define what does not get escalated. Define the standard for what does not get escalated. Be equally specific. Communicate the standard to the team explicitly in a meeting, not by email.
3. Make escalation failures visible. Make the consequence for both kinds of escalation failure visible: not punitive, visible. Handling something that should have been escalated has a structural consequence; so does escalating something that should not have been.
4. Review one missed escalation with its owner. Identify the one case in the last 30 days that should have reached you in real time and did not. Hold the structural conversation about it with the team member or layer that owned the missed escalation.

Decision Latency

1. Make one overdue decision. Make one decision that has been sitting unmade for more than two weeks. Choose a decision whose absence has a visible cost.
2. Have the conversation you've been postponing. Have one accountability conversation you have been postponing. This is the most important action item in Phase 2. The team is watching whether you will.
3. Document the decision and the conversation. Document the decision you made and the conversation you had. Reference both in Phase 3 to verify they held.
4. Schedule the next unmade decision. Identify the next decision sitting unmade. Schedule the date by which it will be made.

Team Friction

1. Assign who resolves which conflicts. Define explicitly which layer of the hospital owns interpersonal resolution for which kinds of conflict. Communicate it to that layer (lead technicians, lead veterinarians, operations manager).
2. Fix one recurring complaint at its source. For one recurring complaint that has been surfacing, address the structural producer of the complaint, not the surface of it. This usually requires a workflow change, a role-definition change, or a hiring change.
3. Watch how the team's tone shifts. Watch the team's tone shift over the back half of Phase 2. If tone has gotten sharper or quieter, the structural changes are landing as decree rather than definition.
4. Check whether the stabilizers carry less. Identify which informal stabilizers from Phase 1 are now carrying less of the interpersonal load. This is a signal that the structural changes are landing in the right place.

The third 30 days are for verifying that the structure holds when you are not personally producing it. The test of any change made in Phase 2 is whether it functions when you are not on shift.

Watch for: If the structure depends on your presence, the structure has not been built. It has been performed.

By the end of the phase: A structurally defined medical director role that holds when you are not personally producing it. A team that escalates the right things and resolves the others. A reduced burden on your personal calendar that frees capacity for the work the role actually requires.

Staffing Patterns

1. Audit the staffing decisions still routed to you. Audit the staffing layer over the last 30 days. How many decisions routed to you that should have routed to lead technicians or lead veterinarians?
2. Diagnose why decisions still reach you. For decisions that still routed to you, diagnose whether the issue is authority (the layer below does not have it yet), capability (they have it but are not exercising it), or structure (the architecture does not support it). Address the diagnosis, not the symptom.
3. Confirm critical shifts meet the standard. Confirm that critical shifts over the next 30 days are staffed at the standard you defined in Phase 2. Confirm with the layer below you, not by personally staffing them.
4. Revisit staffing with a specific ask. Hold the Phase 2 ownership conversation about staffing architecture again, this time with a specific structural ask.

Escalation Behavior

1. Audit how you still learn about cases. Audit the escalation pattern. How many cases are you still learning about from clients, owners, or chart review? The number should be lower than Phase 1.
2. Audit upward and downward escalation failures. Audit upward escalation failures (what didn't reach you that should have) and downward escalation failures (what reached you that shouldn't have). Address each as a structural conversation, not an individual correction.
3. Recalibrate the escalation standard. Hold a second-pass conversation with the team about the escalation standard. The first pass was definition. The second pass is calibration based on the last 60 days.
4. Talk to the one who still over-escalates. Identify the one team member who is still escalating decisions they are authorized to make. The structural conversation belongs with them specifically.

Decision Latency

1. Repeat the accountability conversation. Hold the second-pass version of the accountability conversation from Phase 2. Verify the change held.
2. Make the next decision on a timeline. Identify the next decision that's been sitting and make it. The latency pattern is reversed not by a single decision but by the team observing that decisions get made on a defined timeline.
3. Schedule a recurring decision review. Schedule a recurring decision review (weekly or biweekly) that surfaces any decision over two weeks old. Make the review explicit.
4. Reopen decisions the team walked back. Note any decision from Phase 2 that the team has quietly walked back. Reopen it. The pattern of relitigation is the pattern that has to break in Phase 3.

Team Friction

1. Audit which complaints persist. Audit the recurring complaints from Phase 1. Which ones have stopped surfacing? Which ones still are? For the ones still surfacing, the structural producer has not yet been addressed.
2. Verify the layer below resolves conflict. Verify that the layer below you is resolving the conflict it was defined to own in Phase 2. If conflict is still escalating to you, the layer below is missing authority, capability, or both.
3. Compare tone to your Phase 1 baseline. Watch the team's tone in the back half of Phase 3 against the Phase 1 baseline. Sharper or quieter tone is a signal that something in Phase 2 was decree, not definition.
4. Check how the stabilizers are carrying. Identify the quiet stabilizers from Phase 1. Are they carrying less? More? The same? The answer is the truest read on whether the structural work landed.