Creating an Agile Roadmap Timeline Infographic

Tech architecture infographic titled "Creating an Agile Roadmap" using HOW-IT-WORKS adapted as a milestone timeline for product planning. Show a consultant-deck roadmap diagram with a horizontal timeline axis split into three horizons: 1 Year, 3 Year, 5 Year, with accurate quarter markers in the near-term section and broader horizon bands for mid-term and long-term planning. Include swim lanes by team where applicable, such as Product, Engineering, Design, Data, and Go-to-Market. Render labeled BOXES and feature cards as roadmap components connected by ARROWS showing progression, dependency, and feedback direction across the timeline.

Core boxes/components to include:
- Strategic Goals box with icon, name "Strategic Goals", role description "Defines business outcomes and prioritization criteria"
- Customer Insights box with icon, name "Customer Insights", role description "Supplies research, feedback, and usage signals"
- Opportunity Backlog box with icon, name "Opportunity Backlog", role description "Collects validated problems and improvement themes"
- Prioritization Framework box with icon, name "Prioritization Framework", role description "Ranks initiatives by value, effort, and risk"
- Delivery Teams box with icon, name "Delivery Teams", role description "Execute milestones across cross-functional lanes"
- Release Feedback box with icon, name "Release Feedback", role description "Measures outcomes and informs roadmap updates"

Place realistic feature milestone cards inside team swim lanes, each as labeled boxes with icon, English feature name, one-line role description, and sharp status pill. Use realistic non-hyped feature names such as:
- "Roadmap Template Setup" — "Establishes planning structure and review cadence" — status: Planned
- "Stakeholder Alignment Review" — "Confirms goals, dependencies, and ownership" — status: In Progress
- "Customer Feedback Intake" — "Captures recurring requests and pain points" — status: Shipped
- "Quarterly Prioritization Cycle" — "Refreshes roadmap based on current evidence" — status: Planned
- "Delivery Metrics Dashboard" — "Tracks throughput, lead time, and outcomes" — status: In Progress
- "Cross-Team Dependency Mapping" — "Highlights sequencing and shared constraints" — status: Planned
- "Annual Theme Planning" — "Groups initiatives into strategic outcome areas" — status: Shipped
- "Outcome Review Process" — "Evaluates shipped work against intended impact" — status: Planned

Use ARROWS with short English labels describing flow between boxes and milestones, such as:
- "research inputs"
- "prioritized themes"
- "team plans"
- "delivery milestones"
- "usage metrics"
- "roadmap updates"
- "dependency"
- "quarterly review"

Add a numbered legend (1-7) walking through the roadmap lifecycle in English:
1. Gather customer feedback and business goals
2. Define themes and opportunities for the roadmap
3. Prioritize initiatives by value, effort, and timing
4. Assign work across team swim lanes and quarters
5. Track milestones by status: Planned, In Progress, Shipped
6. Review delivery outcomes and operational metrics
7. Update the roadmap across 1-year, 3-year, and 5-year horizons

Visual requirements: milestone timeline layout, quarter columns in the 1-year horizon, broader horizon blocks for 3-year and 5-year outlook, consultant presentation aesthetic, warm earth palette with clay, sand, terracotta, olive, muted brown, and cream tones, sharp status indicators, crisp typography, subtle gridlines, clean spacing, executive-friendly structure, balanced hierarchy, polished enterprise strategy mood. Use 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.