Projekt Diagramm Excel als Roadmap-Infografik

Tech architecture infographic titled "Project Diagram Excel" using HOW-IT-WORKS archetype adapted as a kanban-style product roadmap board for a two-year planning horizon. Create a consultant-deck roadmap infographic with three primary vertical sections: NOW, NEXT, DONE, combined with a clear quarter-based timeline axis spanning 8 quarters across two years (Q1 to Q4, Year 1; Q1 to Q4, Year 2). Add optional horizontal swim lanes by team such as Core Templates Team, Data & Reporting Team, Collaboration Team, and UX Team where applicable. Render labeled boxes as feature cards and roadmap modules, each connected with subtle arrows showing progression from planned to in-progress to shipped over time. Every feature card must include a small icon, a canonical English feature name, and a one-line English role description. Include sharp status pills: Planned, In Progress, Shipped. Use realistic, non-hyped feature names suitable for Excel-based project diagram tooling, such as Gantt Chart Template, Milestone Tracker, Task Dependency View, Resource Allocation Sheet, Conditional Formatting Rules, Import from CSV, Timeline Auto-Update, Print-Ready Dashboard, Team Status Summary, Risk Register Tab, Baseline Comparison, and Filterable Project Portfolio View. Add arrows with short English labels describing transitions such as "Backlog item", "Design spec", "Template update", "User feedback", "Released feature", and "Spreadsheet workflow". Structure the infographic so that feature cards appear placed in accurate quarter columns and move logically across NOW, NEXT, and DONE lanes over the two-year horizon. Include secondary labeled boxes for supporting components such as User Needs, Template Library, Excel Workbook, Formula Logic, Data Validation, Reporting View, and Shared File Access, each with icon, English label, and one-line role description, connected by arrows to show how roadmap items support the product evolution. Add a numbered legend from 1 to 7 in English explaining the roadmap lifecycle: 1. Collect user needs, 2. Prioritize backlog, 3. Plan quarterly scope, 4. Build workbook features, 5. Validate spreadsheet logic, 6. Release usable templates, 7. Review adoption and feedback. Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Mood: polished consultant presentation, structured, strategic, credible, calm. Color palette: warm earth tones with clay, sand, terracotta, muted brown, soft olive accents, and off-white background; use darker earth tones for shipped, medium warm tones for in progress, lighter sandy tones for planned. Ensure crisp grid alignment, clean quarter dividers, timeline markers, subtle shadows, and presentation-ready spacing. Emphasize roadmap readability, accurate quarter labeling, distinct swim lanes, and clear status rendering. 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.