Organizational Chart With Duties and Responsibilities

Tech architecture infographic titled "Organizational chart with duties and responsibilities" using HOW-IT-WORKS adapted as a left-to-right hierarchical tree for a 5-10 person startup org structure. Show a clean left-to-right reporting layout with visually grouped departments and hierarchical reporting lines. Render labeled boxes as org nodes connected by arrows/lines indicating reporting direction from leadership to teams. Include color-coded role pills and simple generic avatar icons inside each node, but no real-person names or photos, only placeholder role titles.

Main structure:
- Leftmost root node: "Founder / CEO" — "Sets vision, strategy, and final decisions"
- Second level grouped branches:
  1. "Product Lead" — "Defines roadmap, priorities, and customer value"
  2. "Engineering Lead" — "Builds product systems and manages delivery"
  3. "Operations / Finance" — "Runs budget, admin, and internal processes"
  4. "Growth / Sales" — "Generates demand, closes deals, and grows revenue"
- Third level supporting roles:
  - Under Product Lead: "Product Designer" — "Designs UX, flows, and interface consistency"
  - Under Engineering Lead: "Software Engineer" — "Implements features, APIs, and bug fixes"
  - Under Engineering Lead: "QA / Support" — "Tests releases and handles customer issues"
  - Under Growth / Sales: "Marketing Generalist" — "Creates campaigns, content, and lead generation"
  - Under Operations / Finance: "People / Admin" — "Supports hiring, onboarding, and office operations"

Use arrows or reporting connectors labeled in English with concise relationship text such as:
- "Reports to"
- "Owns roadmap"
- "Delivers product"
- "Supports operations"
- "Drives revenue"
- "Design handoff"
- "Release feedback"

Add small duty callouts or sublabels for each node in English, for example:
- CEO: "Fundraising, hiring, strategy"
- Product Lead: "Requirements, prioritization"
- Engineering Lead: "Architecture, sprint execution"
- Product Designer: "Wireframes, prototypes"
- Software Engineer: "Frontend, backend, integrations"
- QA / Support: "Testing, incident triage"
- Growth / Sales: "Pipeline, demos, conversion"
- Marketing Generalist: "SEO, email, content"
- Operations / Finance: "Payroll, vendors, compliance"
- People / Admin: "Recruiting, onboarding, coordination"

Include a numbered legend 1-7 walking through the organizational operating lifecycle in English:
1. "CEO sets company direction and top priorities"
2. "Product Lead turns strategy into roadmap"
3. "Design and Engineering align on scope and delivery"
4. "Engineers build and release product increments"
5. "QA / Support validates quality and collects issues"
6. "Growth / Sales and Marketing bring users and revenue"
7. "Operations / Finance and People / Admin keep the company running"

Visual style: hand-drawn whiteboard look, minimal monochrome palette with subtle grayscale boxes and selective muted accent colors only for role pills, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Mood: thoughtful, startup-focused, tasteful framing, structured, airy spacing, sharp readable role titles, departments visually grouped with soft outlines or brackets, sketched connector lines, clean negative space, no clutter. 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.