Creating an Agile Roadmap Quarterly Swim-Lane Infographic

Tech architecture infographic titled "Creating an Agile Roadmap" using HOW-IT-WORKS archetype, adapted as a quarterly swim-lane product roadmap over an 18-month horizon. Show a dark background canvas with 6 quarter columns in sequence: Q1, Q2, Q3, Q4, Q5, Q6, with a clear horizontal timeline axis and vertical swim lanes by team. Teams as labeled boxes/lanes in English: Product Management, Design & Research, Engineering Platform, Application Engineering, Data & Analytics, Go-to-Market. Populate each lane with connected feature cards / milestone boxes styled as modern startup roadmap items, each box containing an icon, a feature name, and a one-line role description in English, plus a sharp status pill: Planned, In Progress, or Shipped. Use realistic, non-hyped feature names related to creating an agile roadmap, such as Roadmap Principles, Stakeholder Alignment Workshops, Outcome-Based Themes, Capacity Planning Baseline, Discovery Intake Process, Prioritization Framework, Quarterly Planning Cadence, Dependency Mapping, Initiative Scoring Model, Now-Next-Later View, Customer Feedback Loop, Delivery Metrics Dashboard, Release Readiness Checklist, Cross-Team Planning Rituals, Backlog Health Review, Roadmap Update Workflow, Executive Summary View, Retrospective Improvements. Connect major boxes with arrows showing progression and dependency direction across quarters and between teams. Every arrow must have a short English label describing what moves across the system, such as Strategic goals, Research insights, Prioritized initiatives, Team capacity, Delivery plan, Dependency update, Customer feedback, Usage metrics, Release notes, Roadmap revision. Include supporting architecture-style components as labeled boxes where helpful: Stakeholders, Customer Research Repository, Prioritization Board, Team Backlogs, Delivery Dashboard, Feedback Channel. Each box must include a simple tech-style icon, canonical English name, and concise role description in English. Add a numbered legend 1-7 in English walking through the lifecycle of creating an agile roadmap: 1 Define goals and planning horizon, 2 Gather research and stakeholder inputs, 3 Group work into outcome-based themes, 4 Prioritize initiatives against capacity, 5 Schedule work by quarter and team lane, 6 Track progress and shipped outcomes, 7 Review feedback and update roadmap. Make the layout read like an editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Visual style: modern startup, dark mode neon palette with charcoal background, electric cyan, violet, magenta, lime accents, subtle grid, glowing edges, crisp cards, high contrast status pills, clean geometric arrows, polished SaaS-planning aesthetic, focused and credible mood. Ensure quarter labels and 18-month horizon are accurate and visually prominent. Avoid vendor branding; use generic product-planning and analytics icons. 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.