Norman Leandro

Tag: decision-making

  • The quiet role of judgment in regulated healthcare

    Regulated healthcare systems like to believe they run on rules.

    Policies are written. Procedures are approved. Training is completed. Decisions are documented. Everything appears controlled, auditable, and repeatable. On paper, very little is left to chance.

    And yet, the truth is simpler and less comfortable: rules do not run healthcare systems—people do.

    What actually determines outcomes, especially when situations are complex or imperfect, is not the policy itself, but the quality of judgment applied around it. That judgment operates quietly, often invisibly, and frequently without acknowledgment.

    Judgment is always present, even when organizations pretend it is not

    There is a persistent fiction in regulated environments: that judgment can be minimized, engineered away, or replaced by sufficiently detailed guidance.

    It cannot. Every interpretation of a policy is an act of judgment. Every decision about whether a case truly fits the guidance is judgment. Every escalation—or decision not to escalate—is judgment.

    When judgment is not acknowledged, it does not disappear. It simply goes underground.

    Why regulated systems prefer silence over honesty

    Judgment creates discomfort because it resists clean accountability. Rules are easy to defend. Judgment is not.

    As a result, organizations default to the language of compliance, adherence, alignment, and documentation. These concepts are necessary, but insufficient. They allow systems to avoid the harder question: how professionals are expected to think when policy does not clearly decide the case.

    Suppressing judgment does not eliminate risk—it redistributes it

    Professionals learn to choose the most defensible option, escalate to avoid responsibility, and over-document to compensate for uncertainty. The system becomes slower, less confident, and more brittle.

    The fiction that discretion and judgment are the same

    Judgment is often confused with discretion. Discretion implies freedom of choice. Judgment is reasoned interpretation within constraints.

    When systems collapse these concepts, they produce decisions that are technically defensible but intellectually weak.

    Experience fills the gap, but erratically

    Because judgment is not taught, it is learned informally. Senior professionals develop internal models over time. Others learn what attracts scrutiny rather than how to reason well.

    Judgment matters most when systems are under stress

    Judgment becomes visible when evidence is incomplete, guidance conflicts, timelines compress, or ethical tensions surface. These are also the moments most likely to be reviewed in hindsight.

    Training talks about judgment, but rarely takes responsibility for it

    Judgment is expected but not defined, relied on but not protected. Training focuses on clarity, while real value lies in preparing for uncertainty.

    Making judgment explicit is not a threat to control

    Acknowledging judgment strengthens governance. Policies set boundaries. Judgment determines how responsibly they are navigated.

    Closing thought

    Healthcare systems do not fail because people use judgment. They fail when judgment is used silently and defensively.

    The most dangerous judgment is not the visible one, but the one the system refuses to admit it depends on.

  • 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.