Gantt Spreadsheet Product Roadmap Infographic

Tech architecture infographic titled "Gantt Spreadsheet Product Roadmap". HOW-IT-WORKS archetype adapted into a product roadmap board with a kanban-style layout: three main vertical columns labeled Now, Next, Done, combined with a one-year timeline axis spanning Q1, Q2, Q3, Q4 across the top. Editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Consultant deck aesthetic, warm earth palette with terracotta, sand, clay, olive, warm beige, muted brown, soft cream background, sharp high-contrast status pills.

Show a structured roadmap for a spreadsheet-based Gantt chart product using labeled BOXES as feature cards, arranged inside swim lanes by team where applicable: Core Spreadsheet, Timeline & Planning, Collaboration, Import/Export, Admin & Reliability. Each feature card is a clean rectangular box with a small icon, a feature name in English, and a one-line role description in English. Include status indicators as sharp pills: Planned, In Progress, Shipped. Use realistic, credible feature names only.

Feature card examples to render as boxes:
- Dependency Columns — "Track predecessor and successor task links"
- Drag-to-Resize Bars — "Adjust task duration directly on the timeline"
- Baseline View — "Compare planned dates against current schedule"
- Conditional Cell Formatting — "Highlight overdue or blocked tasks automatically"
- CSV Import — "Load task tables from exported spreadsheet files"
- Excel Export — "Download timeline data for offline sharing"
- Comment Threads — "Discuss tasks with contextual replies"
- Assignee Filter — "View schedule by owner or team"
- Milestone Markers — "Pin key delivery dates on the chart"
- Quarter Zoom — "Switch between month and quarter timeline density"
- Permissions Matrix — "Control who can edit sheets and timelines"
- Audit History — "Review schedule edits and field changes"
- Template Library — "Start from project planning presets"
- Progress Rollup — "Aggregate completion across grouped tasks"
- Freeze Header Row — "Keep column labels visible while scrolling"

Connect related boxes with ARROWS showing roadmap progression and dependency flow between columns, for example Done -> Now -> Next, and cross-team arrows where relevant. Every arrow must include a short English label describing what moves across the roadmap, such as "shipped capability", "active development", "planned dependency", "timeline data", "user feedback", "export format".

Include quarter columns / timeline axis accurately aligned to Q1, Q2, Q3, Q4, with feature cards spanning the appropriate quarter ranges visually like mini Gantt bars behind or attached to each card. Maintain clear Now / Next / Done grouping while still showing annual timing. Status labels must render sharp and legible. Quarter and horizon labels must be accurate.

Add a numbered legend (1-7) in English explaining the lifecycle of roadmap delivery:
1. Ideas enter the backlog from customer planning needs
2. Validated items move into Next for upcoming quarter planning
3. Scoped work enters Now when active implementation starts
4. Core spreadsheet and timeline features ship incrementally
5. Collaboration and import/export items follow dependency order
6. Completed work moves into Done with shipped status
7. Teams review quarterly progress and rebalance the roadmap

Visual mood: polished consultant presentation slide, strategic planning board, executive-friendly, credible SaaS product planning, warm and structured rather than playful. Use subtle gridlines, tidy spacing, neat swim lanes, crisp typography, soft shadows, clear iconography, and balanced information density. Avoid exaggerated claims and avoid fantasy UI. The target search intent should be visually represented as a roadmap for a gantt spreadsheet product, without rendering the search phrase as on-image text.

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.