Put it to work.
One useful step at a time.

Start with the situation, not the whole book.

You may already know which conversation you have been putting off. Start there. Describe what happened, read the closest example and prepare an opening that sounds like you. You do not need to finish the toolkit first.

Find the right pages in your purchased toolkit.

In the 91-page PDF edition 4.7: difficult conversations begin on PDF page 11; use the preparation page on page 14. For work not being completed, begin on page 15 and use the accountability and support plan on page 18. These are overall PDF page numbers.

A useful first session

Allow about 15-20 minutes for preparation, not for resolving the issue. Write the observed behavior, its impact, two questions and the next step you want to discuss. Use the working page in this companion if you need a short starting point.

What this companion adds

Three fictional OR examples, a fillable preparation page and a plan for trying the approach this week. The full toolkit adds detailed lessons and working pages. This companion is free to use, with or without a purchase.

Keep the work appropriate.

Use your authority and organizational processes. A safety concern may need immediate action before a coaching conversation. Keep patient, personnel and confidential business information in approved workplace systems.

The situation

A coordinator agreed to review a service-line orientation checklist by Friday. Monday arrives and the review is incomplete. You do not yet know whether time, unclear expectations, missing input or follow-through caused the delay.

Check before you conclude

Confirm what was agreed, whether the deadline was understood and whether the protected time you promised was actually available. Do not treat a missing resource as proof that someone refused the work.

A natural opening

"We agreed to review the checklist by Friday, and it is not complete yet. I want to understand what got in the way, including whether you had the time we discussed."

What changes your response

In this example, the coordinator was pulled into coverage. You acknowledge the lost preparation time and discuss a smaller next step with a realistic deadline. If the time and support were available, explore the reason for the missed work and clarify expectations; do not assume the same response fits both situations.

Close with a clear agreement

Agree which section will be reviewed, who will provide missing input and when you will check progress. Ask the coordinator to explain the plan back in their own words. At the check-in, look together at what was actually finished.

At review

Check the actual work and whether the promised support was provided. Record what remains unresolved. Use the formal process when required; this example is routine leadership preparation, not a disciplinary procedure.

The situation

A surgeon asks for a different team and a flip room. The charge nurse running the board has explained the assignment, but the surgeon is frustrated and asks you to overrule it.

Check the issue, then support the decision.

Confirm the team is appropriate for the work under local requirements and ask whether the surgeon is raising a specific capability or safety concern. Verify staffing, room availability and the reason for the assignment. Supporting a colleague does not mean ignoring new information.

A natural opening

"I understand you would prefer a different team. Based on the staffing and assignments we have reviewed, I support this plan. Is there a specific concern about the team's preparation that we need to address?"

Separate preference from a new concern.

A preference alone does not establish that a reassignment is needed. A specific capability or safety concern needs prompt assessment through the proper process. Do not promise a flip room before the staffing and resource plan is authorized.

After the interaction

Check in privately with the charge nurse. Ask how the conversation felt from their side, whether your support helped and what still needs to be clarified. If inappropriate conduct occurred, follow the reporting process; do not minimize it because the schedule continued.

What to review

Did the assignment remain appropriate? Was any concern addressed? Did the team receive consistent direction? A surgeon walking away does not, by itself, mean the relationship issue is resolved.

The situation

An additional room is requested without a confirmed staffing plan. You anticipate late finishes and difficulty covering breaks. The decision belongs to a leader above you, but you are responsible for explaining the operational effects.

Make the concern specific.

Confirm available staff, competencies, expected finish times and break coverage with the responsible teams. Separate what is known from what is only a possibility. Escalate immediate safety concerns through the required process.

A natural opening

"Before we confirm the additional room, can we review the staffing plan? With the current assignments, I cannot identify coverage for these breaks or the expected finish. We need an agreed plan before we make that commitment."

Bring options to the discussion.

Ask the authorized leader to consider the available options and their effects. These may include confirming additional qualified coverage or revising the proposed schedule under local policy. Do not invent a safe staffing number or make a clinical prioritization decision from this worksheet.

What you can promise staff

"I will raise the concern, follow up on the decision and update you by the time we agree. I cannot promise the request will be approved, but I can tell you what is known and what is still pending."

If the discussion is dismissed

Restate the unresolved operational issue, use the appropriate escalation route and keep required records in the approved system. If you still do not have an answer, say so. Arrange a follow-up and consider how earlier planning could help next time.

Keep it brief.

Use roles rather than names. Put formal records in approved systems. These fields have fixed space; save a copy and test one nonsensitive entry before relying on your PDF app.

Prompts for your own preparation

• What happened? What have I verified?
• Why does it matter? What remains uncertain?
• My opening and two questions
• What happens next, who will help and when to check back

