AI-generated roadmap slides infographic showing a next-quarter planning board with Now, Next, and Later columns, team swim lanes, feature cards, and dependency arrows. The visual uses a clean blueprint schematic style with deep navy tones, precise grid lines, and sharp status labels for a polished product-planning brand aesthetic.
Re-render this exact infographic with every label, heading and caption translated. We re-use all the original attributes (topic, style, palette, …) and only swap the language. Currently in English.
Tech architecture infographic titled "Roadmap Slides" using HOW-IT-WORKS archetype adapted as a now / next / later planning board for the next quarter (next 3 months). Create a clean board with three main time columns: Now, Next, Later, plus a subtle timeline axis covering Month 1, Month 2, Month 3. Add horizontal swim lanes by team where applicable: Product, Design, Engineering, Marketing. Render labeled boxes / feature cards inside each lane and column, connected with directional arrows to show progression and dependency from Now → Next → Later. Each card must include a small icon, a feature name in realistic product language, and a one-line role description in English. Add compact status pills on each card: Planned, In Progress, Shipped, rendered sharp and legible. Example cards: "Slide Template Refresh — update core presentation layouts for consistency", "Presenter Notes Cleanup — simplify speaker note editing workflow", "Export Performance Pass — reduce large deck export time", "Team Sharing Permissions — improve deck access control", "Comment Resolution Flow — streamline feedback tracking", "Analytics Snapshot Panel — surface basic slide engagement metrics". Use arrows with short English labels such as "design spec", "handoff", "implementation", "QA feedback", "release", "usage data". Include a numbered legend 1-7 explaining the lifecycle in English: 1. Identify current quarter priorities. 2. Place active work in Now. 3. Queue validated follow-up items in Next. 4. Reserve lower-certainty items for Later. 5. Track ownership by team swim lane. 6. Update status as work moves from Planned to In Progress to Shipped. 7. Review dependencies and rebalance scope across the 3-month horizon. Add small supporting metrics labels in English such as "Owner", "Status", "Target Month", "Dependency". Ensure quarter / horizon labels are accurate for a next-3-month view and avoid overpromising feature names. Visual style: blueprint schematic, minimal monochrome palette, white and light gray linework on deep navy / charcoal background, precise grid, thin technical strokes, subtle blueprint notations, crisp modular spacing, calm product-planning mood. 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.
Tell us why this image is inappropriate. A description is required — generic submissions are dismissed. Confirmed reports are resolved within 24 hours.