Sink or Swim

The Dilemma

Now, in my experience procedural errors are often just the symptom of a deeper, systemic issue. A bootcamp might be the answer, but we can’t propose a solution until we’ve validated the problem. I’ve scheduled a 30-minute follow-up call for you with Dr. Sinclair. Your job is to go into that meeting, build on her initial analysis, and use your strategic questioning skills to either confirm her diagnosis or uncover the real root cause.

Dr. Sinclair: As I told Skye, the data is clear. Our new ICU nurses are making too many small procedural errors. I’m convinced a simulation-based ‘bootcamp’ is the best way to get them up to speed and ensure patient safety.

You: Dr. Sinclair, thank you for that clarity. The data you’ve gathered is a fantastic starting point. Before we dive into the bootcamp idea, could you walk me through the types of errors you’re seeing most frequently?

Dr. Sinclair: Certainly. A lot of it is related to the new patient monitoring software we rolled out last year. They’re missing alerts, misinterpreting readings, and not documenting their actions correctly. The system is complex, and the veteran nurses just ‘get it’ because they’ve been using it for so long.

You: That’s very helpful. It sounds like the issues are centered on the new software. In your experience, when do these errors tend to happen? Is it during a particular time of day, or when dealing with a specific type of patient case?

Dr. Sinclair: That’s an interesting question. Now that I think about it, the mistakes happen most often when the new nurses are on their own. When they’re paired with a veteran, the error rate is almost zero. It makes sense, of course; the veterans know what they’re doing.

You: That’s a fascinating insight. It sounds like the veterans’ presence is a key factor. What kind of formal training or support do the new nurses currently receive to get them to that point?

Dr. Sinclair: They’re supposed to be in our mentorship program. A new hire is always paired with a veteran for their first six weeks. But anecdotally, I’m hearing it’s not working. The veteran nurses are territorial. They don’t think the new hires can handle the new system, so they don’t let them get their hands dirty. They tell them to just ‘watch,’ because it’s faster and they know it will be done right. It’s hard for me to argue with them when the data shows the mistakes happen when the new nurses are on their own. The bootcamp is the only way I can think of to plug the hole.

You: That sounds incredibly challenging. Putting yourself in the veteran nurses’ shoes for a moment, what do you think their biggest concern is?

Dr. Sinclair: They’re worried about patient safety. They feel that taking the time to properly train a new person will slow them down and could put a patient at risk. They’re not wrong to feel that way. I just… I wish the mentorship program was still working. It used to be the heart of our culture. It was how we built bonds and strengthened the whole team. I’m sad to see it failing like this…

---

The Decision

---

The Debrief

Solving the cultural problem is the most ambitious and, in a perfect world, the ‘right’ thing to do. It’s a strategy grounded in a deep Organizational Needs Assessment, attempting to solve the true cultural problem. By proposing to revive the human mentorship program, you’re applying Social Learning Theory, which recognizes that the most valuable knowledge transfer often happens through observation and collaboration. However, as you saw, this path carries immense project risk. It requires a bigger budget and buy-in from a group of already stressed-out veteran nurses.

Solving the performance problem is the pragmatic choice. It’s a brilliant example of working within constraints to deliver a tangible solution to the client’s stated performance problem. This path focuses on a very targeted Task Needs Assessment, identifying the specific procedural skills the new nurses need and building an efficient solution to address that gap. The ‘digital mentor’ is a form of Just-in-Time Resource, providing support precisely when it’s needed. The risk, of course, is that by creating an effective workaround, you may have inadvertently reinforced the ‘sink or swim’ culture, solving the symptom but not the disease.

So, how did you get from a request for an onboarding bootcamp to this complex discussion about hospital culture?

The first and most important principle is to always dig for the root cause. This is arguably the most valuable skill a consultant possesses. A client may come to you with a problem they’ve already diagnosed, but it’s important not to take their word as the absolute truth. Their observations might be symptoms of a larger, underlying issue. Your job is to challenge that initial assumption, not by arguing, but by investigating.

In the conversation with Dr. Sinclair, the “procedural errors” were the symptom. A bootcamp would have been a treatment for that symptom. By asking a series of probing questions, you successfully dug deeper and uncovered the disease: a failing mentorship program and a toxic ‘sink or swim’ culture. You proved that the errors weren’t the real problem; they were the result of the real problem.

This happens in every project, in every industry:

• A client might say, ‘Our sales team is bad at closing deals’ (the symptom). A root cause analysis might reveal the marketing team is providing them with unqualified leads (an organizational problem).
• A manager might say, ‘My team doesn’t know how to use the new software’ (the symptom). The root cause might be that the software’s user interface is confusing and unintuitive (a UX problem, not a training problem).
• A call center might have ‘low accuracy rates’ (the symptom). The root cause could be something as simple as poor lighting in the office causing eye strain (an environmental problem).

