Shapes and arrows show the order of work and conditional branches.
Difference from similar diagrams
Swimlanes place steps in bands by owner. A plain flowchart does not identify ownership.
When to use it
Share the sequence from request to archive.
Limits and cautions
This example has no branches. For a decision, specify its condition and each destination.
Creation instruction
Create a diagram of this example.
Flowchart
Request → Review → Approve → Archive. Request=Requester; Review=Reviewer; Approve=Approver; Archive=Requester
Share the sequence from request to archive.
This example has no branches. For a decision, specify its condition and each destination.
The last step returns to the first, expressing repetition.
Difference from similar diagrams
A flowchart can end; this cycle adds a connection into the next round.
When to use it
Explain a recurring request, review, approval and archiving process.
Limits and cautions
A circular arrangement alone is not a cycle. Show the return arrow and the condition for repeating.
Creation instruction
Create a diagram of this example.
Cycle diagram
Request → Review → Approve → Archive. Request=Requester; Review=Reviewer; Approve=Approver; Archive=Requester. Archive → Request
Explain a recurring request, review, approval and archiving process.
A circular arrangement alone is not a cycle. Show the return arrow and the condition for repeating.
The team contains requester, reviewer and approver. The network adds contact between requester and reviewer.
What it represents
Branches express parent–child, higher–lower or containment relationships.
Difference from similar diagrams
A relationship diagram also allows peer connections. Hierarchy branches express the stated parent–child relation.
When to use it
Organize team membership or information categories.
Limits and cautions
State whether branches mean reporting, classification or containment. Do not confuse them with process order.
Creation instruction
Create a diagram of this example.
Hierarchy diagram
The team contains requester, reviewer and approver. The network adds contact between requester and reviewer.
Organize team membership or information categories.
State whether branches mean reporting, classification or containment. Do not confuse them with process order.
Steps sit in bands by owner, showing sequence and handoffs.
Difference from similar diagrams
It adds ownership to a flowchart. Connections crossing bands show handoffs.
When to use it
Review responsibilities and handoffs between requester, reviewer and approver.
Limits and cautions
Specify each step owner and arrow meaning. Band width does not represent duration.
Creation instruction
Create a diagram of this example.
Swimlane diagram / cross-functional flowchart
Request → Review → Approve → Archive. Request=Requester; Review=Reviewer; Approve=Approver; Archive=Requester
Review responsibilities and handoffs between requester, reviewer and approver.
Specify each step owner and arrow meaning. Band width does not represent duration.
Overlapping sets show shared members and members exclusive to either set.
Difference from similar diagrams
A network edge means a connection; Venn overlap means membership in both sets.
When to use it
Separate shared and exclusive tasks for two work groups.
Limits and cautions
State membership criteria. Circle and overlap areas in this example do not encode counts.
Creation instruction
Create a diagram of this example.
Venn diagram
1=Request, 2=Review, 3=Approve, 4=Archive. Operations={1,2,3}; Review group={2,3,4}. Ratings: 1=(low effort, high importance), 2=(high, high), 3=(low, low), 4=(high, low).
Separate shared and exclusive tasks for two work groups.
State membership criteria. Circle and overlap areas in this example do not encode counts.
The team contains requester, reviewer and approver. The network adds contact between requester and reviewer.
What it represents
Nodes and edges show connections between elements.
Difference from similar diagrams
This example adds a peer contact to a hierarchy; connections need not be parent–child.
When to use it
Show who communicates with whom in a team.
Limits and cautions
State whether edges mean contact, dependency or causation. These edges mean contact, not causation.
Creation instruction
Create a diagram of this example.
Relationship diagram / network diagram
The team contains requester, reviewer and approver. The network adds contact between requester and reviewer.
Show who communicates with whom in a team.
State whether edges mean contact, dependency or causation. These edges mean contact, not causation.
Two evaluation axes position items for comparing combinations.
Difference from similar diagrams
Venn diagrams describe set membership; a two-axis matrix describes two evaluation criteria.
When to use it
Compare four tasks by importance and effort to discuss work order.
Limits and cautions
Specify axes, criteria and boundaries. Position alone does not prove impact or priority.
Creation instruction
Create a diagram of this example.
Two-axis matrix / quadrant diagram
1=Request, 2=Review, 3=Approve, 4=Archive. Operations={1,2,3}; Review group={2,3,4}. Ratings: 1=(low effort, high importance), 2=(high, high), 3=(low, low), 4=(high, low).
Compare four tasks by importance and effort to discuss work order.
Specify axes, criteria and boundaries. Position alone does not prove impact or priority.