Project Chart Example Kanban Roadmap Infographic

Tech architecture infographic titled "Project Chart Example" using HOW-IT-WORKS archetype, adapted as a kanban-style product roadmap for the next quarter (next 3 months). Create an isometric 3D board with three main labeled columns: Now, Next, Done, plus a subtle 3-month timeline axis across the top with Month 1, Month 2, Month 3. Add horizontal swim lanes by team where applicable, such as Product, Design, Engineering, QA, and Operations. Render labeled boxes and feature cards as structured components connected by directional arrows to show roadmap progression and delivery flow.

Include these component boxes with icons, canonical English names, and one-line English role descriptions:
- Product Backlog — backlog icon — "Prioritized work items for the quarter"
- Now Column — play icon — "Items actively scheduled or in execution"
- Next Column — calendar icon — "Approved upcoming work for the next sprint cycle"
- Done Column — check icon — "Completed and shipped roadmap items"
- Product Team — strategy icon — "Defines scope, priority, and success criteria"
- Design Team — pencil icon — "Prepares UX, UI, and interaction assets"
- Engineering Team — code icon — "Builds features and technical changes"
- QA Team — test icon — "Validates functionality and release quality"
- Operations Team — gear icon — "Supports deployment readiness and rollout"
- Timeline Axis — timeline icon — "Shows quarter planning horizon across 3 months"

Inside the roadmap, add realistic feature cards with compact pill status indicators: Planned, In-Progress, Shipped. Use believable non-hyped feature names such as:
- Update task filters
- Improve export performance
- Add audit log view
- Refine dashboard layout
- Mobile navigation cleanup
- Email notification settings
- Bug fix sprint
- Release checklist automation
- API pagination update
- Accessibility contrast pass
Each card should look like a labeled box with a tiny icon, feature name, and short one-line role description in English.

Connect components and columns with arrows showing accurate work progression. Label arrows in English with short flow text such as:
- "Prioritized items"
- "Scope approved"
- "Design ready"
- "Implementation in progress"
- "Ready for QA"
- "Validated release"
- "Shipped update"
- "Moved to next cycle"
Use arrows from Product Backlog to Now and Next, from team swim lanes into active cards, and from Now to Done where delivery completes.

Add a numbered legend 1-7 in English explaining the lifecycle across the quarter:
1. Product Team prioritizes realistic roadmap items for the next 3 months
2. Approved work is placed into Now or Next based on current capacity
3. Design Team prepares layouts and interaction details for selected items
4. Engineering Team implements items marked In-Progress
5. QA Team verifies acceptance criteria and regression coverage
6. Operations Team supports release readiness and deployment steps
7. Completed items move to Done and are marked Shipped

Ensure quarter and horizon labeling is accurate for a next-quarter view only, not annual planning. Emphasize sharp readable status labels, realistic roadmap planning, clean card hierarchy, and a visual search-intent-friendly layout for "project chart example" without making it look like marketing hype. Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a sage + ivory palette with muted green accents, warm off-white background, subtle shadows, precise grid alignment, polished but practical product-ops mood. 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.