Create a professional organizational chart or process flow diagram with clear hierarchy, logical flow, and formatting suitable for internal documentation and team communication.

DIAGRAM FRAMEWORK:
Follow the appropriate path based on the diagram type requested:

FOR ORGANIZATIONAL CHARTS:
1. STRUCTURE ANALYSIS
   - Determine the hierarchy model: traditional top-down, matrix, flat, or hybrid
   - Identify reporting lines, dotted-line relationships, and any shared-resource structures

2. CHART CONSTRUCTION
   - Start from the top leadership and build downward level by level
   - Each node includes: Name (if provided), Title/Role, Department
   - Use consistent box sizing per level; distinguish levels visually
   - Show direct reports with solid lines; dotted lines for matrix or advisory relationships
   - Group departments with subtle background shading or color coding

3. SUPPLEMENTARY DETAILS
   - Add a legend explaining line types (solid = direct report, dotted = matrix/advisory)
   - Note headcount per department if data is available
   - Flag any open/vacant positions if mentioned

FOR PROCESS FLOW DIAGRAMS:
1. PROCESS MAPPING
   - Identify the trigger (what starts the process) and the end state (what signals completion)
   - Map every step sequentially, identifying decision points and parallel paths

2. DIAGRAM CONSTRUCTION
   Use standard flowchart notation:
   - Rounded rectangles: start/end points
   - Rectangles: process steps (actions)
   - Diamonds: decision points (yes/no or branching conditions)
   - Arrows: flow direction, labeled at decision branches
   - Parallelograms: inputs/outputs (documents, data)
   - Swimlanes: if multiple roles or teams are involved, separate into lanes

3. ANNOTATIONS
   - Label each step clearly and concisely (verb + noun: "Review application", "Send notification")
   - Add estimated time per step if known
   - Highlight bottlenecks or steps that commonly cause delays
   - Note any system integrations or handoff points between teams

OUTPUT CONSTRAINTS:
- Style: clean, professional, consistent spacing and alignment
- Use a clear visual hierarchy: larger/bolder elements for higher levels or critical steps
- Keep text in each node concise (under 6 words per box where possible)
- Include a title and date on the diagram
- If the provided information is incomplete, create the diagram with what is available and clearly mark placeholders with "[TBD]"
- For process flows with more than 15 steps, suggest breaking into sub-processes for readability
- Output the diagram in a format appropriate to the tool's capabilities (structured text, Mermaid syntax, or visual rendering)

---

MY INFO:

Diagram Type (org chart / process flow / both): (required)
Purpose (onboarding / process improvement / team planning / documentation / other): (required)

FOR ORG CHART:
  Company/Team Name: (required if org chart)
  Structure (hierarchical / matrix / flat): (optional)
  Departments & Team Leads: (required if org chart)
  Headcount per Department: (optional)
  Open/Vacant Positions: (optional)

FOR PROCESS FLOW:
  Process Name: (required if process flow)
  Start Point (trigger event): (required if process flow)
  Steps: (required if process flow)
    1.
    2.
    3.
  Decision Points (where does the process branch?): (optional)
  End Point (completion criteria): (required if process flow)
  Roles/Teams Involved (for swimlanes): (optional)
  Estimated Time per Step: (optional)