Pure Project Organization Structure Infographic Blueprint

Tech architecture infographic titled "Pure Project Organization Structure" using HOW-IT-WORKS archetype adapted as a left-to-right hierarchical tree for an enterprise org chart. Create a clean left-to-right reporting structure with visually grouped departments and clear parent-child connectors. Show a large 150+ enterprise projectized organization where authority flows through projects rather than functional silos. Use labeled BOXES for each organizational component, each connected by ARROWS indicating reporting or coordination direction from left to right. Every node must include: a small generic icon, initials in a circle avatar, a role title in English, and a one-line English role description.

Suggested node hierarchy and grouping:
- Executive Sponsor box — icon: flag — role description: "Provides strategic direction and funding"
- Project Management Office box — icon: clipboard — role description: "Sets governance, standards and portfolio oversight"
- Program Director box — icon: compass — role description: "Leads multiple strategic projects"
- Project Director A box — icon: roadmap — role description: "Owns delivery for Project A"
- Project Director B box — icon: roadmap — role description: "Owns delivery for Project B"
- Project Director C box — icon: roadmap — role description: "Owns delivery for Project C"

Under each Project Director, render grouped project teams with boxes such as:
- Project Manager — "Coordinates scope, schedule and budget"
- Technical Lead — "Guides solution design and engineering decisions"
- Business Analyst — "Defines requirements and stakeholder needs"
- Solution Architect — "Designs end-to-end project architecture"
- Engineering Team — "Builds and integrates the solution"
- Quality Assurance Lead — "Validates quality and test coverage"
- UX/UI Lead — "Designs user flows and interface standards"
- Data Lead — "Manages project data models and reporting"
- Change Manager — "Drives adoption, training and communications"
- Procurement Lead — "Coordinates vendors, contracts and sourcing"
- Risk and Compliance Lead — "Monitors controls, policy and project risk"
- Project Controller — "Tracks cost, forecasting and financial status"

Add support/shared service boxes connected with dotted coordination arrows where appropriate:
- Finance Partner — "Supports budget control and approvals"
- HR Partner — "Supports staffing and role allocation"
- Legal Support — "Reviews contracts and compliance matters"
- Vendor Management — "Coordinates external delivery partners"

Arrow labels must be in English and describe organizational flow such as:
- "strategic direction"
- "portfolio governance"
- "project authority"
- "status reporting"
- "resource coordination"
- "risk escalation"
- "delivery oversight"
- "cross-project support"

Add a numbered legend 1-7 in English explaining the organizational lifecycle:
1. Executive Sponsor defines strategic priorities.
2. PMO establishes governance and reporting standards.
3. Program Director aligns multiple projects to business goals.
4. Project Directors own delivery within dedicated project structures.
5. Project Managers coordinate scope, schedule, budget and teams.
6. Specialist leads execute delivery within each project team.
7. Support functions provide advisory services without replacing project authority.

Emphasize that this is a pure project organization structure: project teams are dedicated to projects, reporting lines primarily follow project leadership, and departments are visually grouped by project rather than by function. Use sharp, readable English role titles only, no real-person names, no photos, only placeholder initials in circular avatars. Visual style: blueprint schematic, navy and cream palette, precise linework, subtle grid background, tasteful framing, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. 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.