Catalog
concept#Software Engineering#Architecture#Product

Flowchart

Symbolic visualization of steps, decisions, and process flows.

A flowchart visualizes sequential steps, decisions, and process flows using standard symbols.
Established
Low

Classification

  • Medium
  • Organizational
  • Design
  • Intermediate

Technical context

Mermaid, Graphviz or similar diagram enginesDocumentation platforms (Confluence, Notion)Ticket and process management tools (Jira)

Principles & goals

Clarity over completeness: show only relevant steps.Use consistent symbols and a legend.Iterate and refine diagrams based on feedback.
Discovery
Domain, Team

Use cases & scenarios

Compromises

  • Outdated diagrams lead to incorrect assumptions.
  • Overreliance on static flows hinders flexible solutions.
  • Omitting stakeholders creates blind spots.
  • Start with a coarse as‑is model, then add detail.
  • Use colors and legend sparingly for emphasis.
  • Link diagrams to responsibilities and artifacts.

I/O & resources

  • Process descriptions or interviews
  • Org chart and role descriptions
  • System and interface specifications
  • Flowchart file (SVG/PNG/tool format)
  • Action list based on findings
  • Test and validation scenarios

Description

A flowchart visualizes sequential steps, decisions, and process flows using standard symbols. It supports analysis, communication, and documentation of business and software processes and helps identify errors. Flowcharts are tool-agnostic, aid problem solving, clarify handovers, and make decision logic explicit. They are widely used in workshops.

✔

  • Improved communication between domain and technical views.
  • Faster identification of decision and error points.
  • Foundation for testing, automation and onboarding.

✖

  • Not sufficient for highly dynamic or event-driven systems.
  • Too much detail reduces diagram readability.
  • Different interpretations possible without a legend.

  • Readability (reviewer rating)

    Subjective reviewer rating of diagram understandability.

  • Number of decision branches

    Counts complex branches that increase maintenance effort.

  • Freshness rate

    Share of diagrams reviewed within a defined time period.

E‑commerce order process

Visualization of selection, payment, stock check and shipping decisions to align product and operations.

Data validation logic

Flowchart representing validation steps, error paths and return mechanisms for APIs.

Customer support escalation

Documentation of support levels, escalation criteria and communication channels for rapid decision making.

1

Define the goal and scope of the flowchart.

2

Gather information via interviews and artifacts.

3

Create initial draft, review and iterate refinements.

4

Establish symbol conventions and version storage.

5

Regular review and maintenance in the lifecycle.

⚠️ Technical debt & bottlenecks

  • Outdated templates without version history.
  • Proprietary diagram formats without export options.
  • Missing integration into CI/CD documentation flows.
decision-pointscomplexity-growthstakeholder-alignment
  • Attempting to represent asynchronous event flows fully with simple flowcharts.
  • Using highly technical symbols in domain workshops.
  • Not updating diagrams after process changes yet using them as reference.
  • Premature formalization before full domain understanding.
  • Confusing process flow with organizational chart.
  • Neglecting exceptions and error paths in the depiction.
Process modeling and domain analysisVisual communication and facilitationBasic system and interface design knowledge
Process transparencyTraceability of errors and decisionsCross-functional communication
  • • Scaling large processes on a single diagram is limited.
  • • Unclear symbol conventions cause misunderstandings.
  • • Diagrams are static and do not capture runtime data.