Chapter 7: Tools for Problem Solving and Decision Making

Rational Decision-Making Framework and Cognitive Barriers

Decision-Making Overview in Healthcare Operations:
- Healthcare operational leadership requires rapid, high-stakes problem solving and decision making under resource and time constraints.
- Adopting a structured, rational methodology enhances efficiency, operational consistency, and clinical outcomes.
- The continuous decision-making cycle consists of four distinct phases:
  - Framing: Identifying, defining, and bounding the core problem or operational challenge.
  - Gathering Intelligence: Generating viable alternative courses of action, collecting pertinent operational data, and systematically evaluating each alternative.
  - Coming to Conclusions: Selecting the optimal course of action based on evidence and executing the implementation process.
  - Learning from Feedback: Systematically auditing outcomes, assessing deviations from expected performance, and reflecting on the decision process to inform future problem framing.
Systemic and Behavioral Barriers to Decision Making:
- Barriers in Framing the Question:
  - Plunging In: Initiating action or data gathering prior to clearly defining the underlying problem.
  - Frame Blindness: Setting out to solve the wrong problem due to overlooking alternative, more appropriate problem definitions.
  - Lack of Frame Control: Failing to recognize or manage how a problem is presented, or being unconsciously restricted by a single, narrow perspective.
- Barriers in Gathering Intelligence:
  - Overconfidence in Judgment: Believing assumptions and private assessments are far more accurate than objective data warrant.
  - Shortsighted Shortcuts: Relying excessively on convenient heuristics, anecdotal evidence, or easily available rules of thumb rather than rigorous facts.
- Barriers in Coming to Conclusions:
  - Shooting from the Hip: Relying on intuition rather than systematic analysis and structured multi-criteria evaluation.
  - Group Failure: Succumbing to groupthink, peer pressure, or social conformity, where teams fail to critically evaluate assumptions.
- Barriers in Learning from Feedback:
  - Fooling Yourself About Feedback: Rationalizing failures, attributing poor outcomes to external bad luck, and misattributing successes to pure skill.
  - Not Keeping Track: Failing to track benchmarks, milestones, and actual operational results systematically.
  - Failing to Audit the Decision Process: Overlooking past decision-making mechanics, thereby preventing organizational learning and entrenching recurring errors.

Mind Mapping and Systems Analysis

Foundations of Mind Mapping:
- Mind mapping organizes and develops concepts nonlinearly through visual associative branching.
- The core challenge is positioned at the center of the canvas, while contributing factors, root causes, operational pathways, and potential interventions branch radially outward.
Operational Application: High Accounts Receivable Mind Map:
- Central Problem: High Accounts Receivable balance in a healthcare facility.
- Contributing Systemic Pathways:
  - Billing Delays and Cash Flow Issues: Slow billing processes directly create an accumulation of unbilled and unpaid services, producing missing revenue and limiting capital funding for technological improvements.
  - Electronic Medical Records (EMR) and Information Technology: High accounts receivable strains funding, delaying the acquisition of new computer systems. Operating complex, outdated legacy systems leads to frequent data entry errors and insufficient clinical information.
  - Clinical Documentation Challenges: Poor chart documentation results in missing clinical data and documentation problems, feeding directly into billing denials.
  - Coding Discrepancies: Inaccurate physician coding and administrative coding errors produce insurance claim denials.
  - Payer-Specific Reimbursement Dynamics: Denials stem from distinct payer categories, including Private Insurance (e.g., Blue Cross Blue Shield), public programs (Medicare and Medicaid under the Department of Health and Human Services), and uninsured self-pay populations.
  - Claim Denial Drivers: Denials are frequently issued because procedures are deemed not medically necessary, services are not covered under the patient's plan, or documentation contains incorrect or missing information.
  - Systemic Resolution: Resolving high accounts receivable requires implementing Plan-Do-Check-Act (PDCA) quality improvement cycles to correct systematic billing and documentation problems.

Mind map of High Accounts Receivable causes and systemic interactions

Process Mapping and Cross-Functional Flowcharting

