Workflow Diagram
What is a Workflow Diagram?
A workflow diagram maps how a piece of work moves from its trigger to its outcome, showing each task, decision, role and system involved using standard symbols. Diagrams range from whiteboard sketches to formal BPMN models.
Updated November 2026 · 3 min read
A workflow diagram is a visual map of the steps, decisions, people and systems involved in completing a piece of work, from the trigger that starts it to the outcome that ends it. It shows who does what, in what order, and what happens at each decision point, so a team can understand, discuss and improve a process without relying on memory or long written procedures.
Workflow diagrams descend from the flow process charts that Frank and Lillian Gilbreth presented to the American Society of Mechanical Engineers in 1921. Today they range from quick whiteboard sketches to formal models in Business Process Model and Notation (BPMN), a standard maintained by the Object Management Group whose 2.0 version was released in 2011.
Workflow diagram symbols
| Symbol | Meaning |
|---|---|
| Oval or rounded rectangle | Start or end of the workflow |
| Rectangle | A task or activity |
| Diamond | A decision with two or more outcomes |
| Arrow | Direction of flow from one step to the next |
| Parallelogram | Input or output, such as a form or report |
| Document shape | A document produced or used in the step |
BPMN adds more precise elements, such as events, gateways for parallel or exclusive paths, and message flows between organizations. For most internal teams, the basic flowchart shapes are enough.
Types of workflow diagrams
- Basic flowchart. A single sequence of steps and decisions. Good for simple or linear processes.
- Swimlane diagram. Splits the diagram into horizontal or vertical lanes, one per role, team or system. It makes handoffs visible, which is where delays and errors often occur.
- BPMN diagram. A formal notation that can be read by people and, in many tools, executed by workflow engines.
- Data flow diagram. Focuses on how information moves between processes and data stores rather than on who performs the steps.
- Value stream map. Adds timing data such as wait time and processing time to show where work stalls. See value stream mapping.
How to create a workflow diagram
- Set the boundaries. Name the trigger that starts the workflow and the outcome that ends it.
- Talk to the people who do the work. Documented procedures often differ from what actually happens. Walk through real recent cases.
- List the steps and owners. Write each step as a verb and object, such as "Review request," and note who performs it.
- Add decisions and exceptions. Capture what happens when a request is rejected, incomplete or urgent.
- Draw the current state first. Resist fixing the process while mapping it, or the diagram will describe a process nobody follows.
- Review and mark problems. Ask participants to flag delays, rework loops and unclear handoffs, then draft the improved version.
A workflow diagram in practice
Consider a hypothetical SaaS company where customer feature requests reach the product team through support, sales and customer success. A swimlane diagram with four lanes (customer, support, product operations and product manager) shows each request being logged in two places, triaged twice and sent back to support for more detail in many cases.
The team counts 11 steps and 5 handoffs between the customer submitting a request and a product manager seeing it. The redesigned workflow uses one intake form with required fields, so requests arrive complete, and product operations triages them once. The new diagram has 7 steps and 3 handoffs. Over the following quarter the team tracks the median time from submission to triage to see whether the shorter flow actually speeds things up.
Common pitfalls
- Too much detail. A diagram with 80 boxes is rarely read. Split complex processes into a high-level view and linked sub-processes.
- Mapping the ideal instead of the real. Diagrams drawn from policy documents miss workarounds that explain why the process is slow.
- Leaving out exceptions. The happy path is usually the least problematic part of a workflow.
- Letting it go stale. A diagram that no longer matches the process misleads new staff. Assign an owner and review it when the process changes.
Workflow diagrams are closely related to the process flow diagram and support process documentation. Once a workflow is mapped and simplified, it is often the starting point for workflow automation and broader process improvement.
Frequently asked questions
What do the shapes in a workflow diagram mean?
In a basic workflow diagram, an oval or rounded rectangle marks the start or end, a rectangle is a task, a diamond is a decision with two or more outcomes, and arrows show the direction of flow. A parallelogram represents an input or output, and a document shape marks a document produced or used. BPMN adds more precise events, gateways and message flows.
What is a swimlane workflow diagram?
A swimlane diagram splits a workflow diagram into horizontal or vertical lanes, one per role, team or system. Placing each step in the lane of whoever performs it makes handoffs visible, and handoffs are where delays and errors often occur. Swimlanes suit processes that cross several teams, such as customer feature requests moving from support to product.
Should a workflow diagram show the current process or the ideal one?
Draw the current state first, based on talking to the people who do the work and walking through recent real cases. Documented procedures often differ from reality, and a diagram drawn from policy misses the workarounds that explain why a process is slow. Once the real workflow is mapped and its delays and rework loops are marked, draft the improved version.
Related terms
Process Flow Diagram (PFD)
A flowchart showing the steps, decisions and order of a process.
Process Documentation
Recording how work gets done so others can repeat and improve it.
Process Improvement
Analyzing and changing how work is done to make it faster and better.
Value Engineering
Delivering the same functions at lower cost without cutting quality.