Simplified Diagram¶
Artifact — instantiates Essential Structure Extraction
Uses a visual representation to show the essential parts and relations while suppressing incidental visual or textual detail.
A simplified diagram is a picture that deliberately drops incidental visual and textual detail — exact positions, true proportions, ornamentation, minor labels — so that a subject's relation structure (connection, sequence, adjacency, flow) becomes legible at a glance. Its defining move is a stated visual elision rule: an explicit policy for what the picture leaves out, which is what lets a viewer trust that the omissions were chosen, not accidental. It is indifferent to subject matter — a metro network, a manufacturing process, a family tree — because what makes it this mechanism is that legibility is bought by suppressing depiction, not by naming domain concepts (that is a Conceptual Model) nor by mapping a system's components for a decision (that is a High-Level Architecture Diagram).
Example¶
The geographic map of a metro network is unreadable to a rider underground: the lines wiggle, the outer stations crowd the edges, and nothing tells you where to change trains. Harry Beck's London Underground diagram famously fixed this with a hard elision rule — force every line to 45- or 90-degree angles, space the stations evenly regardless of true distance, throw away real geography entirely, and keep just one landmark, the river Thames, to stop riders getting disoriented.[n1] What survives exactly is the topology: the order of stations on each line and where lines interchange.
The result is one of the most copied information designs ever made, precisely because it kept the relations a rider needs and discarded the ones they do not. It also lies, honestly: two stations that sit a thumb's width apart on the diagram can be a three-minute walk at street level, because the diagram bought its legibility by distorting distance.
How it works¶
Decide what the diagram must let a reader do (trace connectivity, follow a sequence). Choose a visual grammar for it. Then state the elision rule — drop scale, absolute position, decoration — and hold the essential relations exact even while you distort the incidental ones. The distinctive property is that the elision is visual and rule-governed: because the omission policy is explicit and on the page, anyone can see what the picture is not telling them, and judge whether that is safe for their task.
Tuning parameters¶
- Elision aggressiveness — how much visual detail to drop. More gives a cleaner, more legible picture and more distortion of whatever was sacrificed.
- Which relations stay exact — topology, geometry, or scale. You can keep only some exact; choosing wrong hides the relation a viewer actually needs.
- Grammar constraints — how strict the angle/grid/shape rules are. Tighter grammar reads cleaner but bends the underlying reality further.
- Landmark retention — how many orienting anchors survive (Beck's river). Too few and the reader loses their bearings; too many and the clutter returns.
When it helps, and when it misleads¶
Its strength is that it makes relation structure graspable in a single glance — wayfinding maps, process flows, and org charts all work because a good elision rule turns tangle into pattern. Its failure is that people read the diagram literally: they treat its deliberate distortions (distance, scale, proportion) as facts, or a designer produces a diagram that is merely decorative — pretty, but preserving no real relation.[n1] The guarding discipline is to publish the elision rule alongside the picture, mark the dimensions it distorts, and refuse to use it for any task that turns on a dropped dimension — you do not plan a walking route from a topological transit map.
How it implements the components¶
essential_variable— the parts that must appear on the page (the stations, the process steps) are drawn as nodes.relation_preservation— the connections and sequence are held exact even as geometry is sacrificed; keeping them legible is the diagram's reason to exist.detail_elision_rule— the explicit visual policy for what is left off (scale, true position, ornament) is what makes the simplification auditable.
A simplified diagram suppresses incidental visual clutter to reveal any subject's relations; it does NOT map a system's components and dependencies at a decision altitude or define when to drill back into a component's internals (detail_reintroduction_trigger) — that is its nearest twin, High-Level Architecture Diagram.
Related¶
- Instantiates: Essential Structure Extraction — makes the extracted relation structure visible in a single glance.
- Sibling mechanisms: Conceptual Model · Core Schema · Problem Abstraction · Design Model · Mathematical Idealization · High-Level Architecture Diagram · Executive Summary
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Simplified Diagram operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it uses a visual representation to show the essential parts and relations while suppressing incidental visual or textual detail.
Independent corroboration: The frozen evidence defines Simplified Diagram as 'Uses a visual representation to show the essential parts and relations while suppressing incidental visual or textual detail', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Art & Aesthetics
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Suppressing incidental detail while preserving essential visual relations is graphic abstraction and diagrammatic design.
Related originating lineages:
- Education & Pedagogy — Instructional graphics select structure relevant to learning.
- Engineering & Design — Schematic diagrams retain functional relations while omitting physical detail.
- Human-Computer Interaction — Information visualization manages attention and cognitive load.
Review resolution: The blind reviewers agree that art_aesthetics is the primary origin and differ only on alternate origin disagreement, origin mode disagreement, domain reach disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain convergent because the combined evidence shows independent disciplinary development. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] "The map is not the territory" — Alfred Korzybski's dictum that a representation necessarily differs from the thing represented. A simplified diagram makes the gap deliberate and useful; the danger is that a fluent reader forgets the gap is there. ↩a ↩b