Circuit Diagram vs Flowchart

回路図 / フローチャート

Both sit in Diagrammatic Expression, so the question is not what they belong to but how they behave. One is style and the other layout. They are reached for with some of the same intent, which is where they get confused.

Circuit Diagram

An engineering language that draws circuits with standardized symbols and orthogonal lines. Discarding physical placement to record only connection, it arrived at a topological way of drawing well before the transit map did.

Flowchart

The Gilbreths invented this process diagram for work analysis. Its grammar of shapes gives a diamond to every decision and a rectangle to every process, and by way of programming it became the common language for thinking in steps.

Circuit DiagramFlowchart
Era1890s–1921–
FamilyDiagrammatic ExpressionDiagrammatic Expression
KindStyleLayout
CuesStandardized component symbols / Orthogonal wiring / Junction dots / Abstraction from physical layoutA grammar of shapes / The decision diamond / Arrows of flow / Start and end terminals
Best used forRecording connection intent in a form another engineer can inherit · Explaining how a device works as a system in a manual or courseGetting a team to agree on a work procedure that branches · Surfacing branches and exceptions in a spec before implementation
TypeOne symbol standard throughout, values and part numbers alongsideA question inside every diamond, a verb first sentence in rectangles
CompositionSignal left to right, supply at the top, ground at the bottomMain path down one column, branches right and always rejoining
MaterialJunctions always shown by a dot, crossings passing straightEach branch labeled with its answer, terminals only at both ends
CautionRouting the drawing to match the physical board hides the flow of signal and throws away the abstraction that made the diagram useful.Mixing diamonds and rectangles without respecting their meanings erases the line between decision and process, and readers guess.

IndexStyle