Diagram of Organogram for a Squad-Based Startup

Tech architecture infographic titled "Organizational Chart for a Squad / Pod-Based Startup" using HOW-IT-WORKS archetype adapted as an org-structure flow. 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 5-10 person startup organizational chart with hierarchical reporting lines and visually grouped departments as squads / pods. Use labeled BOXES for each node connected by ARROWS or reporting lines showing direction of responsibility and escalation. Each box must contain a simple icon, a generic English role title, and a one-line role description in English. Use color-coded role pills or avatar-style markers for role categories, but no real-person names and no photos.

Layout: top leadership node, then pod-based branches underneath. Suggested structure: Founder / CEO, Product Lead, Engineering Lead, Designer, Software Engineer, Software Engineer, Growth / Marketing Lead, Operations / People Lead. Group nodes into visual clusters such as Product Pod, Engineering Pod, Growth Pod, Operations Pod. Reporting flow: Founder / CEO oversees Product Lead, Engineering Lead, Growth / Marketing Lead, Operations / People Lead; Product Lead collaborates with Designer and Software Engineers inside the Product Pod; Engineering Lead manages the Software Engineers inside the Engineering Pod. Show cross-functional dotted collaboration links between Product Lead, Designer, and Engineering Lead.

Each node box examples in English: 
- Founder / CEO — Sets vision and company priorities
- Product Lead — Defines roadmap and customer outcomes
- Engineering Lead — Owns technical delivery and architecture
- Designer — Crafts user experience and interface direction
- Software Engineer — Builds product features and fixes issues
- Software Engineer — Maintains backend and application logic
- Growth / Marketing Lead — Drives acquisition and brand messaging
- Operations / People Lead — Supports hiring, culture, and operations

Arrow / line labels in English for org relationships: "reports to", "manages", "collaborates", "pod alignment", "delivery coordination". Keep hierarchy visually clear and departments grouped with subtle enclosing frames or shaded hand-drawn boundaries.

Add a numbered legend (1-7) in English explaining the organizational lifecycle and collaboration model:
1. Founder / CEO sets company direction
2. Product and Engineering leaders align priorities
3. Product Pod defines goals and user needs
4. Engineering Pod plans and delivers implementation
5. Design supports product discovery and usability
6. Growth and Operations support go-to-market and team health
7. Cross-functional collaboration keeps squads aligned

Visual style: hand-sketched marker lines, whiteboard diagram look, minimal monochrome base with restrained accent colors only for role pills, sharp readable role titles, clean spacing, startup org clarity, balanced composition, no decorative clutter. No real-person names, no realistic portraits, no photos, only generic placeholder role titles. 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.