The primary tool for this investigation is strategic questioning. You didn’t challenge Dr. Sinclair’s ‘bootcamp’ idea directly. Instead, you used a series of open-ended and probing questions to help her uncover the deeper issue herself. This is what separates a consultant from a developer.

Active listening is the foundation of any successful consultation. It’s more than just hearing words; it’s about making the other person feel truly heard and understood. A key technique here is paraphrasing, where you summarize the other person’s point in your own words to confirm your understanding.

Probing questions are designed to dig beneath the surface of a problem. They are the “why” and “how” questions that move a conversation from a surface-level symptom to a potential root cause. You used a classic probing question to get more context: “In your experience, when do these errors tend to happen?” This moved the conversation from the “what” (the errors) to the “when and where,” which was the key that unlocked the deeper problem.

Your most powerful move was your final question: “Putting yourself in the veteran nurses’ shoes for a moment, what do you think their biggest concern is?” This is a great empathetic question. It shifted the focus from a sterile discussion about procedural errors to a deeply human conversation about the fears and anxieties of her veteran staff, which was the final key to uncovering the true cultural issue. This is how you find the human-centered story behind the data.

The ‘digital mentor’ is still a form of training, but it’s a different kind. It’s a highly targeted performance support tool designed to solve the immediate problem of procedural errors. This approach is like applying a tourniquet to stop the bleeding. It’s a fast, effective, and often necessary first step to stabilize a critical situation. It solves the immediate performance issue, but the bullet (the toxic culture) is still in there. If left unaddressed, it can lead to a deeper infection down the road.

Fixing the mentorship program is the attempt to actually remove the bullet. It’s a non-training solution focused on fixing the organizational problem itself: the broken mentorship and the burnout culture. This is the true long-term solution. However, non-training solutions are not always as simple as creating a job aid. A systemic fix like this is a form of organizational surgery. It’s complex, it’s costly, and it requires deep buy-in from multiple levels of the organization. There’s a real risk that you can correctly diagnose the disease but find that the organization isn’t ready for the cure.

---

The Bottom Line

An instructional designer’s job isn’t just to find the ‘perfect’ solution; it’s to find the best possible solution within the given constraints. Our greatest value as consultants is our ability to see both the symptom and the disease.

This means we have a professional responsibility to present the client with the full picture. We must be able to offer the pragmatic ‘tourniquet’, the targeted solution that stops the immediate bleeding. But we must also present the case for the more difficult ‘surgery’, the systemic solution that will solve the underlying problem. We show them the full picture, the wound and the cure. The final choice of treatment is always theirs.

Community Insights

Real-world feedback from instructional design practitioners polled on LinkedIn, Reddit, and ID forums such as ONILP and Useful Stuff.

of polled professionals advised to solve the performance problem first.

• Solve the Performance Problem 70%
• Solve the Cultural Problem 30%

The prevailing logic was that while culture is the root cause, it's a systemic issue outside a contract ID's immediate scope; the pragmatic solution is to apply a "band-aid" performance fix now while advocating for a larger cultural initiative later.

Featured comments

I'd apply a band-aid fix (option 2) while working on the deeper issue (option 1). Option 2 may give you a tiny bit of breathing room and/or plausible deniability with your leadership, but it sounds like the root issue can't be addressed by training alone. That's always a harder sell — but it is a more permanent fix.

If I could only do one, I would solve the performance problem. Turning company culture around is a herculean task, and you've got to have buy-in from the top down. Even if it's just one department, it's still a large task and can take months or years. In the meantime mistakes are still being made.

I work in a place that manufactures biologics, where strict Quality Assurance is embedded in what we do. Medical facilities outside of drug manufacturing often don't have the QA mindset you'd imagine. Much of the software we use was designed by engineers, and UX was last on their list. As an ID you can't do anything about third-party software, but it's something to consider.

I think it would also be useful for IDs to study engineering controls — basically setting up your machine or environment to force correct behaviors, like the deadman switch on a lawnmower. Most medical device training and manuals are pretty poor across the board, enough that a good one stands out.

Culture represents the behaviors that are allowed to exist and no amount of "culture training" is going to change that.

The performance problem needs solving now, while the culture problem sounds more like it needs a company-wide initiative that's likely more under the purview of management or HR. My thoughts are on the 'bootcamp' idea and whether it's the best choice. Healthcare tends to be fast-paced: would nurses really have the time to sit down and go through a learning module, let alone retain it?

I wonder if creating a job aid would be more effective — a one-page handout or a searchable library of microlearning modules so newer nurses could find the information on their specific questions quickly. They'd probably master the database usage through the repetition of looking things up and retain it more easily.

In this medical context, it's performance hands-down! Error could mean a wrong diagnosis resulting in a fatal outcome. Culture would be too ambitious and complex, going beyond your scope (and possibly interest/expertise).