Multi Year Roadmap Tech Architecture Infographic

Tech architecture infographic titled "Multi Year Roadmap" — HOW-IT-WORKS archetype adapted as a quarterly swim-lane roadmap over two years. Create a vector-clean product planning infographic with 8 vertical quarter columns on a left-to-right timeline axis labeled Q1, Q2, Q3, Q4, Year 1, then Q1, Q2, Q3, Q4, Year 2. Use horizontal swim lanes by team with labeled boxes: Product Team, Platform Team, API Team, Web App Team, Mobile Team, Data Team, Security Team. In each lane, render feature cards / rounded pills placed in the appropriate quarter cells, each with a small icon, a realistic feature name, and a one-line role description in English. Add sharp status indicators on every card: Planned, In Progress, Shipped, using consistent badge colors. Suggested realistic feature cards include: Product Team — "Roadmap Review" / "Prioritize quarterly initiatives"; Platform Team — "CI Pipeline Upgrade" / "Faster build and deploy workflow"; API Team — "REST Pagination" / "Stable list endpoint performance"; Web App Team — "Dashboard Filters" / "Improve reporting navigation"; Mobile Team — "Offline Cache" / "Basic read access without network"; Data Team — "Event Schema Cleanup" / "Standardize analytics payloads"; Security Team — "SSO Rollout" / "Centralize team authentication"; plus later-quarter items such as "Audit Log Export", "Search Relevance Tuning", "Usage Metrics v2", "Background Job Retry", "Role-Based Access", "Release Notes Panel", "Billing Webhooks", "Data Retention Controls", "Localization Foundations", "Incident Timeline View", "API Rate Limits", "Performance Budget Alerts". Connect related cards across quarters with thin arrows showing progression or dependency, with short English labels such as "discovery", "implementation", "beta feedback", "general availability", "dependency", "handoff". Include labeled boxes for roadmap structure elements: Timeline Axis, Quarter Columns, Team Swim Lanes, Feature Cards, Status Legend, Dependency Arrows, Milestone Markers. Each structural box should include an icon, a canonical English name, and a one-line role description. Add a numbered legend 1-7 explaining the planning lifecycle in English: 1. Define team swim lanes, 2. Map work to quarter columns, 3. Mark planned initiatives, 4. Track in-progress delivery, 5. Show shipped outcomes, 6. Link dependencies and milestones, 7. Review roadmap across two years. Visual style: sketchnote-inspired editorial developer-blog illustration with hand-drawn accents but clean alignment, isometric or flat tech-diagram style, vector-clean infographic layout. Palette: tech blue + gradient with light background, blue-to-cyan gradients, subtle violet accents, dark navy text, crisp status badges, soft grid lines, confident product-planning mood. Keep quarter / horizon labels accurate for a two-year span and ensure realistic roadmap scope with no overpromising. 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.