Use SmartArt and Create Organization Chart Infographic

Tech architecture infographic titled "Use SmartArt and Create Organization Chart"; SYSTEM ARCHITECTURE adapted as an organizational hierarchy infographic in a flat departmental grid. Create a clean org-chart style diagram with labeled BOXES connected by ARROWS / reporting lines showing hierarchy and information flow direction. Arrange 20–50 small-company roles into visually grouped departments with sharp readable role titles, generic placeholder titles only, no real-person names, no photos. Include illustrated cartoon avatars inside or beside each node.

Top row: executive leadership boxes centered and prominent. Example nodes: "Chief Executive Officer — Leads company strategy and decisions", "Chief Operating Officer — Oversees daily operations", "Chief Technology Officer — Guides product and engineering", "Chief Financial Officer — Manages finance and planning".

Second and third rows: grouped departmental clusters in a flat grid with subtle monochrome grouping frames. Example department groups and canonical English role boxes:
- Product: "Product Manager — Defines roadmap and priorities", "Product Designer — Shapes user experience"
- Engineering: "Engineering Manager — Leads software delivery", "Frontend Engineer — Builds client interfaces", "Backend Engineer — Develops server logic", "QA Engineer — Validates product quality", "DevOps Engineer — Maintains infrastructure"
- Sales: "Sales Director — Leads revenue strategy", "Account Executive — Closes customer deals", "Sales Development Rep — Qualifies new leads"
- Marketing: "Marketing Manager — Runs campaigns and positioning", "Content Specialist — Produces marketing content"
- Customer Support: "Support Lead — Oversees customer help", "Support Specialist — Resolves user issues"
- Human Resources: "HR Manager — Manages people operations", "Recruiter — Sources new talent"
- Finance & Admin: "Finance Manager — Tracks budgets and reporting", "Office Administrator — Supports office logistics"

Add more small-company nodes as needed to reach a believable 20–50 node structure while keeping readability. Every box must contain: a simple icon, a role title in English, and a one-line role description in English. Connect leadership to department heads with straight reporting ARROWS/lines, then to individual contributor boxes beneath them. Use short arrow labels in English such as "reports status", "team goals", "project updates", "budget approval", "hiring request", "support escalation", "roadmap input", "performance review".

Add a numbered legend (1-7) in English walking through the organizational lifecycle:
1. "Executive leadership sets company direction"
2. "Department heads translate strategy into plans"
3. "Managers assign work across teams"
4. "Individual contributors execute daily tasks"
5. "Teams share status and dependencies"
6. "Department leads escalate risks and decisions"
7. "Leadership reviews outcomes and updates priorities"

Visual style: hand-drawn whiteboard look, minimal monochrome palette, black/charcoal ink on white background, subtle gray grouping panels, sketch-style arrows, tasteful framing throughout, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Mood: clear, instructional, organized, smart, approachable. Ensure departmental groups are visually separated but cohesive in one balanced grid. No real cloud-vendor logos; use generic office, team, hierarchy, document, chat, gear, and analytics icons. 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.