Principles of Process Mapping:
- Process mapping creates a visual representation of operational workflows, tracing inputs, sequence transformations, decision gates, delays, and final outputs.
- It serves as a core diagnostic tool across major process improvement frameworks, including Lean production, Six Sigma, the Balanced Scorecard, Root-Cause Analysis (RCA), and Failure Mode and Effects Analysis (FMEA).
Step-by-Step Procedure for Process Mapping:
1. Assemble and Train the Team: Involve multidisciplinary staff from every level and operational area touched by the workflow to capture the actual process rather than an idealized policy.
2. Determine Process Boundaries and Granularity: Define exact starting and stopping points, establishing the scope and level of detail needed to address the specific operational issue.
3. Brainstorm Tasks and Subtasks: List operational activities exhaustively and order them sequentially (utilizing tools such as sticky notes for rapid reordering).
4. Construct the Formal Flowchart: Draft the process flow utilizing standardized diagramming notation, prioritizing flow accuracy over visual refinement.
5. Validate Flowchart Accuracy: Review the flowchart with frontline personnel and administrative stakeholders, updating the diagram to correct discrepancies.
6. Collect Operational Performance Data: Measure cycle times, waiting periods, error rates, and resource utilization, annotating these metrics directly onto the flowchart.
Standard Flowchart Notation:
- Oval (Terminator): Denotes process entry points, terminal outcomes, or process boundaries.
- Rectangle (Process Step): Represents an individual operational task, activity, or execution step.
- Diamond (Decision Node): Marks a branch point where an evaluation occurs, leading to alternative downstream paths.
- Block Arrow (Transport): Highlights the physical movement or logical transfer of patients, specimens, supplies, or information.
- D-Shape (Delay): Depicts operational bottlenecks, waiting intervals, or queues in the workflow.

Standard flowcharting symbols and their operational functions

Cross-Functional ("Swim Lane") Process Maps:
- Arranges sequential steps into horizontal or vertical bands corresponding to distinct departmental roles or work units.
- Illustrates handoffs, accountability boundaries, and administrative touchpoints across multi-professional teams.
- Example Hospital Workflow Matrix:
  - Clerk: Collects and verifies patient insurance information.
  - Nurse: Records patient vital signs.
  - Porter: Transports the patient to examination or inpatient units; physically delivers pathology requests to diagnostic laboratories.
  - Doctor: Takes medical history, performs clinical examination, and formulates/writes the pathology request.

Service Blueprinting in Healthcare

Concepts of Service Blueprinting:
- A specialized branch of process mapping that designs and analyzes processes explicitly from the customer or patient perspective.
- Its primary goal is to isolate customer touchpoints, reveal potential points of service failure, and introduce poka-yoke (mistake-proofing) controls before failures affect patient satisfaction.
Structural Demarcations in Service Blueprints:
- Line of Interaction: The boundary separating direct customer actions from onstage employee touchpoints.
- Line of Visibility: The boundary separating visible employee activities (onstage) from hidden operational support functions (backstage).
Case Analysis: Outpatient Prescription Fulfillment Blueprint:
- Customer Actions (Above the Line of Interaction):
  - Patient hands the prescription paper/order to the pharmacy clerk.
  - Patient receives the completed medication package.
- Onstage Actions (Between Lines of Interaction and Visibility):
  - Clerk inputs prescription and patient data into the pharmacy information system.
  - Clerk hands the physical prescription order to the backstage dispensing area.
  - Clerk retrieves the verified medication from the backstage staging area.
  - Clerk hands the dispensed medication to the customer.
- Backstage Actions (Below the Line of Visibility):
  - Pharmacist reviews, compounds, and fills the prescription order.
  - Pharmacist performs clinical checks and hands the filled medication back to the clerk.

Service blueprinting diagram of a pharmacy prescription dispensing workflow

Root-Cause Analysis (RCA)

Methodological Framework:
- A structured, reactive problem-solving approach designed to isolate the fundamental, systemic breakdowns behind an adverse event rather than treating surface symptoms.
- Addresses three core questions:
  1. What happened?
  2. Why did it happen?
  3. What specific systemic interventions will prevent it from happening again?
The Five Whys Technique:
- An iterative interrogation tool that repeatedly asks "Why?" (typically five iterations as a rule of thumb) to trace a chain of cause-and-effect relationships back to the root cause.

Five Whys staircase descending from visible problem to root cause