Use the fillable PDF or your approved working system. Do not enter confidential information into public feedback.

Day 1: choose and prepare

Choose one appropriate conversation. Read the matching lesson and prepare your opening. Check that the facts, timing and setting are appropriate.

Days 2-3: listen and agree

Have the conversation when feasible. Ask for the other person's account. Agree the action and support rather than reading a prepared speech at them. If the issue requires a formal route, use it.

Days 4-6: provide your part

Provide the support you agreed to. If the plan changes, communicate it. Keep the actual commitment in your approved work system or calendar.

Day 7 or the agreed review: check the work

What was completed? Did you provide the support you promised? What still needs attention? A calmer conversation matters, but check whether the work changed too.

Before you move on

Can the other person explain the expectation? Is the action feasible? Is the support clear? Is there a real review date? If one answer is no, clarify the plan before calling the issue resolved.

Continue only where useful.

Use the toolkit's deeper examples for a different challenge. No additional product or video is required to use this companion. For file help or feedback, visit westclinicalleadership.com/contact. Do not send confidential case details.

Your first useful result

It can be hard to explain your experience when the question catches you off guard. Start with one real example. Practice explaining your part, then rehearse two follow-up questions.

Open the right pages.

In the 96-page Interview Sprint PDF edition 4.7, role-specific practice begins on overall PDF page 42. Build answer 1 and Build answer 2 are on pages 93-94. Use the actual job description to choose the level and topics.

Use a natural answer structure.

Explain the situation, your responsibility, what you checked, what you did, what changed and what you learned. This is a preparation guide, not a script you must recite in a fixed order.

Choose an experience you remember clearly.

Use a real example involving communication, a difficult decision, improvement, accountability or a setback. State what you personally contributed and give appropriate credit to others. Do not invent a percentage or imply causation you cannot support.

What this companion adds

Role-level questions, an annotated answer, a fillable preparation page and a rehearsal route. Questions are original practice material, not verified questions from HCA, Vanderbilt or another employer. No hiring outcome is promised.

Charge nurse or first manager

Question: "Tell us about a time you addressed a concern with a colleague while keeping the work moving." Show your own actions, how you listened and when you involved the responsible leader. Follow-up: "What would change if you became that person's manager?"

Experienced OR manager

Question: "Describe a recurring operational problem you helped improve. How did you identify the cause and involve the team?" Explain the starting point, authority, action and evidence. Follow-up: "What else changed at the same time, and how did you check whether the improvement lasted?"

Director

Question: "Tell us about a decision where surgical demand exceeded available resources." Explain alternatives, cross-service input, the trade-off and who approved the decision. Follow-up: "What did you stop or defer, and how did you manage the effect on other teams?"

Executive

Question: "Describe how you evaluated competing priorities across services." Explain what the organization needed, how reliable your information was, the investment choices, who made the decision and how you reviewed it. Follow-up: "What evidence would have made you change direction?"

If you have not held that authority

Say so. Use the nearest genuine example, then distinguish what you did from how you would approach the larger responsibility. Titles vary; the posting and actual scope matter more than the label.

Weak answer

"I improved communication and built a great culture. I always listen to my team, and everyone trusts me." The interviewer cannot tell what happened, what you did or how you know.

Stronger fictional answer

"Staff told me they raised concerns but did not consistently hear what happened next. I was responsible for the team's follow-up, although some decisions required director approval. I reviewed the open concerns, confirmed who could answer them and agreed when I would update the team. At huddles, I separated what had been decided from what was still pending. Some requests remained unresolved, but staff received the promised updates. I learned not to wait for a final answer before communicating progress."

Why it is stronger

The answer names a recognizable issue, shows the speaker's responsibility, explains specific actions and admits what remained unresolved. It does not claim that communication alone caused a survey-score improvement.

Follow-up to practice

"How did you know staff received the update?" and "What happened when the director had not made a decision?" Prepare a factual answer. If the evidence is limited, say what you know and what you would measure next.

Make it yours without borrowing the history.

Do not use this fictional account as your experience. Replace it with a real event and language you would naturally use. Keep patient, employee and confidential business information out of interview preparation.

Write notes, not a speech.

Use short phrases that help you speak naturally. Save a working copy and test your PDF app. Fields do not expand or calculate.

Prompts for your own preparation

• The question and responsibility in the job posting
• Situation, my role and limits of my authority
• What I checked, decided and did personally
• Result I can support; limits and what I learned
• Two follow-up questions I need to rehearse

Use the fillable PDF or your approved working system. Do not enter confidential information into public feedback.

First practice

Speak the answer aloud. Ask a listener to tell you what problem you faced, what you personally did and what changed. If they cannot identify those points, revise the answer.

