Norman Leandro

Tag: desicion-making

  • From Compliance to Decision Quality

    In regulated healthcare, compliance is the language everyone speaks.

    It is measurable. It is auditable. It is defensible. It scales. It creates consistency and reduces variability in complex systems. In many organizations, it becomes the primary signal of safety: if the process was followed, the system assumes the outcome was acceptable.

    And yet, a mature system eventually runs into a limitation that is difficult to admit:

    compliance is not the same as decision quality.

    Compliance answers the question “Did we follow the rules?” Decision quality answers a different question: “Was the decision reasonable, given what we knew at the time, and the constraints we were operating under?”

    In environments where ambiguity is common and consequences matter, that distinction is not academic. It is operational.

    Why compliance became the default

    The dominance of compliance is not a mistake. It is a rational response to complexity.

    Regulated healthcare environments need repeatable processes, consistent interpretations, clear escalation pathways, and documentation that can survive scrutiny. These are not cosmetic features. They are structural requirements.

    But when compliance becomes the end goal rather than the minimum standard, it quietly changes what organizations optimize for. People learn that the safest posture is not necessarily to reason well, but to demonstrate adherence.

    The system becomes excellent at proving it followed steps. It becomes less reliable at ensuring those steps led to a sound decision.

    The compliance trap: defensible decisions that are not necessarily good

    In practice, compliance can create a decision-making trap.

    When the dominant incentive is defensibility, professionals tend to gravitate toward behaviors that protect them from scrutiny: selecting the most conservative interpretation, escalating uncertainty rather than analyzing it, documenting extensively rather than reasoning explicitly, and prioritizing process completion over decision clarity.

    The outcome is often a decision that is safe to defend but weak in judgment.

    This is not a moral critique. It is a predictable adaptation to systems that reward procedural correctness more than decision maturity.

    What decision quality actually means

    Decision quality is not outcome-based. It is reasoning-based.

    A high-quality decision can still lead to a poor outcome if the environment is uncertain or the evidence evolves. Conversely, a low-quality decision can appear successful if it happens to work out.

    Decision quality asks whether a decision was made with appropriate use of available evidence, a clear understanding of policy intent and constraints, recognition of uncertainty, transparent reasoning, and proportional risk management.

    It focuses on the quality of thinking at the moment of decision, not on hindsight.

    This matters because regulated healthcare often punishes decisions retrospectively—after outcomes are known—while expecting professionals to make judgments prospectively, with incomplete information.

    A system that confuses outcomes with decision quality cannot learn reliably.

    Why organizations struggle to shift from compliance to decision quality

    The shift sounds simple, but it runs into structural friction.

    Compliance is easier to measure than reasoning. It is straightforward to verify whether a checklist was completed. It is far harder to evaluate whether reasoning was sound, especially when reasonable professionals can disagree.

    Compliance protects the organization. Compliance creates defensibility. Decision quality requires nuance, and nuance can feel risky.

    Decision quality exposes uncertainty. Many organizations prefer certainty as a narrative—even when uncertainty is the reality. Decision quality requires admitting uncertainty and still making responsible choices.

    Decision quality requires cultural maturity. A culture that punishes uncertainty encourages defensive compliance. A culture that supports decision quality must make space for thoughtful disagreement and honest trade-offs.

    A practical model: what to build if you want decision quality

    If an organization genuinely wants to shift from compliance to decision quality, it needs more than messaging. It needs operational changes.

    1. Treat policy as a boundary, not an answer. Policies should define constraints and expectations. They should not be treated as a substitute for professional thinking. Training should explicitly address where policy guides strongly, where it guides weakly, and where it does not decide.

    2. Normalize reasoning documentation, not just process documentation. Documentation should capture why decisions were made, not only what steps were followed. This does not require long narratives. It requires clarity: what information was available, what uncertainty existed, what trade-offs were considered, and why the chosen path was reasonable.

    3. Teach boundary cases, not only typical cases. Most training focuses on clean scenarios where policy fits perfectly. Decision quality improves when training includes edge cases, conflicting constraints, situations where multiple compliant options exist, and scenarios where escalation is not an automatic answer.

    4. Define escalation as a tool, not a shield. Escalation should be used to add expertise and oversight—not to avoid accountability. Decision quality increases when teams understand when escalation is necessary, when it is optional, and when it becomes a substitute for analysis.

    5. Build shared language for judgment. Systems cannot improve what they cannot name. Decision quality requires a shared vocabulary for judgment: intent, uncertainty, proportionality, risk trade-offs, and reasoning transparency. Without that language, judgment remains personal rather than professional.

    The uncomfortable truth: decision quality demands trust

    Compliance is often used as a substitute for trust. If people are not trusted to reason, the system tries to control them with rules.

    But decision quality cannot be created through control alone. It requires trust in professional capability, supported by training and accountability structures that evaluate reasoning rather than punish it.

    This does not mean relaxing standards. It means raising them.

    A compliance-driven culture asks: “Did you follow the process?”

    A decision-quality culture asks: “Did you think well within the process?”

    That is a higher expectation.

    Closing thought

    Compliance is necessary. But it is not sufficient.

    Regulated healthcare environments do not become safer by producing perfectly compliant decisions. They become safer by producing consistently high-quality decisions—decisions that are reasoned, transparent, and appropriate to uncertainty.

    If organizations want to strengthen governance, improve outcomes, and reduce brittleness under pressure, the goal cannot stop at compliance.

    Compliance should be the floor. Decision quality should be the standard.

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