Case Example: Medication Dispensing Error:
- Level 1: A patient received the wrong medication. Why?
- Level 2: The doctor prescribed the incorrect medication. Why?
- Level 3: Critical clinical information was missing from the patient’s medical chart. Why?
- Level 4: The patient’s most recent laboratory test results were not transcribed or integrated into the active chart. Why?
- Level 5: The laboratory technician dispatched the results, but the transmission was delayed in transit, leaving the chart un-updated at the time of clinical evaluation.
- Root Cause: Operational lag in diagnostic data transmission and charting, not isolated physician negligence.
- Systemic Corrective Action: Accelerate electronic diagnostic reporting or implement a mandatory chart flag indicating pending laboratory results.
Cause-and-Effect (Ishikawa / Fishbone) Diagrams:
- Overcomes the single-cause limitation of the Five Whys by capturing complex multi-factor causality.
- Structural Anatomy:
  - Head: The defined problem statement or undesirable effect.
  - Spine: Central horizontal axis directing causal pathways to the head.
  - Major Bones: Primary categories of potential causes.
  - Minor Bones: Sub-causes identified through deep analysis.
- Standard Operational Categories (The 4 Ms / Healthcare Adaptations):
  - Mother Nature (Environment)
  - Machines
  - Process
  - People
Diagnostic Case: Hospital Outpatient Waiting Times:
- Mother Nature (Environment):
  - Outdated inner-city architectural layout.
  - Physical corridor blockages obstructing patient throughput.
- Machines:
  - Elevator breakdowns resulting from deferred maintenance schedules.
  - Shortages of functional transport wheelchairs.
- Process:
  - Patient transport dispatch delays.
  - Ineffective clinic scheduling policies.
  - Absence of workflow-enabling clinical technologies.
  - Excessive overall process cycle times.
  - Administrative bureaucracy, including disarranged physical file systems and cumbersome HIPAA verification protocols.
- People:
  - Unscheduled or unexpected patient walk-ins driven by incorrect clinical referrals.
  - Patient scheduling errors and arrival off-schedule (e.g., missed original appointments).
  - Clinical staff unavailability driven by acute staff sickness or transit tardiness.

Comprehensive Cause-and-Effect fishbone diagram for hospital waiting time

Failure Mode and Effects Analysis (FMEA)

Principles of FMEA:
- A proactive, prospective risk-assessment technique that analyzes prospective failure points across each process step before an adverse event occurs.
- Systematically interrogates three dimensions of operational vulnerability:
  - Failure Mode: What could go wrong at this step?
  - Failure Causes: Why would the failure happen?
  - Failure Effects: What are the clinical or operational consequences if the failure occurs?
FMEA Rating Scales ( $1\text{--}10$ ):
- Likelihood of Occurrence ( $O$ ): Scored from $1$ (extremely improbable) to $10$ (almost certain to occur).
- Likelihood of Detection ( $D$ ): Scored inversely from $1$ (certain detection before reaching the patient) to $10$ (undetectable; failure will pass unnoticed).
- Severity ( $S$ ): Scored from $1$ (negligible impact) to $10$ (catastrophic outcome, such as severe harm or death).
Risk Priority Number (RPN) Formulation:
- The overall risk of any specific failure mode is quantified through multiplication: $\text{RPN} = O \times D \times S$
- The resulting scale ranges from a theoretical minimum of $1$ to a maximum of $1000$ .
- Total Process Risk is evaluated by summing all individual step RPNs: $\text{Total RPN} = \sum_{i=1}^{n} \text{RPN}_i$
- Mitigation strategies focus on high-RPN steps to lower occurrence frequency ( $O$ ) or enhance proactive detection ( $D$ ).

FMEA structured engineering worksheet format

Theory of Constraints (TOC)

Core Concepts:
- Developed by Eliyahu M. Goldratt and Jeff Cox in The Goal (1986).
- Asserts that any complex operational system is bounded by at least one limiting constraint (bottleneck) preventing it from reaching higher performance goals.
- System throughput can only increase by focusing improvements on this primary constraint; optimizing non-bottleneck processes produces excess work-in-progress inventory without increasing overall output.
- Physical Constraints: Tangible capacity limits (e.g., MRI machine operating limits, operating room physical capacity, inpatient bed counts).
- Nonphysical Constraints: Intangible operating barriers (e.g., hospital discharge policies, rigid physician scheduling protocols, administrative sign-off procedures).
The Four Steps of Continuous TOC Improvement:
1. Identify the Constraint: Pinpoint the exact resource, task, or policy restricting total system throughput.
2. Exploit the Constraint: Maximize the efficiency and continuous utilization of the bottleneck resource using current assets (e.g., eliminating idle downtime during shift handoffs, removing non-essential tasks from bottleneck resources).
3. Elevate the Constraint: Invest organizational resources or capital to expand the capacity of the bottleneck (e.g., hiring additional personnel, purchasing additional diagnostic equipment, adding physical space).
4. Repeat the Process (Prevent Inertia): Once the original constraint is elevated, the bottleneck shifts elsewhere. The cycle repeats to address the newly formed constraint.

