Process Mapping and Workflow Diagramming Standards Specification
Define standardized visual notation, iconography, and spatial rules for operational process architecture.
Use this template when establishing unified visual diagramming standards across operations, engineering, and HR workflows. It produces an unambiguous specification covering syntax, color signaling, and responsive zoom levels.
Role: Lead Systems Designer & Process Visualization Architect
Context
- Operational Domain: {{team_domain}}
- Target Diagramming Stack: {{tooling_ecosystem}}
- Process Complexity: {{complexity_tier}}
- Governance Ownership: {{governance_model}}
- Primary Diagram Archetypes: {{primary_diagram_archetypes}}
- Audience Personas: {{stakeholder_consumers}}
Task
Formulate a rigorous visual mapping and notation specification for {{team_domain}} to standardize the visual structure, node syntax, connector semantics, and layout flow of all workflow diagrams produced in {{tooling_ecosystem}}.
Method
- Define directional flow rules, swimlane proportions, milestone markers, and canvas grid alignment standards.
- Standardize geometric node primitives (shapes, corner radii, stroke widths) to map strictly to operational actions (events, activities, gateways, artifacts).
- Establish connector semantics detailing line styles (solid, dashed, dotted), arrowheads, routing angles (orthogonal vs straight), and crossing conventions.
- Design a semantic color token system for status signaling (active, blocked, automated, manual, external dependency) adapted for {{complexity_tier}}.
- Specify typographic labeling rules inside nodes, along connector paths, and on boundary containers.
- Detail iconography integration guidelines, defining scale, positioning, and approved icon sets within nodes.
- Create abstraction rules for progressive disclosure across different viewing zoom levels for {{stakeholder_consumers}}.
- Establish metadata annotation standards, including version tags, owner attribution, and system integration badges.
Constraints
- MUST define explicit geometric parameters (width, height, radius, stroke px) for every standard node shape.
- MUST NOT permit non-standardized flowchart shapes outside the approved notation registry.
- Connectors MUST use orthogonal routing by default with explicit rules for handling line intersections.
- The design system MUST remain natively constructible within {{tooling_ecosystem}} without third-party plugins.
Output format
Deliver an end-to-end diagramming specification organized into these mandatory sections:
- Canvas Setup, Swimlanes & Spatial Layout Standards
- Shape & Node Component Registry (with geometry rules)
- Connector Taxonomy & Line Routing Rules
- Status Signaling & Semantic Color Palettes
- Typography, Labeling & Iconography Rules
- Governance, Lifecycle & Maintenance Protocols (aligned with {{governance_model}}) Target word count is 700 to 1050 words.
Self-review
- Verify that each diagram archetype specified in {{primary_diagram_archetypes}} is supported by the notation rules.
- Ensure connector crossing rules prevent visual ambiguity in dense multi-system flows.
- Check that node dimension and text truncation standards account for varied screen sizes.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.