Second practice

Ask the listener to challenge one claim: "How do you know?", "Who else contributed?" or "What did not work?" Practice acknowledging limits without becoming defensive.

Prepare your questions about the job.

Ask what success means in the first 90 days, what authority comes with the role and what support is available. Ask how conflicting priorities are resolved and how onboarding will be provided.

Before the interview

Check the role scope, examples, dates and numbers. Prepare a genuine reason for wanting the role. Choose questions that are not already answered in the posting.

After the interview

Record what you learned about the work, support and expectations. Note one answer to improve. Use what you learned to decide whether the role and its expectations are a good fit. The hiring decision may depend on factors you cannot see.

A useful standard

The answer is clear, relevant, truthful and specific about your contribution. This is a self-review checklist, not a validated hiring assessment. File help and feedback: westclinicalleadership.com/contact.

Choose the work in front of you.

If you are new to the role, first ask what you can decide and who can help. If a familiar OR problem keeps returning, choose that one issue and check what is happening before adding another fix.

Find the right pages.

In the 104-page Launch System PDF edition 4.7: first-case starts begin on overall PDF page 7; the action page is 10. Turnover begins on page 11; the worksheet is 14. The Appointment Field Guide begins on page 49; Agree the appointment is page 51.

What you will prepare

Prepare a short proposal: the problem, what you know, what needs checking, one action, the approval needed and a review date. You are preparing a decision, not authorizing a change outside your role.

What this companion adds

An example of how to measure first-case starts, questions to investigate delays, a short planning page and steps for getting started this week. Do not skip required safety checks to meet a time target. Follow local policy for urgent concerns.

Use the example carefully.

The times, rules and findings on the next pages are fictional. They illustrate how to think through an operational problem, not a universal standard or a result achieved by WCL customers.

Define the local measure first.

For this example only: include the first scheduled elective case in each room, scheduled before 9 a.m. on weekdays. Compare actual patient-in-room time with scheduled patient-in-room time. No grace period is used. Other facilities may define the window or tolerance differently.

Keep a delayed case in the group.

A first case scheduled at 7:30 that enters the room at 9:05 is still a delayed morning first case. Select cases by their scheduled time, not by whether their actual arrival happened before the cutoff.

Separate intentionally later starts.

A first case scheduled at 10:00 that enters at 10:00 is on time but outside this example's morning group. A 10:30 first case entering at 10:42 is delayed against its own scheduled time and belongs in a separate review.

Separate other cases.

A second case is not a first case even if scheduled before 9 a.m. An add-on is a case added after the established schedule, not simply an afternoon case. Review add-ons and urgent or emergent cases using the relevant scheduling and urgency rules. Track cancellations separately.

Agree the rules before reporting.

Specify the schedule reference point, eligible cases, start event, tolerance and exceptions. Do not move scheduled times after the event to make performance look better. Patient-in-room and incision time are different measures.

A small fictional sample

Four eligible first cases are scheduled at 7:30, 7:30, 8:30 and 8:45. Actual room times are 7:30, 7:42, 8:29 and 9:05. Two of four are on time: 50%. Delay minutes are 0 + 12 + 0 + 20 = 32. Early arrival does not offset another case's delay. Four cases are not enough to establish a trend.

Reconstruct the sequence.

Using approved records, check patient arrival and preparation; required documentation and site marking; anesthesia and surgeon readiness; room, instruments and equipment; team availability; and communication and transfer. Ask the teams involved what happened. A single delay code is not proof of the full cause.

Distinguish a readiness issue from a handoff issue.

In this fictional example, preparation was complete, but the receiving team was not notified and transfer had not been arranged. Starting preparation earlier would not directly address that handoff gap. Other cases may have different or multiple causes.

Choose one small test with the responsible teams.

Agree who confirms readiness, who receives that message and who arranges the next step under local policy. Test the agreed handoff on a limited, appropriate group. Required safety checks remain unchanged.

Review the result and the burden.

Compare similar eligible cases, delay minutes and completeness of the handoff. Ask whether the change created extra calls, interruptions or delays elsewhere. Do not claim success from one good morning or assume every remaining delay is preventable.

This is preparation, not an operational order.

Confirm authority, policy and necessary review before implementation. Use de-identified planning notes; keep operational records in approved systems. Save a copy and test fields before longer work.

Prompts for your own preparation

• Problem, starting facts and what remains unknown
• Local definition and evidence source
• One proposed change and the teams involved
• Approval, responsible role, time and support needed
• Review date, measures and reasons to change or stop

Use the fillable PDF or your approved working system. Do not enter confidential information into public feedback.

