Sample Project Roadmap Infographic for Next Quarter

Tech architecture infographic titled "Sample Project Roadmap". Use HOW-IT-WORKS archetype adapted into a quarterly swim-lane product roadmap for the next quarter (next 3 months). Create a clean roadmap board with 3 timeline columns labeled Month 1, Month 2, Month 3 and grouped under Q-next / Next Quarter, plus horizontal swim lanes by team: Product, Frontend, Backend, QA/Release. Show labeled BOXES / feature cards in each lane connected by subtle ARROWS where dependencies exist, with data-direction style flow from planning to delivery. Each box must include a small icon, a feature name in canonical English, and a one-line role description in English. Add crisp status pills on each card: Planned, In Progress, Shipped. Use realistic, modest feature names such as User Onboarding Improvements, Dashboard Filters, API Pagination, Error Logging Upgrade, Release Automation, QA Regression Pass, Analytics Events Cleanup, Notification Preferences. Add dependency arrows with short English labels such as "spec ready", "API dependency", "test coverage", "release candidate", "handoff". Include a numbered legend 1-7 explaining the roadmap lifecycle in English: 1 discovery, 2 prioritization, 3 design/spec, 4 implementation, 5 integration, 6 validation, 7 release. Ensure quarter labels and timeline horizon are accurate for a single upcoming quarter spanning 3 months. Visual style: sketchnote meets editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout; hand-drawn annotation energy but polished and readable; sharp status labels; subtle notebook lines, arrows, checkmarks, and planning markers. Color palette: tech blue + gradient, white background, dark navy text, blue/cyan/violet accents, soft card shadows, calm product-planning mood. Add small generic metric or milestone markers like milestone diamonds and release flags, but no vendor branding. 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.