Matrice organigramme blueprint en structure squads

Tech architecture infographic titled "Matrix Organizational Chart" using HOW-IT-WORKS archetype adapted as a squad / pod-based organizational structure diagram for a small team of 11-20 members. Create a blueprint schematic org chart with visually grouped departments and squads, hierarchical reporting lines, and text-only nodes with no avatars, no photos, no personal names. Show a clear top-down matrix structure with cross-functional pods.

Layout: central top leadership layer, middle functional department layer, lower pod / squad execution layer, plus dotted cross-functional matrix connections. Use labeled BOXES for each component connected by ARROWS and reporting lines showing direction of responsibility and collaboration.

Include these boxes as sharp readable text-only nodes:
- Executive Lead — top leadership — sets company strategy and priorities
- Operations Manager — operations — coordinates delivery and team rhythms
- Product Lead — product department — defines roadmap and business requirements
- Engineering Lead — engineering department — owns technical direction and delivery quality
- Design Lead — design department — ensures UX consistency and visual quality
- Data / Analytics Lead — analytics department — tracks metrics and informs decisions
- Pod A: Product Manager — pod leadership — prioritizes squad backlog and outcomes
- Pod A: Tech Lead — pod engineering — guides implementation and architecture
- Pod A: Designer — pod design — designs user flows and interfaces
- Pod A: Engineer 1 — pod engineering — builds product features
- Pod A: Engineer 2 — pod engineering — builds backend or frontend services
- Pod B: Product Manager — pod leadership — owns second squad objectives
- Pod B: Tech Lead — pod engineering — coordinates technical execution
- Pod B: Designer — pod design — supports usability and interface design
- Pod B: Engineer 1 — pod engineering — develops core functionality
- Pod B: Engineer 2 — pod engineering — maintains integrations and testing
- Shared QA / Support — shared services — validates releases and handles issues
- Shared Marketing / Sales Liaison — shared services — connects go-to-market feedback

Connection logic:
- Solid arrows downward for formal reporting lines
- Dotted arrows sideways for matrix collaboration lines across departments and pods
- Group Pod A and Pod B in visually framed cream panels
- Group Product, Engineering, Design, and Analytics as functional departments
- Show matrix relationships from department leads into corresponding pod roles

Arrow labels in English, using concise organizational flow terms such as:
- "Strategic direction"
- "Operational priorities"
- "Roadmap guidance"
- "Technical mentorship"
- "Design standards"
- "Metrics review"
- "Squad delivery"
- "Cross-functional support"
- "Feedback loop"

Add a numbered legend (1-7) in English explaining how the matrix organization works:
1. Executive leadership sets strategic goals for the organization.
2. Functional leads manage discipline standards across product, engineering, design, and analytics.
3. Squad leads translate strategy into pod-level priorities and delivery plans.
4. Cross-functional pod members execute work together inside each squad.
5. Team members receive day-to-day direction from pod leads and capability guidance from functional leads.
6. Shared services such as QA and marketing support multiple pods when needed.
7. Feedback, delivery status, and performance metrics flow back to leadership for planning.

Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout, blueprint schematic aesthetic, navy background with cream lines and boxes, subtle grid paper drafting feel, precise technical linework, tasteful framing throughout, clean spacing, elegant hierarchy, sharp typography, high legibility, organized and professional mood. Departments visually grouped with thin cream frames, reporting lines clearly separated from matrix dotted links, balanced composition for a small-team org chart.

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.