Company Department Structure Chart for Startup Pods

Tech architecture infographic titled "Company Department Structure Chart"; archetype: SYSTEM ARCHITECTURE adapted as a squad / pod-based org structure diagram for a 5–10 person startup. Create a hierarchical org-chart style layout with visually grouped department clusters and clear reporting lines, while preserving a clean tech-infographic structure with labeled boxes and directional connectors. Top level: one parent box for "Company Leadership" with icon, name, and one-line role description: "Sets strategy and approves priorities." Below it, connect ARROWS downward to grouped team boxes representing pods / departments. Include boxes for: "Founder / CEO" — "Owns company vision and final decisions"; "Product Pod" — "Defines roadmap and customer priorities"; "Engineering Pod" — "Builds and maintains the product"; "Design" — "Shapes user experience and interface"; "Operations / Admin" — "Handles finance, hiring support and internal process"; "Growth / Sales" — "Drives customer acquisition and revenue"; optional small startup roles inside pods as child boxes: "Product Manager" — "Coordinates scope and delivery"; "Software Engineer" — "Implements features and fixes"; "Full-Stack Engineer" — "Works across frontend and backend"; "Designer" — "Creates UX flows and visual design"; "Operations Manager" — "Runs day-to-day business operations"; "Sales / Growth Lead" — "Owns outreach and conversion". Each node must be a rendered BOX with a simple generic icon, sharp role title, and one-line English description. Use color-coded role pills or avatar-like markers for role category accents, but no real-person names, no real-person photos, only placeholder role titles. Show hierarchical reporting lines with ARROWS; arrow labels in English should describe org relationships such as "reports to", "aligns on roadmap", "delivers product input", "supports hiring", "shares customer feedback". Add small cross-functional dotted arrows between Product, Engineering, Design, and Growth to show pod collaboration, labeled with accurate English phrases like "roadmap input", "feature requirements", "user feedback", "launch coordination". Add a numbered legend 1-7 in English walking through how the startup operates: 1. Leadership sets company direction. 2. Product turns goals into roadmap. 3. Design shapes user flows and interfaces. 4. Engineering builds and ships features. 5. Growth / Sales brings market feedback and demand. 6. Operations supports people, finance and process. 7. Pods sync across functions and report outcomes upward. Visual style: hand-drawn whiteboard look, minimal monochrome palette with restrained grayscale boxes and thin black connector lines, subtle role-pill accents for categories, tasteful framing, lightly sketched outlines, developer-friendly editorial composition. Overall mood: smart, minimal, structured, startup-focused, readable, polished but informal. Composition should resemble an editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real-person names or photos. Generic role titles. Tasteful framing throughout.