Organization Chart IT Company Startup Squad Infographic

Tech architecture infographic titled "IT Company Organization Chart" using HOW-IT-WORKS archetype adapted as a squad / pod-based org structure for a 5–10 person startup. Create a clean hierarchical organizational chart with visually grouped departments and clear reporting lines, framed like a polished corporate infographic. Show labeled BOXES as org nodes connected by ARROWS indicating reporting direction from leadership to squads and support roles. Include compact color-coded role pills or generic avatar icons inside each node, no real photos, no personal names.

Layout: top-down hierarchy with grouped pods. Top row: CEO / Founder — "Company Lead" — "Sets vision and business direction". Second row split into core leaders: CTO — "Engineering Lead" — "Owns technical strategy and delivery"; COO / Operations Manager — "Operations Lead" — "Runs processes and coordination". Third row: Product Manager — "Product Owner" — "Defines roadmap and priorities"; Tech Lead — "Engineering Coordinator" — "Guides architecture and code quality"; Designer — "Product Designer" — "Shapes UX and visual design". Fourth row as squad / pod members: Frontend Developer — "Frontend Engineer" — "Builds client-side interfaces"; Backend Developer — "Backend Engineer" — "Builds APIs and business logic"; QA / Tester — "Quality Engineer" — "Verifies features and release quality"; DevOps / Platform — "Platform Engineer" — "Maintains deployment and infrastructure"; Customer Success / Sales optional small node — "Business Support" — "Handles clients and growth". Keep total headcount visually within 5–10 startup scale.

Arrows and labels: CEO to CTO labeled "strategy alignment"; CEO to COO labeled "operations goals"; CTO to Product Owner labeled "product direction"; CTO to Engineering Coordinator labeled "technical leadership"; Product Owner to Designer labeled "requirements"; Engineering Coordinator to Frontend Engineer labeled "feature implementation"; Engineering Coordinator to Backend Engineer labeled "API delivery"; Engineering Coordinator to Quality Engineer labeled "test scope"; Engineering Coordinator to Platform Engineer labeled "release pipeline"; COO to Business Support labeled "customer feedback"; optional dotted cross-functional arrows between Product Owner, Designer, Frontend Engineer, Backend Engineer labeled "squad collaboration". Use arrow directions consistently top-down, with optional lateral collaboration lines visually distinct.

Add a numbered legend (1-7) in English explaining the org workflow lifecycle: 1. Leadership sets company goals. 2. Product and engineering leads turn goals into roadmap. 3. Designer and product owner prepare solution scope. 4. Engineering pod splits work by frontend and backend. 5. Quality and platform roles support delivery readiness. 6. Operations and business support collect market and customer input. 7. Feedback loops back to leadership for next priorities.

Visual style: classic corporate, pastel office palette, tasteful framing, soft blue, mint, lavender, peach, and light gray accents, subtle shadows, crisp typography, balanced white space, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Departments should be visually grouped with soft containers such as Leadership, Product & Design, Engineering Pod, Operations & Support. Each role title rendered sharp and readable in English. Use generic business and tech icons only, no real-person likenesses, no real-person names, no logos.

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.