Org Org Chart Tech Company Hierarchy Infographic

Tech architecture infographic titled "Org Org Chart", HOW-IT-WORKS archetype adapted as a top-down hierarchical tree org chart. Create a clean top-down tree layout for a small company with 20–50 people, showing hierarchical reporting lines from leadership to departments to team roles. Use grouped labeled BOXES as org nodes connected by ARROWS or thin reporting lines indicating management structure and reporting direction from top to bottom. Each node must include: a small illustrated cartoon avatar icon, a generic role title in English, and a one-line role description in English. No real-person names, no photos, placeholder titles only.

Structure the chart with these grouped sections:
- Top level: Chief Executive Officer — "Sets company direction and final decisions"
- Executive layer: Chief Operating Officer — "Runs daily business operations"; Chief Technology Officer — "Leads product and engineering strategy"; Chief Revenue Officer — "Owns sales and growth targets"; Head of People — "Leads hiring and team development"; Finance Manager — "Owns budgeting and financial reporting"
- Under CTO / Technology department group: Engineering Manager — "Coordinates engineering execution"; Product Manager — "Defines roadmap and priorities"; UX/UI Designer — "Designs product experience and interfaces"; Backend Engineer — "Builds APIs and business logic"; Frontend Engineer — "Builds user-facing application"; QA Engineer — "Ensures product quality and testing"; DevOps Engineer — "Maintains deployment and infrastructure"; Data Analyst — "Tracks metrics and business insights"
- Under CRO / Revenue department group: Sales Manager — "Leads pipeline and closing"; Account Executive — "Converts leads into customers"; Sales Development Representative — "Qualifies outbound and inbound leads"; Marketing Manager — "Plans campaigns and brand positioning"; Content Specialist — "Creates demand-generation content"; Customer Success Manager — "Drives retention and account growth"
- Under COO / Operations department group: Operations Manager — "Improves workflows and delivery"; Project Coordinator — "Tracks timelines and cross-team tasks"; Support Lead — "Owns customer issue resolution"; Support Specialist — "Handles day-to-day support requests"
- Under Head of People / HR department group: Recruiter — "Sources and closes candidates"; People Operations Specialist — "Supports onboarding and policies"
- Under Finance department group: Accountant — "Manages books and reconciliations"; Financial Analyst — "Builds forecasts and reporting"

Visually group departments with soft containers labeled in English: Leadership, Technology, Revenue, Operations, People, Finance. Use arrows or clean reporting connectors between managers and direct reports. Add small connector labels in English where appropriate, such as "reports to", "team lead", "department owner", "cross-functional partner".

Include a numbered legend (1-7) in English explaining the org structure lifecycle:
1. Leadership defines company strategy
2. Department heads translate strategy into plans
3. Managers coordinate team execution
4. Specialists deliver functional work
5. Cross-functional partners collaborate across departments
6. Support and operations maintain business continuity
7. Feedback and metrics inform leadership decisions

Visual style: sketchnote, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a tech blue palette with white background, blue-gray containers, navy headings, cyan accents, soft hand-drawn sketch lines, tasteful framing, sharp readable role titles, friendly cartoon avatars, organized spacing, subtle depth, polished but informal startup aesthetic. Keep composition balanced and easy to scan, with small-company org chart density and clear hierarchy. 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.