00 — CLASS INTRODUCTION Module One begins with the first move in Sentinel practice: seeing beyond an isolated event without outrunning the evidence. As The Oversight Sentinel Doctrine, Volume One explains, the oversight environment has changed. Systems move faster than traditional oversight cycles were designed to accommodate. Data volumes strain static review models. Digital architectures can replicate error at scale. Political and operational pressure can compress decision timelines and distort signal clarity. The burning imperative is to change posture: to move upstream from isolated events toward trajectory, and to synthesize insight across audits, inspections, investigations, analytics, and institutional memory. Lesson One turns that imperative into disciplined practice. You will distinguish a visible event from a recurring pattern, identify structures that may shape the pattern, and frame a bounded question about the behavior the system may be producing. You will work with the fictional Office of Public Benefits Administration and its Benefits Delivery Modernization Initiative throughout the course. The case gives you one continuous system in which to test your judgment. Remember the boundary. A systems question directs inquiry. It does not independently establish cause, intent, misconduct, fraud, or responsibility. Select Begin lesson when you are ready. SECTION 01 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. 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. SECTION 02 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: Refer to the table on page 2 of your lesson plan. Keep that page open as we examine the dashboard and the questions under What to Watch For. Agency leadership summarizes the situation simply: “BDMI is working.” The dashboard provides evidence of performance. It also creates a question. What does the dashboard tell us? 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. SECTION 03 Turn to Seeing Beyond the Event on page 3 of your lesson plan. Follow the definitions there as the illustration moves through the four stages. OSD introduces a simple progression for organizing that inquiry: Event, Pattern, Structure, and System Behavior. An event is something observable that happened. An event gives oversight a place to begin. It does not necessarily explain why the outcome occurred. 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. Once a meaningful pattern appears, attention can move toward the conditions surrounding it. “What conditions could be making this pattern more likely?” 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. “What is the organization repeatedly producing—and what within the system may be helping produce it?” SECTION 04 Return to the BDMI dashboard. 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. Refer to Apply the Lens on page 4 of your lesson plan. Follow the questions there alongside this illustration. What workflows, measures, technologies, incentives, information pathways, or operating conditions should oversight examine? What might the organization be repeatedly producing that is not fully visible in its headline performance measures? We have not made a finding. We have improved the question. SECTION 05 Use Your Observation on page 5 of your lesson plan for the next exercise. The illustration will remain on screen as you work through the prompts. 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. SECTION 06 Turn to page 6 of your lesson plan. Follow OSD Boundary, then Principal Takeaway and Before Lesson 2, as we close the lesson. 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. 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. 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.