Lesson 1 Participant Lesson Plan

OSD FOUNDATIONS MODULE I / LESSON 1 OSD Foundations | Fictional Training Scenario — For Educational Use. 1 THE OVERSIGHT SENTINEL DOCTRINE™ FOUNDATIONS Module I — Seeing the System Lesson 1 — The Problem Behind the Problem Participant Lesson Plan — Draft v1.0 Estimated lesson time: 5–6 minutes Program format: Self-directed webinar Module: I — Seeing the System Lesson Purpose Oversight work frequently begins with an event: a missed target, an unusual transaction, a complaint, a control failure, a recurring delay, or an unexpected outcome. The event matters. But the event may not be the whole problem. This lesson introduces a foundational shift in the Oversight Sentinel Doctrine™: moving beyond the immediate event to examine the organizational conditions that may be shaping recurring outcomes. The objective is not to abandon traditional oversight disciplines or their evidentiary requirements. It is to develop an additional way of seeing the system in which those facts exist. Learning Objectives By the end of this lesson, you should be able to: • distinguish an individual event from a broader pattern of organizational behavior; • recognize when repeated outcomes warrant examination beyond their immediate causes; • use the progression Event → Pattern → Structure → System Behavior to organize an initial systems-oriented inquiry; and • identify questions that can reveal conditions making an outcome increasingly likely. The lesson does not ask you to diagnose system drift or reach conclusions about organizational causes. Those judgments require additional evidence and inquiry.

OSD FOUNDATIONS MODULE I / LESSON 1 OSD Foundations | Fictional Training Scenario — For Educational Use. 2 The Case: OPBA and BDMI Throughout OSD Foundations, you will work with a fictional federal organization: the U.S. Office of Public Benefits Administration (OPBA). OPBA is an independent federal agency administering nationwide benefits and assistance programs. It employs approximately 8,200 federal employees, operates headquarters and 10 regional offices, administers approximately $38 billion in annual program expenditures, and processes more than 11 million beneficiary transactions. The agency is implementing a major modernization effort—the Benefits Delivery Modernization Initiative (BDMI). At first glance, BDMI appears to be producing strong results: Performance indicator Reported result Average claims processing time ↓ 18% Reported pending claims ↓ 23% Administrative cost per claim ↓ 11% IT contractor SLA performance 96% Prior OIG corrective actions closed 91% Beneficiary complaints ↑ 14% Agency leadership summarizes the situation simply: “BDMI is working.” The dashboard provides evidence of performance. It also creates a question. What to Watch For As you move through the lesson, resist the temptation to decide immediately whether BDMI is succeeding or failing. Instead, pay attention to the relationship between the indicators. Ask yourself: What does the dashboard tell us? Then ask the more difficult question: What doesn't it tell us? A contradiction between indicators does not establish a finding. It may, however, provide a reason to look more closely.

OSD FOUNDATIONS MODULE I / LESSON 1 OSD Foundations | Fictional Training Scenario — For Educational Use. 3 Seeing Beyond the Event OSD introduces a simple progression for organizing that inquiry: EVENT → PATTERN → STRUCTURE → SYSTEM BEHAVIOR EVENT An event is something observable that happened. A beneficiary experiences an unusual delay. A transaction fails. A complaint is filed. A deadline is missed. An event gives oversight a place to begin. It does not necessarily explain why the outcome occurred. PATTERN When similar events recur, the question changes. Instead of asking only: “What happened here?” we can begin asking: “Where else is this happening?” Patterns help distinguish isolated occurrences from outcomes that may reflect something broader. STRUCTURE Once a meaningful pattern appears, attention can move toward the conditions surrounding it. Those conditions might include workflows, incentives, information pathways, performance measures, technology, authorities, staffing arrangements, escalation processes, or other organizational structures. The question becomes: “What conditions could be making this pattern more likely?” SYSTEM BEHAVIOR When structures interact repeatedly, they can influence how the organization behaves over time. The resulting behavior may not have been intentionally designed. It may emerge from ordinary decisions, adaptations, constraints, and incentives operating together. The systems-oriented question therefore becomes: “What is the organization repeatedly producing—and what within the system may be helping produce it?”

OSD FOUNDATIONS MODULE I / LESSON 1 OSD Foundations | Fictional Training Scenario — For Educational Use. 4 Apply the Lens Return to the BDMI dashboard. You know that processing time has decreased. Reported pending claims have decreased. Administrative cost per claim has decreased. Contractor service levels are high. Most prior corrective actions are reported closed. You also know that beneficiary complaints have increased by 14 percent. At this point, what can you responsibly conclude? Not much about cause. The complaint increase is a signal worthy of attention, not proof that BDMI is failing. The appropriate next move is inquiry. Consider the progression: EVENT A beneficiary reports a problem. PATTERN Complaints are increasing. STRUCTURE What workflows, measures, technologies, incentives, information pathways, or operating conditions should oversight examine? SYSTEM BEHAVIOR What might the organization be repeatedly producing that is not fully visible in its headline performance measures? Notice what has happened. We have not made a finding. We have improved the question.

OSD FOUNDATIONS MODULE I / LESSON 1 OSD Foundations | Fictional Training Scenario — For Educational Use. 5 Your Observation Before continuing, capture one observation. Think about an oversight matter you have encountered—or use the OPBA case if you prefer. Complete this progression: Event: What happened? Pattern: What appears to be recurring? Structure: What organizational condition would you want to examine? System Behavior: If that condition persists, what recurring organizational behavior might it help produce? Do not try to prove the relationship yet. The purpose is to identify where disciplined inquiry should look next.

OSD FOUNDATIONS MODULE I / LESSON 1 OSD Foundations | Fictional Training Scenario — For Educational Use. 6 OSD Boundary Systems thinking does not replace audit, inspection and evaluation, investigation, legal analysis, data analytics, or other oversight disciplines. Those disciplines establish facts according to their applicable standards and methods. OSD helps connect and interpret what those disciplines reveal. Disciplines establish facts. OSD helps the OIG see what those facts mean together. A systems-oriented question is therefore not a finding. It is a way of directing attention toward relationships that may deserve further examination. Principal Takeaway The first discipline of system stewardship is learning to distinguish what happened from what may be producing what happened. That distinction changes the questions oversight asks. The finding may identify what happened. Systems thinking asks what made the outcome increasingly likely. Before Lesson 2 Carry one question forward: What happens when people inside a system begin adapting to its constraints—and those adaptations gradually become normal? That is where Lesson 2 — How Systems Drift begins.

OSD FOUNDATIONS INQUIRY GUIDE Questions for Inquiry LESSON 1: THE PROBLEM BEHIND THE PROBLEM Moving from visible events to patterns, structures, and recurring system behavior. SIGNAL What happened, and which observable fact makes the matter worthy of closer attention? RECURRENCE Where else, how often, and under what conditions does the same or a related outcome appear? ARCHITECTURE Which workflows, measures, incentives, technologies, authorities, or information paths could make the pattern more likely? SYSTEM BEHAVIOR What does the organization repeatedly produce, regardless of stated intent or isolated explanations? EVIDENCE What records, comparisons, interviews, or data could support, refine, or disprove the emerging pattern? BOUNDARY What remains unknown, and which conclusions would exceed the evidence now available? Use these questions to direct attention and develop testable hypotheses. They do not establish findings, intent, causation, or responsibility. OSD Foundations | Questions for Inquiry | Fictional Training Scenario - For Educational Use 7