Roadmap Visualisierung als Tech-Infografik mit Timeline

Tech architecture infographic titled "Roadmap Visualization" using HOW-IT-WORKS adapted as a product roadmap timeline infographic. Create a minimalist Swiss editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Show a two-year quarterly roadmap with 8 clear quarter columns on a horizontal timeline axis: Q1, Q2, Q3, Q4 for Year 1 and Q1, Q2, Q3, Q4 for Year 2. Use swim lanes by team with labeled boxes and feature cards: Product Team, Design Team, Frontend Team, Backend Team, Data Team, Platform Team. Each lane contains compact feature-card boxes or pills with a small status indicator icon and sharp status label: Planned, In Progress, Shipped. Use realistic, non-hype feature names for a roadmap visualization product such as: Timeline View MVP, Quarter Filter, Milestone Markers, CSV Import, Team Swimlanes, Status Color Rules, Export to PNG, Export to PDF, Public Share Link, Role Permissions, Dependency Lines, Search and Filter, Comment Threads, Audit Log, API Read Access, API Write Access, Template Library, Accessibility Pass, Performance Improvements, Mobile Layout Refinement, Dark Mode, Localization Support, Usage Analytics, Admin Controls. Arrange cards under the appropriate quarter with accurate spacing and bullet-list rhythm inside each quarter column. Include labeled BOXES for supporting roadmap system components connected by ARROWS showing data direction so it still reads as a tech architecture / how-it-works infographic: User Browser box with icon, name "Browser UI", role description "View and edit roadmap plans"; Application Service box with icon, name "Roadmap API", role description "Serves roadmap data and updates"; Database box with icon, name "Roadmap Database", role description "Stores quarters, teams and feature status"; Asset Export box with icon, name "Export Service", role description "Generates PNG and PDF outputs"; Notification box with icon, name "Activity Feed", role description "Tracks roadmap changes and comments". Connect them with arrows and short English labels: "HTTPS request", "JSON roadmap data", "SELECT roadmap rows", "UPDATE feature status", "render export job", "activity event". Add subtle numbered callouts 1-7 walking through the lifecycle in English: 1 User opens roadmap view, 2 Browser requests quarter data, 3 API loads roadmap items, 4 Database returns team and status records, 5 UI renders quarter columns and swim lanes, 6 User updates a feature card or status, 7 Export or share output is generated. Visual style: strict grid, strong alignment, large negative space, high-contrast modern palette with black, white, electric blue, vivid orange, cool gray, and one accent green for shipped state; minimalist Swiss typography, crisp lines, thin dividers, flat vector iconography, precise quarter labels, clean bullets, no decorative clutter. Mood: professional, product-strategy focused, analytical, modern, calm, credible. Ensure status labels are sharp and legible, quarter horizon labels are accurate, and swim lanes clearly separate teams. 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.