Schedule Graph Template Quarterly Product Roadmap

Tech architecture infographic titled "Schedule Graph Template" using HOW-IT-WORKS archetype adapted as a quarterly product roadmap over two years. Create a consultant-deck roadmap infographic with a clean timeline axis and quarter columns: Year 1 Q1, Q2, Q3, Q4; Year 2 Q1, Q2, Q3, Q4. Use horizontal swim lanes by team where applicable, such as Product, Design, Engineering, Data, and Operations. Render labeled BOXES as feature cards or rounded pills placed in the appropriate quarter cells, each connected by subtle ARROWS where dependencies or rollout sequence exist. Each box must include: a small icon, a feature name in canonical English, and a one-line role description in English. Use realistic feature names for a schedule graph template product, for example: "Template Gallery — Browse reusable scheduling layouts", "Quarterly Timeline View — Show milestones across quarters", "Dependency Lines — Visualize task relationships", "Team Swim Lanes — Group work by owner", "Status Filters — View planned, in-progress, shipped items", "Export to PDF — Share roadmap snapshots", "Editable Milestones — Update dates and labels", "Baseline Comparison — Compare original vs current plan", "Access Permissions — Control editing rights", "Version History — Track roadmap changes", "CSV Import — Load task data", "Presentation Mode — Clean stakeholder view". Add clear status indicators on each feature card: Planned, In-Progress, or Shipped, rendered as sharp consultant-style pills. Include ARROWS labeled in English for sequencing or handoff, such as "design spec", "implementation", "beta feedback", "GA release", "data import", "status sync". Add a numbered legend (1-7) in English walking through the roadmap lifecycle: 1. Discover needs, 2. Define scope, 3. Design workflow, 4. Build core features, 5. Validate with users, 6. Launch broadly, 7. Optimize and maintain. Emphasize accurate quarter labels and realistic horizon planning, with quarterly bullet-list structure inside each quarter column where useful. Visual style: consultant deck, warm earth palette with sand, clay, terracotta, muted olive, warm brown, and off-white; polished presentation mood, strategic and executive-friendly. Use 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.