Decision Tree Analysis for Healthcare Operations

Decision Analysis Mechanics:
- A quantitative methodology that models decision sequences, chance variables, and financial/clinical payoffs under uncertainty.
- Events are ordered chronologically from left to right.
- Standard Decision Tree Nodes:
  - Decision or Choice Event (Square): Indicates an operational fork controlled directly by the decision-maker.
  - Chance Event (Circle): Indicates an uncertain probabilistic outcome outside the manager's direct control. Probabilities across mutually exclusive branches must sum to $1.0$ ( $100\%$
  - Outcome Node (Triangle): Denotes terminal operational payoffs, net financial consequences, or clinical outcomes.
- Tree Rollback (Backward Induction): Evaluation proceeds from right to left, computing the expected monetary value (EMV) or expected cost for each chance node and choosing the optimal alternative at each decision node.

HMO influenza vaccination program decision tree

Quantitative Case Study: HMO Influenza Vaccination Strategy:
- Problem Context: A Health Maintenance Organization (HMO) must decide whether to implement a preventive flu vaccination program. Financial figures represent costs expressed in millions of dollars ( $\text{M}$ ). Probability of an influenza outbreak is $70\%$ ( $0.70$ ); probability of no outbreak is $30\%$ ( $0.30$ ).
- Initial Choices at Decision Node 1:
  - Vaccination Program #1: Fixed implementation cost of "\-"\$7\text{ million}.
  - No Program: Zero initial capital cost ( $0$ ).
