Product Roadmap Layout Infographic for 18-Month Timeline

Tech architecture infographic titled "Product Roadmap Layout" using HOW-IT-WORKS archetype adapted as a quarterly roadmap timeline over 18 months. Create a structured product-roadmap infographic with 6 quarter columns on a horizontal timeline axis: Q1, Q2, Q3, Q4, Q5, Q6, covering 18 months accurately. Add optional swim lanes by team such as Product, Platform, Design, Growth, and Operations. Render labeled BOXES as feature cards or pills inside the quarter columns, each connected with subtle ARROWS to show progression, dependencies, handoff, or lifecycle movement across quarters. Each box must include: a small icon, a feature name in canonical English-tech form, and a one-line role description in English. Use realistic, grounded feature names only, such as "Roadmap Filters", "Team Swim Lanes", "Status Badges", "Quarter Export", "Dependency View", "Portfolio Rollup", "Stakeholder Notes", "Capacity Markers", "Milestone Pins", "Release Summary". Add sharp status indicators on each feature card: Planned, In Progress, Shipped. Use arrows with short English labels such as "scope defined", "design handoff", "build phase", "QA review", "release", "customer feedback", "iteration". Include a numbered legend 1-7 explaining the roadmap lifecycle in English, for example: 1. Themes are collected, 2. Features are prioritized, 3. Items are scheduled into quarters, 4. Cross-team dependencies are mapped, 5. Work moves to in progress, 6. Shipped items are marked complete, 7. Feedback informs the next quarter. Make the composition read like a premium editorial developer-blog illustration while still being a clean roadmap planning graphic. Visual style: warm boutique, elegant but practical, navy base with warm accent palette such as cream, amber, terracotta, muted gold, and soft coral; crisp status labels; refined typography; subtle depth; balanced whitespace; flat or lightly isometric vector-clean infographic layout. Show quarter columns, timeline markers, bullet-list structure within cards where appropriate, and clear separation between teams. Include small supporting metrics or labels in English such as "Priority", "Owner", "Target", "Blocked", "Done" where useful. Ensure the diagram feels like a polished software planning system, not a marketing poster. 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 Status labels rendered sharp. Realistic feature names — no overpromising. Quarter / horizon labels accurate.