High Level Gantt Chart Product Roadmap Infographic

Tech architecture infographic titled "High Level Gantt Chart" using HOW-IT-WORKS archetype, redesigned as a product roadmap timeline infographic with quarterly bullet-list structure and three planning horizons: Year 1, Year 3, Year 5. Show a clean roadmap board with labeled BOXES and feature cards arranged across quarter columns and a timeline axis, with swim lanes by team where applicable. Include connected ARROWS to show progression, dependencies, and milestone flow between roadmap items.

Layout: horizontal quarterly roadmap grid with clear quarter columns labeled Q1, Q2, Q3, Q4 repeated across the visible timeline, grouped into Horizon 1 (1 year), Horizon 2 (3 year), Horizon 3 (5 year). Add swim lanes such as Product, Platform, Data, Design, Growth, Operations. Within each lane, place rounded rectangular feature BOXES or pills with status indicators.

Each BOX must contain: a small generic tech/product icon, a realistic feature name in English, and a one-line role description in English. Example realistic boxes:
- User Research Hub — centralize customer insight notes and interview synthesis
- Billing Portal Refresh — simplify invoice access and subscription changes
- Team Permissions v2 — improve role-based access for admins and managers
- Analytics Event Cleanup — standardize tracking schema across key journeys
- API Rate Limit Controls — protect backend stability during peak traffic
- Mobile Navigation Update — reduce friction in core app browsing flows
- Reporting Export CSV — enable lightweight data extraction for operations teams
- Search Relevance Tuning — improve result ranking for common queries
- Design System Tokens — unify UI theming and component consistency
- Data Retention Controls — support configurable archive and deletion rules
- Workflow Templates — speed up repeat setup tasks for new accounts
- Audit Log Viewer — surface change history for compliance reviews

Status indicators on cards: Planned, In Progress, Shipped, rendered as sharp crisp labels or small colored badges. Use accurate quarter placement and realistic duration bars extending across one or more quarter columns. Show milestone diamonds where relevant.

Use ARROWS between related boxes with short labels in English describing what moves or depends on what, for example: "dependency", "handoff", "beta feedback", "release milestone", "design spec", "platform support", "analytics event schema". Keep arrow logic technically plausible for roadmap sequencing.

Add a numbered legend (1-7) walking through the roadmap lifecycle in English:
1. Discovery themes are gathered from research and support signals
2. Candidate initiatives are prioritized by team and horizon
3. Features are scheduled into quarter-based planning windows
4. Cross-team dependencies are mapped before delivery starts
5. In-progress work advances across the timeline with milestones
6. Shipped items are marked complete and retained for context
7. Longer-horizon bets stay high level and less granular

Visual style: warm boutique, polished editorial product-strategy infographic, subtle premium feel, navy base with warm accent palette such as amber, terracotta, sand, cream, muted coral, and soft gold. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Emphasize elegant spacing, refined card shadows, crisp timeline structure, sharp status chips, soft textured background, high readability, modern SaaS planning aesthetic, balanced information density.

Do not use vendor branding. Keep the composition visually searchable as a high level gantt chart without adding search-intent phrases as decorative text beyond the actual roadmap labels. Ensure quarter labels and horizon labels are accurate and consistent. 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 Status labels rendered sharp. Realistic feature names — no overpromising. Quarter / horizon labels accurate.