- Right-to-Left Rollback Calculations:
  - Evaluation of Chance Node 6 (Outbreak, No Program):
    - Branch C (Probability $0.60$ ): Payoff of $-\$12\text{ million}$ .
    - Branch D (Probability $0.40$ ): Payoff of $-\$8\text{ million}$ . $\text{Expected Cost}_{\text{Node 6}} = (0.60 \times -12) + (0.40 \times -8) = -7.2 + (-3.2) = -\$10.4\text{ million}$
  - Evaluation of Chance Node 5 (Outbreak, Reactive Vaccination Program #2):
    - Fixed program cost: $-\$7\text{ million}$ .
    - Branch A (Probability $0.60$ ): Direct cost of $-\$6\text{ million}$ .
    - Branch B (Probability $0.40$ ): Direct cost of $-\$4\text{ million}$ . $\text{Expected Variable Cost} = (0.60 \times -6) + (0.40 \times -4) = -3.6 + (-1.6) = -\$5.2\text{ million}$ $\text{Total Expected Cost}_{\text{Node 5}} = -7 + (-5.2) = -\$12.2\text{ million}$
  - Evaluation of Decision Node 4:
    - Choice 1 (Reactive Program #2): Expected cost of $-\$12.2\text{ million}$ .
    - Choice 2 (No Program): Expected cost of $-\$10.4\text{ million}$ .
    - Decision: Choose "No Program" because an expected cost of "\-"\$10.4\text{ million} is lower than "\-"\$12.2\text{ million}.
  - Evaluation of Chance Node 3 (Upfront "No Program" Branch):
    - Flu Outbreak occurs (Probability $0.70$ ): Feeds into Node 4 outcome ( $-\$10.4\text{ million}$ ).
    - No Flu Outbreak occurs (Probability $0.30$ ): Incurs zero cost ( $0$ ). $\text{Expected Cost}_{\text{Node 3}} = (0.70 \times -10.4) + (0.30 \times 0) = -\$7.28\text{ million}$
  - Evaluation of Chance Node 2 (Upfront "Vaccination Program #1" Branch):
    - Fixed initial investment: $-\$7\text{ million}$ .
    - With a fully vaccinated population, outbreak downstream cost equals $0$ , and no outbreak cost equals $0$ . $\text{Total Expected Cost}_{\text{Node 2}} = -7 + 0 = -\$7.00\text{ million}$
  - Evaluation of Root Decision Node 1:
    - Option A (Vaccination Program #1): Expected cost of $-\$7.00\text{ million}$ .
    - Option B (No Program): Expected cost of $-\$7.28\text{ million}$ .
    - Conclusion: Implement Vaccination Program #1 upfront, reducing expected costs by "\+"\$0.28\text{ million} ( $\$280{,}000$ ).

Force Field Analysis and Change Implementation

Conceptual Model:
- Identifies and weights the balance of power between opposing forces surrounding an organizational change initiative:
  - Driving Forces: Pressures, incentives, and rationales favoring change.
  - Restraining Forces: Cultural habits, obstacles, risks, and employee anxieties resisting change.
- Strategic Utility:
  - Helps determine the initial feasibility of a change proposal before committing capital.
  - Provides an actionable framework to design targeted interventions that reduce restraining forces rather than simply pushing on driving forces (which often increases counter-resistance).
- Decision Metric: If the sum of Restraining Force scores exceeds the sum of Driving Force scores, the change will face major friction or fail entirely.
Case Analysis: Transition to Bedside Shift Handover:
- Driving Forces (Total Score: $19$ ):
  - Complaints from patients and attending physicians are increasing (Weight: $5$ ).
  - Critical incidents during shift transitions are on the rise (Weight: $4$ ).
  - Staff are well-trained and knowledgeable in change management principles (Weight: $4$ ).
  - Discharges against medical advice (AMA) are increasing (Weight: $3$ ).
  - Current nursing care model is predominantly biomedical rather than patient-centered (Weight: $3$ ).
- Restraining Forces (Total Score: $21$ ):
  - Operational issues associated with late shift arrivals (Weight: $5$ ).
  - Risk of disclosing confidential patient medical data in multi-bed units under privacy guidelines (Weight: $5$ ).
  - Entrenched department traditions, ritualism, and inertia (Weight: $4$ ).
  - Staff fear that bedside handovers will create additional uncompensated work (Weight: $4$ ).
  - Nursing anxieties regarding increased personal accountability at the bedside (Weight: $3$ ).
- Implementation Diagnostic: The restraining total ( $21$ ) exceeds the driving total ( $19$ ). Pushing the initiative without mitigation will likely fail. Implementation success requires targeted actions to soften the top restraining forces, such as structuring standardized arrival handoff protocols and establishing clear patient privacy guidelines for shared patient rooms.

Force field analysis evaluating bedside shift handover

Questions, Discussion Prompts, and Applied Exercises

Discussion Prompt 1: Service Blueprinting and Visibility Thresholds:
- Prompt Focus: Reflect on an encounter as an inpatient, outpatient, or retail pharmacy customer.
- Analysis Questions:
  - Where was the distinct line of visibility positioned during the encounter?
  - At which exact operational touchpoint could the service delivery fail most easily?
  - If an unmonitored backstage step broke down, which failure symptom would the customer detect first?
  - What administrative poka-yoke (mistake-proofing) control should be added to prevent this breakdown?
Discussion Prompt 2: Five Whys and Multi-Causal Diagnosis:
- Prompt Focus: Select a recurring operational problem within a healthcare institution (e.g., long clinic wait times, unpunctual operating room starts, missed appointments, or recurring medical billing errors).
- Analysis Questions:
  - Apply the Five Whys technique iteratively to the scenario.
  - At which specific "Why?" iteration does the analysis shift away from individual human blame toward broader system design flaws?
  - Map the identified causes onto an Ishikawa fishbone diagram.
  - Which causal domain (Environment, Process, Machines, or People) accounts for the largest proportion of failure points?
Discussion Prompt 3: Force Field Analysis in Operational Settings:
- Prompt Focus: Identify a proposed organizational or workflow change within an academic or clinical work environment.
- Analysis Questions:
  - What are the primary driving and restraining forces acting on the proposal?
  - Assign a subjective intensity score ( $1$ to $5$ ) to each identified force.
  - If the restraining forces outweigh the driving forces, what single operational intervention would most effectively weaken the highest-scoring restraining force?
Applied Class Exercise: Multidisciplinary Process Improvement:
- Step 1 (Group Formulation): Form multidisciplinary teams.
- Step 2 (Problem Selection): Select an urgent operational healthcare challenge (e.g., emergency department boarding, medication dispensing delays, surgical turnover intervals).
- Step 3 (Process Flowcharting): Construct an exhaustive flowchart detailing the current state of the process, using standard symbols (terminators, activities, decisions, transportation, delays).
- Step 4 (Fishbone Diagramming): Build an Ishikawa cause-and-effect diagram exploring four core causal categories (Environment, Process, Machines, and People), identifying secondary and tertiary causes.
- Step 5 (Synthesis and Reporting): Present the flowchart and fishbone diagram, showing how the combination of diagnostic tools isolates systemic root causes more effectively than using an isolated method.