Roadmap PowerPoint Kanban Infographic for Next Quarter

Tech architecture infographic titled "Roadmap PowerPoint" using HOW-IT-WORKS archetype, adapted as a kanban-style product roadmap board for the next quarter (next 3 months). Create a vector-clean editorial developer-blog illustration showing a structured roadmap planning system with labeled boxes, grouped into 3 primary columns: NOW, NEXT, DONE, plus a subtle horizontal timeline axis covering Month 1, Month 2, Month 3. Add swim lanes by team where applicable, such as Product Team, Design Team, Engineering Team, GTM Team. Each roadmap card must be rendered as a labeled box with an icon, a realistic feature name, and a one-line role description in English. Include status pills on cards with sharp readable labels: Planned, In Progress, Shipped. Use arrows to show lifecycle movement of work items from planning to delivery, with short English labels on arrows such as "prioritized item", "design spec", "implementation", "QA passed", "released deck". Include supporting system-style boxes around the board to make it a technical how-it-works infographic: Backlog, Prioritization, Design Review, Development, QA Check, Release, Stakeholder Feedback. Each supporting box must have an icon, canonical English name, and one-line English role description. Show arrows connecting these boxes into the kanban board to explain flow direction. Add a numbered legend from 1 to 7 in English walking through the roadmap lifecycle: 1 Capture ideas in backlog, 2 Prioritize realistic quarter goals, 3 Move active items to Now, 4 Prepare upcoming work in Next, 5 Track cross-team progress, 6 Mark completed items as Done, 7 Review outcomes and feed learning back into backlog. Use realistic feature names for a roadmap presentation product, such as "Template Refresh", "Slide Library Cleanup", "Milestone View", "Status Badge Update", "Team Swimlane Layout", "Export Polish", "Quarter Planning Sync", avoiding hype or overpromising. Ensure quarter and horizon labels are accurate for a next-quarter roadmap. Visual style: warm boutique, polished and premium, navy base with warm accent palette such as terracotta, muted gold, cream, and soft coral, balanced contrast, elegant spacing, crisp card edges, subtle shadows, modern flat or lightly isometric diagram styling. Include 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.