Organizational Chart for Project Team Startup Pods

Tech architecture infographic titled "Project Team Organizational Chart" using HOW-IT-WORKS archetype adapted as a squad / pod-based team structure for a 5-10 person startup. Create a clean organizational chart with labeled boxes as team nodes, connected by arrows and reporting lines that clearly show hierarchy and collaboration direction. Visually group nodes into pods / departments while keeping the overall composition balanced and easy to scan.

Include these boxes as canonical English role nodes, each with a simple icon, a role title, and a one-line English role description:
- Founder / CEO — sets vision and business priorities
- Product Manager — defines roadmap and coordinates delivery
- Tech Lead — owns technical direction and architecture
- Designer — creates UX flows and interface design
- Frontend Engineer — builds client-side product experience
- Backend Engineer — builds APIs and business logic
- QA Engineer — validates quality and release readiness
- Growth / Marketing — drives acquisition and user communication
- Operations / Admin — supports finance, hiring and team operations

Arrange them as a pod-based startup structure:
- Top level: Founder / CEO
- Second level: Product Manager and Tech Lead as key leads
- Product Pod grouped together: Product Manager, Designer, Frontend Engineer, Backend Engineer, QA Engineer
- Business Pod grouped together: Growth / Marketing, Operations / Admin
- Draw hierarchical reporting lines from Founder / CEO to leads and from leads to individual contributors
- Add lateral collaboration arrows between Product Manager, Designer, Tech Lead, Frontend Engineer, Backend Engineer, and QA Engineer

Each arrow must have a short English label describing what flows across the relationship, such as:
- "priorities"
- "roadmap"
- "design specs"
- "technical guidance"
- "feature delivery"
- "test feedback"
- "launch plan"
- "team support"

Add a numbered legend 1-7 in English walking through the team workflow lifecycle:
1. Founder / CEO sets company direction
2. Product Manager turns goals into roadmap
3. Tech Lead defines implementation approach
4. Designer prepares user experience and screens
5. Engineers build frontend and backend features
6. QA Engineer verifies quality before release
7. Growth / Operations support launch and team continuity

Visual style: hand-drawn whiteboard look, minimal monochrome palette, tasteful framing, slightly sketchy marker outlines, vector-clean infographic layout, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use mostly black, white, gray, and soft neutral accents, with subtle color-coded role pills for avatars only. No real-person names, no photos, no realistic faces, only generic avatar icons or pill markers. Keep role titles rendered sharp and readable. Departments should be visually grouped with light containers or outlined regions.

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.