Corporate Structure Flowchart Tech Org Blueprint Infographic

Tech architecture infographic titled "Corporate Structure Flowchart" — HOW-IT-WORKS adapted as an org-structure hierarchy in a squad / pod-based layout for a 20–50 person small company. Create a blueprint schematic corporate org chart presented as a clean tech-style infographic with visually grouped departments and hierarchical reporting lines. Use illustrated cartoon avatars inside each node, but no real-person likenesses, no photos, and no personal names — placeholder role titles only. Show labeled BOXES / CARDS for each role node, connected by ARROWS / reporting lines indicating management structure and collaboration flow where relevant. Each node must contain: a small generic avatar icon, a role title in sharp readable English, and a one-line responsibility description in English. Organize the chart into grouped clusters with subtle frames: Executive Leadership, Product Pods / Squads, Platform / Engineering, Design, Operations, Sales / Marketing, Finance / People. Use a balanced top-down hierarchy with pod-based subtrees.

Suggested node structure:
- CEO — "Company Lead" — "Sets strategy and company direction"
- Executive Assistant — "Executive Support" — "Coordinates leadership operations"
- Head of Product — "Product Lead" — "Owns roadmap and priorities"
- Head of Engineering — "Engineering Lead" — "Leads delivery and technical execution"
- Head of Design — "Design Lead" — "Drives UX and visual quality"
- Head of Operations — "Operations Lead" — "Runs internal business processes"
- Head of Revenue — "Revenue Lead" — "Owns sales and growth execution"
- Finance Manager — "Finance" — "Manages budgeting and reporting"
- People Manager — "People Ops" — "Supports hiring and employee experience"

Pod / squad grouping:
- Pod A: Product Manager, Engineering Manager, Frontend Engineer, Backend Engineer, Product Designer, QA Engineer
- Pod B: Product Manager, Engineering Manager, Frontend Engineer, Backend Engineer, Product Designer, QA Engineer
- Pod C: Product Manager, Engineering Manager, Full-Stack Engineer, Data Analyst, Product Designer
- Platform Team: DevOps Engineer, Security Engineer, Data Engineer
- Go-To-Market Team: Sales Manager, Account Executive, Marketing Manager, Content Specialist, Customer Success Manager
- Business Support Team: Office Manager, Recruiter, Financial Analyst

Use BOXES grouped by department with thin blueprint divider lines and cream labels on navy background. Reporting ARROWS / lines should clearly show hierarchy from CEO to functional heads, then to pod leads, then individual contributors. Add a few lateral dotted connectors between Product, Engineering, and Design within each pod labeled in English such as "Sprint planning", "Feature delivery", "Design review", "Release coordination". If any arrow labels are used, keep them short and accurate to organizational flow, such as "Reports to", "Manages", "Pod coordination", "Cross-functional sync".

Add a numbered legend (1-7) in English explaining the org lifecycle and structure:
1. Executive leadership defines strategy
2. Functional heads translate strategy into goals
3. Product pods own delivery by area
4. Engineering and design collaborate inside each pod
5. Platform team supports shared infrastructure and security
6. Revenue and operations enable growth and business continuity
7. Reporting lines and cross-team links show accountability and coordination

Visual style: blueprint schematic, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Navy + cream palette with subtle cyan drafting accents, tasteful framing, crisp typography, sharp role titles, thin technical linework, structured spacing, elegant department containers, slightly playful cartoon avatars but still professional. Mood: organized, trustworthy, modern, schematic, polished. Ensure the final composition reads like a high-end corporate structure flowchart while preserving tech-infographic clarity. 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.