A process flow is a visual representation of the steps, decisions, and sequence involved in completing a task or workflow from start to finish. It uses shapes, arrows, and labels to show how work moves through a system, making it easier to understand, communicate, and improve how things get done. You’ll encounter process flows in business operations, software development, healthcare, manufacturing, and nearly any field where work follows a repeatable sequence.
How a Process Flow Works
At its core, a process flow breaks a complex workflow into individual steps and arranges them in order. Each step connects to the next with arrows that show direction, so anyone reading the diagram can follow the path from beginning to end. The value is in making the invisible visible: when steps only exist in people’s heads or scattered across documents, it’s hard to spot inefficiencies or explain the workflow to someone new. A process flow puts everything on one page.
A high-level process flow might show just five to seven core activities, giving you what’s sometimes called a “35,000-foot view” of the work. A detailed version zooms in to capture every substep, handoff, and decision point. Which level you need depends on your goal. If you’re explaining a workflow to leadership, keep it high-level. If you’re troubleshooting delays or training new team members, go detailed.
Standard Symbols and What They Mean
Process flows use a set of standardized shapes, originally defined by the International Organization for Standardization (ISO 5807). You don’t need to memorize them all, but knowing a handful will let you read or create any basic process flow.
- Rectangle (process step): Represents a single action or task. The step is written inside the box, and typically only one arrow leads out to the next step.
- Diamond (decision): Represents a question or branching point. The question is written inside the diamond, and multiple arrows lead out, each labeled with a possible answer (often “yes” and “no”). The path the process takes depends on the answer.
- Oval or rounded rectangle (start/end): Marks where the process begins and where it finishes.
- Rectangle with a wavy bottom (document): Indicates that a document is produced or required at that step.
- Arrows: Connect the shapes and show the direction of flow.
These symbols are consistent across industries, so a process flow drawn by an engineer in Tokyo follows the same visual language as one drawn by a project manager in Chicago.
Types of Process Flows
Not all process flows look the same. The format you choose depends on what you’re trying to capture.
A simple flowchart is the most common type: a linear or branching diagram that maps steps and decisions for a single process. It works well for straightforward workflows like onboarding a new employee or handling a customer return.
A swimlane diagram adds horizontal or vertical lanes to show who is responsible for each step. Each lane represents a person, team, or department. This format is especially useful when a process crosses organizational boundaries, because it makes handoffs between groups explicit rather than assumed.
A SIPOC diagram takes a broader view. It maps five elements: Suppliers (who provides the inputs), Inputs (the materials or information needed), Process (the core steps), Outputs (what the process produces), and Customers (who receives the output). SIPOC diagrams are often the starting point before building a more detailed flowchart, because they define the boundaries of the process and clarify who’s involved on either end.
For more complex modeling, organizations sometimes use Business Process Model and Notation (BPMN), a formal standard designed for detailed workflows. BPMN introduces gateway symbols that handle sophisticated branching. An exclusive gateway means only one path can be taken (like a standard yes/no decision). A parallel gateway means multiple paths run at the same time, and all of them must complete before the process moves forward. An inclusive gateway means one or more paths can be taken depending on conditions. These distinctions matter when you’re modeling processes where multiple things happen simultaneously, like parallel approvals from different departments.
Why Process Flows Matter in Practice
The most immediate benefit of a process flow is clarity. When you map out each step, you can see exactly where work slows down, where steps are redundant, and where handoffs create confusion. Tracking metrics like wait times, backlog volume, and throughput at each stage helps pinpoint bottlenecks that would otherwise stay hidden. A marketing team, for instance, might discover through a flowchart that the campaign approval process is creating significant delays, even though the creative work itself finishes on time.
Process flows also serve as communication tools. A new hire can study a flowchart and understand in minutes what might take hours to explain verbally. Teams working across departments can use a shared process flow to agree on who does what and in what order, reducing the “I thought you were handling that” moments that derail projects.
In quality improvement methodologies like Lean and Six Sigma, process flows are foundational. You can’t improve a process you haven’t defined. The typical progression is to first map the current state (how things actually work today), then model the ideal state (how they should work), and finally identify the gaps between the two. This three-phase approach, mapping, modeling, and improving, applies whether you’re streamlining a factory line or redesigning a patient intake procedure at a hospital.
Process Flows in Healthcare and Laboratories
Healthcare is one of the fields where process flows have the most direct impact. Clinical pathways, which standardize how patients move through treatment, rely on process flow diagrams to map every decision point from initial assessment to discharge. These pathways support consistent care and help clinical teams make decisions at each stage rather than improvising.
Planning decisions in healthcare operate at three levels, and process flows can apply to all of them. Strategic planning covers long-term structural decisions like where to build a new facility or how many staff to hire. Tactical planning handles mid-term organization like shift scheduling. Operational planning manages day-to-day tasks like assigning patients to appointments. A process flow at the operational level might map how a patient moves through an emergency department, while one at the strategic level might map the decision process for expanding a service line.
Clinical laboratories offer another clear example. Lab workflow is typically divided into three phases: pre-analytical (ordering tests, collecting specimens, transporting and labeling samples), analytical (running the tests), and post-analytical (interpreting and reporting results). The pre-analytical phase alone splits into work that happens outside the lab (ordering, specimen collection, transport) and inside the lab (receiving samples, labeling, centrifuging, distributing to analyzers). Mapping this entire sequence as a process flow lets lab managers see where delays accumulate and where errors are most likely to occur.
How to Build a Process Flow
Start by defining the boundaries. What triggers the process to begin, and what marks it as complete? Without clear start and end points, the diagram can sprawl endlessly into adjacent workflows.
Next, list every step in the order it happens. Walk through the process as it actually works, not as you wish it worked. Talk to the people who do the work daily, because the official procedure and the real procedure are often different. For each step, ask: what happens next? Does a decision need to be made here? If yes, that becomes a diamond on your diagram.
Once you have the steps, arrange them using standard symbols and connect them with arrows. Keep the flow moving in one primary direction, typically left to right or top to bottom. Label every decision branch clearly. If the diagram gets too complex to fit on one page, consider breaking it into sub-processes, where a single step on the main diagram links to a separate, more detailed flowchart.
Review the finished diagram with the people who actually perform the process. They’ll catch missing steps, incorrect sequences, and assumptions that don’t match reality. A process flow is only useful if it reflects what actually happens.