Norman Leandro

Category: Essays

  • What medical policy training often gets wrong

    Medical policy training is usually designed with good intentions. It aims to create consistency, reduce risk, and ensure that professionals understand the rules that govern their work. In regulated healthcare environments, that goal is not optional—it is foundational.

    And yet, after spending time close to how policy training is designed, delivered, and absorbed, a pattern becomes hard to ignore: 

    much of medical policy training succeeds at teaching policies, but fails at preparing people to make decisions.

    That failure is rarely obvious. In fact, it often hides behind high completion rates, well‑structured materials, and strong audit outcomes. The gap only becomes visible later, when real decisions must be made under pressure, ambiguity, or incomplete information.

    Mistaking familiarity for understanding

    One of the most common assumptions in policy training is that familiarity equals understanding.

    If someone can:

    • locate the policy,
    • summarize its key sections,
    • identify the relevant definitions,
    • and follow the documented steps,

    They are often considered “trained.”

    But familiarity with content is not the same as comprehension of purpose.

    In practice, this leads to professionals who know ”what” the policy says but struggle to explain:

    • why it exists,
    • what risks it is designed to manage,
    • or how it should be interpreted when circumstances do not align perfectly with the written guidance.

    The training works—until the situation stops being textbook.

    Over‑structuring problems that are not structured

    Policy training tends to favor clean scenarios. Case studies are designed to map neatly onto policy language. Ambiguity is minimized. Outcomes are clear.

    This makes training easier to standardize and easier to measure. But it also creates a distorted picture of reality.

    Real‑world medical and regulatory decisions rarely arrive pre‑structured. They come with:

    • partial information,
    • competing priorities,
    • time constraints,
    • emotional weight,
    • and evolving evidence.

    When training presents decision‑making as a linear process with predictable endpoints, it implicitly teaches that uncertainty is an anomaly rather than a norm. Professionals then experience friction when reality feels messier than what they were trained for.

    That friction is often misinterpreted as a performance issue, when it is actually a training design issue.

    Treating judgment as a risk instead of a requirement

    Another quiet assumption embedded in many training programs is that judgment is something to be constrained rather than cultivated.

    This is understandable. In regulated environments, unchecked discretion can introduce inconsistency and risk. Policies exist precisely to prevent decisions from becoming arbitrary.

    The problem arises when judgment is framed only as a liability.

    When training focuses exclusively on rule adherence, escalation thresholds, and documentation requirements, it can unintentionally signal that independent thinking is dangerous—or worse, non‑compliant.

    The result is not the elimination of judgment, but its suppression.

    People still make judgments. They just do so implicitly, defensively, and without a shared language for explaining their reasoning. Over time, this weakens decision quality rather than strengthening it.

    Teaching the “what” without the “why”

    Many policy training programs are dense with detail and light on intent.

    Participants learn:

    • what is allowed,
    • what is prohibited,
    • what requires escalation,
    • and what must be documented.

    What is often missing is a clear articulation of:

    • what the policy is trying to protect,
    • which risks matter most,
    • and how trade‑offs were considered when the policy was designed.

    Without that context, policies are experienced as external constraints rather than internalized frameworks. Professionals comply, but they do not necessarily align.

    This becomes especially problematic when policies interact, overlap, or appear to conflict. Without an understanding of underlying intent, individuals have no principled way to navigate those tensions beyond defaulting to the most conservative option.

    Confusing escalation with good decision‑making

    Escalation is a critical safety mechanism. Used well, it brings appropriate expertise and oversight into complex decisions.

    But in some training models, escalation becomes a substitute for thinking.

    When professionals are taught that uncertainty automatically requires escalation—without guidance on how to analyze the uncertainty itself—decision ownership slowly erodes. People become hesitant to reason through problems, even when they are well positioned to do so.

    The organization then experiences:

    • increased bottlenecks,
    • slower decisions,
    • higher cognitive load on senior reviewers,
    • and frustration on all sides.

    This is often framed as a workload or resourcing problem. In reality, it is frequently a capability problem created upstream in training.

    What more effective training looks like

    Medical policy training does not need to abandon structure to improve decision quality. But it does need to expand its scope.

    In my experience, training is more effective when it includes:

    • Explicit discussion of policy intent, not just content.
    • Examples where the policy is insufficient, not just where it fits cleanly.
    • Boundary cases, where reasonable professionals might disagree.
    • Reasoning models, not just procedural steps.
    • Language for articulating judgment, so decisions can be explained, reviewed, and improved.

    This kind of training accepts a basic truth: policies are tools for decision‑making, not replacements for it.

    The hidden cost of getting this wrong

    When policy training focuses narrowly on compliance, the costs are subtle but cumulative.

    Organizations see:

    • increased risk aversion,
    • reduced confidence at the decision level,
    • over‑reliance on documentation as protection,
    • and a widening gap between policy design and operational reality.

    None of this shows up easily in dashboards or training metrics. But it shows up clearly in how decisions feel to the people making them—heavier, slower, and more fragile than they need to be.

    Closing thought

    Medical policy training is often evaluated by how well it transfers information. But its real value lies in how well it prepares people to think.

    The goal should not be professionals who know policies perfectly. 

    It should be professionals who understand how policies support responsible decisions—especially when the situation is unclear.

    When training gets that balance right, compliance follows naturally. 

    When it gets it wrong, compliance may still exist, but decision quality quietly suffers.

  • When Guidance Is Clear but the Decision Is Not

    In compliance and governance, some of the most challenging decisions do not arise from vague policies or missing requirements. They emerge in situations where the guidance is perfectly clear—yet the decision remains uncertain. This tension reveals a fundamental truth: clarity in rules does not guarantee clarity in judgment.

    The real complexity often begins precisely where the policy ends.

    Ambiguity persists even when the rule is explicit

    It is easy to assume that ambiguity only appears when policies are poorly written or open to interpretation. But in regulated environments, ambiguity frequently comes from context, not from the text itself.

    A policy can be unambiguous, yet the scenario may introduce variables the rule never intended to address:

    • competing priorities that the policy does not rank,
    • information that technically meets criteria but raises operational or ethical concerns,
    • situations that sit at the edge of what the rule anticipated,
    • decisions where compliance is clear but the implications are not.

    This is the kind of ambiguity that cannot be resolved by re‑reading the policy. It requires judgment, not repetition.

    The limits of policy: where compliance ends and interpretation begins

    Policies are designed to create consistency, reduce risk, and guide behavior. But they are not designed to eliminate the need for interpretation. In fact, the more complex the environment, the more the policy depends on the professional applying it.

    Clear guidance can tell you:

    • what the rule requires,
    • what documentation is needed,
    • what the organization expects.

    But it cannot tell you:

    • how to weigh conflicting signals,
    • how to handle borderline scenarios,
    • how to navigate tensions between compliance, ethics, and operational reality.

    This is the space where governance becomes a discipline of its own.

    Real‑world scenarios where the rule is not enough

    Anyone working in compliance, audit, or policy interpretation has seen cases like these:

    • The documentation satisfies the rule, but the context suggests a different risk profile.
    • The criteria are met, yet the timing or intent raises concerns the policy never contemplated.
    • The rule is clear, but the organizational impact is not.
    • The decision aligns with the policy but conflicts with the underlying purpose of the framework.

    These are not failures of compliance. They are reminders that rules operate in controlled language, while decisions operate in complex environments.

    Decision‑making under uncertainty: the invisible skill behind “clear” cases

    Uncertainty is not always loud. Sometimes it hides inside cases that appear straightforward on paper. The ability to detect that subtle uncertainty—and respond to it responsibly—is a core competency in compliance and governance.

    Effective decision‑makers consistently:

    1. Acknowledge the limits of the policy, rather than forcing artificial certainty.
    2. Identify the true source of ambiguity, which is often contextual rather than textual.
    3. Apply judgment that respects both the rule and the intent behind it.

    This is not improvisation. It is disciplined interpretation.

    Why this distinction matters for compliance and governance

    When organizations assume that clear guidance automatically produces clear decisions, they create blind spots:

    • They underestimate the cognitive work required to interpret borderline scenarios.
    • They overlook the training needed to develop judgment.
    • They treat uncertainty as an exception instead of a structural feature of real‑world compliance.

    Recognizing that clarity in policy does not eliminate ambiguity in practice is essential for oversight, risk management, and organizational integrity. It shifts the focus from “Did you follow the rule?” to “Did you understand the decision?”

    Closing reflection

    Clear guidance is valuable. It creates structure, consistency, and predictability. But it is not a substitute for judgment. The most complex decisions are often the ones where the rule is clear but the situation is not—and it is in those moments that the quality of our governance truly shows.

  • Knowing the Policy Is Not the Same as Understanding the Decision

    Most people working in regulated healthcare environments can recite the policies that govern their work. Fewer can explain why those policies exist, what problem they were designed to solve, or how they should guide a decision when the situation doesn’t fit neatly into the rule. That gap—between knowing the policy and understanding the decision—is where many operational failures begin.

    In my experience, compliance is often treated as a matter of memorization: learn the rule, follow the rule, document the rule. But real‑world decisions rarely present themselves in the clean, structured way policies imagine. Evidence is incomplete. Clinical context varies. Operational constraints get in the way. And people bring different levels of judgment, experience, and risk tolerance to the same scenario.

    A policy can tell you what is allowed. It cannot tell you, on its own, what the right decision is.

    The difference between compliance and judgment

    Compliance is about alignment with requirements. Judgment is about interpreting those requirements in context.

    A person who “knows the policy” can quote the criteria, list the exclusions, and point to the right section of the manual. A person who “understands the decision” can explain how those criteria apply when the case is ambiguous, when the evidence is evolving, or when two principles appear to conflict.

    This distinction matters because regulated healthcare is full of decisions that sit in the gray zone—cases where the policy is technically clear, but the situation is not. In those moments, the quality of the decision depends less on the text of the rule and more on the reasoning behind it.

    Good judgment is not a luxury. It is a regulatory necessity.

    Why training often stops too early

    Most training programs focus on procedural knowledge: definitions, steps, documentation requirements, audit expectations. All of that is necessary, but it is not sufficient.

    If training does not help people understand:

    • the intent behind the policy,
    • the trade‑offs the policy is trying to balance,
    • the risks the policy is designed to mitigate,
    • and the types of ambiguity they are likely to encounter,

    then we are preparing them to follow instructions, not to make decisions.

    Oversight teams see the consequences of this every day: escalations that shouldn’t be escalated, escalations that shouldhave happened but didn’t, inconsistent decisions across teams, and a reliance on “safe” answers rather than thoughtful ones.

    People don’t make poor decisions because they don’t care. They make poor decisions because they were trained to memorize rules, not to interpret them.

    Understanding the decision means understanding the purpose

    Policies are written to guide behavior, reduce variation, and protect patients and organizations. But they are also abstractions—simplified representations of complex clinical and operational realities.

    Understanding the decision requires asking questions that policies alone cannot answer:

    • What risk is this policy trying to prevent?
    • What assumptions does the policy make about the clinical scenario?
    • What is the intended outcome for the patient?
    • What does “reasonable” look like when the evidence is incomplete?
    • Where does the policy expect judgment to fill the gaps?

    When people can answer these questions, they stop treating policies as rigid instructions and start treating them as frameworks for reasoning.

    A more mature approach to compliance

    Compliance is not the opposite of judgment. Compliance requires judgment.

    A mature compliance function does not aim for perfect rule‑following; it aims for decision quality—decisions that are defensible, consistent, aligned with policy intent, and grounded in sound reasoning.

    This shift changes how organizations train, supervise, and evaluate their teams. It encourages:

    • conversations about ambiguity,
    • transparency about trade‑offs,
    • escalation pathways that make sense,
    • and a culture where asking “why” is not seen as resistance but as responsibility.

    When people understand the decision, compliance becomes more than adherence. It becomes a practice of thoughtful, accountable interpretation.

    Closing reflection

    Knowing the policy is the starting point. Understanding the decision is the work.

    In regulated healthcare, the difference between the two determines not only operational accuracy, but also fairness, consistency, and ultimately the quality of care. If we want better decisions, we need to train for judgment—not just knowledge—and build oversight structures that reinforce reasoning, not just rule‑checking.

    That is the space where compliance, governance, and medical policy truly meet.