Copy of an Organizational Structure Diagram Flowchart

Tech architecture infographic titled "Organizational Structure Diagram Flowchart" — HOW-IT-WORKS archetype adapted as a radial / sunburst org-structure layout for a 5–10 person startup. Central hub box at the center: generic company node with icon, name "Company", one-line role description "Startup leadership and coordination center". Around it, render labeled boxes as hierarchical org nodes connected by arrows / reporting lines radiating outward in concentric rings. First ring: "Founder / CEO" — "Sets vision and final decisions"; second ring grouped department boxes: "Product" — "Defines roadmap and priorities", "Engineering" — "Builds and maintains the product", "Design" — "Shapes UX and visual system", "Marketing" — "Drives awareness and acquisition", "Sales / Operations" — "Handles revenue and business operations", "Customer Support" — "Helps users and resolves issues". Optional outer-ring individual contributor boxes for startup scale: "Frontend Engineer" — "Builds browser UI", "Backend Engineer" — "Implements APIs and services", "Product Designer" — "Designs flows and interfaces", "Growth Marketer" — "Runs campaigns and analytics", "Operations Manager" — "Coordinates finance and admin", "Support Specialist" — "Answers customer requests". Each node must include a simple icon, sharp English role title, and one-line English description. Use color-coded role pills / avatar-style generic badges, but no real-person names, no photos, no personal identity details. Visually group departments with subtle sage-tinted enclosing shapes. Connect every node with arrows or reporting lines labeled in English with short hierarchy descriptors such as "reports to", "team lead", "cross-functional sync", "roadmap input", "customer feedback". Add a numbered legend 1-7 explaining the organizational flow in English: 1. Company strategy starts at leadership. 2. CEO aligns department heads. 3. Product defines priorities. 4. Engineering and Design execute delivery. 5. Marketing and Sales / Operations drive growth and revenue. 6. Support returns customer feedback to the team. 7. Cross-functional collaboration keeps the startup aligned. Include small English metrics / captions where helpful, such as "Team size: 5–10", "Startup structure", "Department group". Visual style: isometric 3D org-diagram, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Palette: sage green, warm white, soft neutral grays, muted olive accents, tasteful framing, calm modern startup mood, clean shadows, crisp typography, high legibility, balanced spacing, elegant sunburst composition. Ensure hierarchical reporting lines are technically clear and visually readable. 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.