Days 1-2: confirm the starting point

Agree the role or problem. Review the relevant records and definitions with the responsible people. Ask what explanation is missing before selecting a solution.

Days 3-4: agree the proposal

Explain the verified concern, alternatives and likely effects. Agree who can approve the change, who will do the work and what staffing and support they need. Before the meeting ends, make sure everyone knows what was decided.

Days 5-7: begin only when authorized

Implement the limited action if the necessary approval and support are in place. Otherwise, identify the unresolved decision and the next follow-up. Use more time when the decision or preparation needs it.

At the agreed review

Record what changed, what did not, the quality of the evidence and the effect on other teams. Decide whether to continue, adjust or stop. Use a longer observation period when needed.

Research behind the first-case example

Definitions vary. AORN Expo 2026, Erika Klika and colleagues, poster 797256, describes a before-9-a.m. first-case project; results were pending. Foglia, Ruiz and Burkhalter (2017), An Evolutionary Change in First Case on Time Starts, uses a different morning window and a five-minute grace period. Neither establishes the fictional rule here as universal.

Source access and help

Sources checked October 16, 2026: aornexpo2026.eventscribe.net (poster 797256); clinsurggroup.us/articles/GJPM-1-104.php. The interactive first-case example includes direct research links when published. File help and feedback: westclinicalleadership.com/contact.

Choose one useful result.

A busy week can leave you wondering what you actually moved forward. Choose one thing you want to improve or follow up on. Keep your required daily work in your existing calendar and approved systems.

Open the right pages.

In the 46-page 90-Day Leadership Planner, read the examples on pages 4-6, set your dates and priority on pages 8-10, then plan Week 01 on page 11 and review it on page 12. These are overall PDF page numbers.

Make room before making a promise.

Confirm what can move, what can be delegated with agreement and what support is available. Do not assume work will fit because it matters.

Keep the commitment visible.

Record the next action and review date in your approved calendar or work system. Use the planner for preparation and reflection; it does not send reminders or sync with the website.

What this companion adds

A worked week, a short fillable plan and an honest review. Use this free companion on its own or with the 90-Day Leadership Planner. No account, subscription or video is needed.

The concern

Staff say they raise questions but do not always hear what happens next. Some answers require director approval. The manager cannot promise that every request will be granted.

This week's result

Give an accurate update on two open concerns at the next huddle, including what is still awaiting a decision. Confirm the information with the responsible leaders before presenting it.

Time and support

Reserve a short preparation period and request the missing information. With appropriate agreement, defer a nonurgent formatting task. Required work and safety responsibilities continue.

When the plan changes

A staffing issue reduces preparation time, and one decision is still pending. The manager gives the confirmed answer, explains what remains open and communicates the next update date. The team hears where things stand instead of wondering whether their concern was forgotten.

The honest review

The promised update was given, but one concern remains unresolved. The manager kept the promise to update the team, even though the decision was still open. Ask whether the message was clear. One huddle alone cannot show that trust or engagement scores improved.

What happens next

Follow up with the decision-maker before the next update. Carry forward the specific unresolved action, not every item from last week. Keep identifiable staff concerns in approved systems.

Use concise, nonsensitive notes.

Save a working copy. Test one entry, close and reopen it in a form-supporting PDF reader. Fields have fixed space and do not calculate.

Prompts for your own preparation

• One useful result and why it matters
• Next action, responsible role and date
• Time and support; what can move with agreement
• If blocked, what will I communicate and when?
• Review: completed, unresolved and the next adjustment

Use the fillable PDF or your approved working system. Do not enter confidential information into public feedback.

Notice what moved forward.

Planning a conversation, having it and seeing a change in the work are different steps. Give yourself credit for following through, then check whether the concern improved. If it did not, use that information to decide what comes next.

At the end of the week

Ask what was completed, what remains open and whether the plan was realistic. Notice the effect on other work. Keep, change or stop the next action based on what you learned.

If you use a 90-day cycle

Set actual 30-, 60- and 90-day review dates. Thirteen weeks covers about 90 days; the final week may extend beyond day 90. At each checkpoint, compare the current position with your starting point and explain the limits of the evidence.

Use the right scope.

A coordinator may improve a handoff within an assignment. A manager may address a recurring team concern. A director may coordinate a cross-service decision. The same short routine can support different responsibilities, but does not replace a business case or governance process.

Know when to reset.

If the priority lacks approval, time or support, revise the plan with the responsible leader. Persistent overload is not solved by filling more boxes. Urgent concerns follow the required process immediately.

Get help or share feedback.

Tell WCL which section you used, what you were trying to do and what was unclear. Do not send patient, personnel or confidential business details. Visit westclinicalleadership.com/contact.