Organizational Chart Using Excel for Squad-Based Teams

Tech architecture infographic titled "Organizational Chart Using Excel" using HOW-IT-WORKS archetype adapted as a squad / pod-based organizational structure diagram for a small team of 11–20 people. Create a hand-drawn whiteboard style, minimal monochrome palette, tasteful framing, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Show a hierarchical org chart with visually grouped departments / pods, text-only nodes, no avatars, no photos, no real-person names. Use sharp readable English labels only.

Layout: top-down hierarchy with grouped squads / pods. At the top, one main box: "Head of Organization" — role description: "Sets direction and oversees all pods". Below it, connected by reporting-line arrows, 3 to 4 department / pod group containers with labeled boxes inside. Suggested pods and roles for a 11–20 person team:
1. "Leadership Pod" containing boxes: "Operations Lead" — "Coordinates execution and planning"; "People Manager" — "Supports hiring and team health"
2. "Product Pod" containing boxes: "Product Manager" — "Defines priorities and roadmap"; "Business Analyst" — "Translates needs into requirements"; "Project Coordinator" — "Tracks delivery milestones"
3. "Delivery Pod" containing boxes: "Engineering Lead" — "Guides technical execution"; "Software Engineer" — "Builds core features"; "Software Engineer" — "Implements product changes"; "QA Specialist" — "Verifies quality and test coverage"
4. "Customer Pod" containing boxes: "Customer Success Lead" — "Owns client outcomes"; "Support Specialist" — "Handles incoming issues"; "Marketing Specialist" — "Promotes product messaging"; "Sales Coordinator" — "Supports pipeline and outreach"
Optionally add 2–4 extra boxes to reach the 11–20 range, such as "Designer" — "Creates user-facing visuals"; "Data Analyst" — "Monitors metrics and reporting"; "HR Coordinator" — "Supports people operations"; "Finance Coordinator" — "Tracks budgets and spend".

Each node must be a labeled BOX with a small generic role icon, a canonical English role title, and a one-line English description. Reporting lines must be clear with arrows or connector lines showing hierarchy and dotted lateral collaboration links across pods where relevant. Department / pod groups should be visually enclosed or bracketed and clearly titled in English.

Arrow / connector labels in English should describe relationship flow, such as: "reports to", "team oversight", "delivery coordination", "cross-functional collaboration", "status updates", "resource planning". Keep labels concise.

Add a numbered legend (1–7) in English explaining how the org structure works:
1. Leadership sets overall direction and priorities
2. Department leads translate strategy into team goals
3. Product roles define requirements and timelines
4. Delivery roles build, test, and release work
5. Customer-facing roles gather feedback and support users
6. Cross-pod collaboration aligns execution across functions
7. Reporting lines clarify accountability and escalation paths

Visual guidance: hand-sketched marker lines, whiteboard texture, monochrome black / charcoal / soft gray, minimal shading, clean spacing, balanced symmetry, strong readability, no clutter. Emphasize grouped squads / pods, hierarchical reporting structure, and professional placeholder role titles only. No Excel UI screenshot, but the composition should feel like a polished diagram someone could recreate in Excel. 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.