---
name: flowchart
description: Use when asked to draw a flowchart — start/end, process, decision, connector, and input/output symbols representing a process or workflow's sequence — as distinct from a mind map's radial, associative structure (see mind-map), which suits non-sequential idea structures rather than linear/branching process flow.
---

# Flowchart

A flowchart is a graphical representation of a process, system, or
workflow — using standardized symbols and arrows to depict the sequence
of steps and how information or materials flow from one step to the
next, widely used across business, engineering, programming, and project
management to make a complex process understandable at a glance.

## Key symbols

- **Start/End** — a rounded rectangle or oval marking where the process
  begins or ends.
- **Process step** — a rectangle representing a single action or task.
- **Decision** — a diamond representing a branch point, typically holding
  a question or condition, with arrows leading to different paths
  depending on the outcome.
- **Connector** — a small circle linking different parts of the chart,
  used to avoid cluttering the diagram with long crossing lines.
- **Arrow** — connects symbols and shows the direction/sequence of flow.
- **Input/Output** — a parallelogram marking where data or information
  enters or leaves the process.

## When a flowchart is the right tool

Flowcharts suit **sequential and branching** processes specifically — a
series of steps with clear decision points and a defined flow direction.
Contrast with [[mind-map]]'s radial, associative structure, which
suits non-sequential idea exploration rather than a process that actually
has a defined order and branching logic.

## Common uses

Documenting a business process, mapping a software algorithm's logic,
planning a project workflow, or communicating a procedure clearly enough
that someone unfamiliar with it could follow the steps correctly.

## Common pitfalls

- **Using a flowchart for genuinely non-sequential, associative content**
  — forcing ideas that don't have real sequence or branching logic into a
  flowchart's structure is a poor fit; [[mind-map]] suits that case
  better.
- **Missing decision-point branches** — a diamond with only one exit
  arrow isn't actually representing a decision; every real branch/outcome
  needs its own path shown.
- **Overcrowding one flowchart with too much detail** — a process with
  many sub-steps is often clearer as a top-level flowchart with separate,
  linked sub-flowcharts for detail, rather than one dense diagram trying
  to show everything at once.
- **No clear start/end** — a flowchart missing explicit start/end symbols
  leaves ambiguous where the represented process actually begins or
  terminates.

## Learn more

- [[mind-map]] for the complementary radial/associative diagramming technique for non-sequential content.
- [[plantuml-diagram]] for text-based, version-controllable flowchart/activity-diagram generation (`@startuml` activity diagrams).
- [[decision-tree]] for a related but distinct branching structure focused on decision outcomes rather than process flow.