[Text on screen: QI Hub Process Map Part 1 The Ohio State University College of Medicine The Ohio State University Wexner Medical Center] [Box with text: Processes Start Finish] [Straight arrow connects "start" to "finish" and another arrow connects whole box to a hospital] [Animation turns straight arrow connecting "start" to "finish" into a squiggly arrow] Speaker: Every healthcare system runs on processes. Some are clear and efficient, others are inconsistent or unclear. [Red spiky ball appears along arrow with text: Problem issue lies in how process is designed] When problems arise, it can be tempting to focus on individual actions and look for blame, [The words "start" and "finish" disappear and a red circle appears around the squiggly arrow] but more often the issue lies in how the process is designed. [Text on screen: Process Map] That's where process maps can help. [Process map is shown like a flow chart with various boxes labeled "Start", "Action step", "Decision", "Delay", "End", and they are all connected with arrows] Process maps are visual tools that help teams understand how work actually flows, from start to finish. [Red circles appear around some of the boxes] They show the steps, decisions, handoffs and delays that shape outcomes, and they create a shared picture of the system that everyone can see and improve together. [Text on screen: Process Map Several Ways to map a process, depending on complexity.] There are several ways to map a process, depending on how much complexity you want to capture. [Text on screen: Process Map Step-by-step map] [Arrows connect the text: Step 1 Step 2 Step 3 Step 4] The most basic or high‑level map is a simple step‑by‑step map. ["Step 1" turns into "Patient arrives" "Step 2" turns into "Checks in" "Step 3" turns into "Called back" "Step 4" turns into "Seen by provider"] It just shows the main actions in order. No decision points. No branches. This kind of map is useful for getting started or outlining straightforward workflows. [Flow chart from before appears with red circle around box labeled "Decision." Arrows leave from the box labeled "yes" and "no"] A more complex version includes decision points, places where the process branches based on what's happening. [Text "Decision" turns into "Example: Did the patient arrive on time?"] Adding these decision diamonds helps capture variation and complexity in the process. [Columns appear, splitting up the flow chart with all columns labeled "Job function"] And finally, you can build a swim lane map, which shows who is responsible for each step. [Each column labeled "Job function" turns into "Front desk", "Nurse", "Provider", and "Lab"] This format divides the process by role or function, like front desk, nurse, provider, lab, and helps clarify handoffs, overlaps, and gaps between team members. [Flow chart appears flipped on it's side with rows instead of columns] You can make it horizontal or vertical based on whatever works best for visualizing the process. [Three Process Maps are shown] Each of these formats has value. [Map with 4 steps connected by arrows in a line is highlighted] Sometimes a basic map is enough to spot issues. [Complex flow charts are highlighted] Other times, you'll need more detail to truly understand where things are breaking down. The key is to choose the level of complexity that fits the purpose of your improvement effort. [Text on screen: In the next set of videos: How to use and build process maps in more depth] In the next set of videos, we will discuss how to use and build process maps in more depth. You don't need to be a designer to create a useful map. [Text on screen: See the system clearly Listen to people doing the work Stay curious] What you do need is a commitment to see the system clearly, listen to the people doing the work, and stay curious about what might be improved. [Text on screen: QI Hub Thank you! Scan the QR code for references and resources The Ohio State University College of Medicine The Ohio State University Wexner Medical Center] [QR code links to: https://go.osu.edu/qihub]