Technology Roadmap PPT Dark Dashboard Infographic

Tech architecture infographic titled "Technology Roadmap PPT" using HOW-IT-WORKS archetype, redesigned as a now / next / later roadmap board with a three-horizon timeline (1 year / 3 year / 5 year). Show a structured dark dashboard infographic with clear labeled BOXES and feature-card components connected by subtle ARROWS that indicate progression and dependency across horizons. Include swim lanes by team where applicable, quarter columns for near-term planning, and a timeline axis that expands from detailed quarters in Now to broader horizon markers in Next and Later.

Main layout:
- Three large horizontal roadmap zones: NOW, NEXT, LATER
- Timeline axis beneath or above: Year 1 with Q1 Q2 Q3 Q4, Year 3 horizon marker, Year 5 horizon marker
- Optional swim lanes: Platform Team, Data Team, Application Team, Security Team
- Each roadmap item rendered as a labeled BOX / card / pill with an icon, a realistic feature name, and a one-line role description in English
- Status indicators on each card: Planned, In Progress, Shipped
- Thin ARROWS between related cards to show evolution, dependency, rollout sequence, or handoff
- Each arrow must have a short English label such as "dependency", "beta rollout", "API upgrade", "data sync", "policy update", "user feedback"

Use these example roadmap boxes with icons and one-line descriptions:
- Presentation Template System — Standardized slide components for roadmap communication
- Theme Token Library — Shared design variables for consistent deck styling
- Collaboration Comments — Team feedback workflow for slide review
- Export to PDF — Reliable presentation export for stakeholder sharing
- Version History — Track edits and restore earlier roadmap drafts
- Chart Component Refresh — Updated visual blocks for timeline and status views
- Slide Performance Tuning — Faster editing and rendering in large decks
- Analytics Summary Widget — Snapshot of roadmap progress and adoption signals
- Data Connector Sync — Pull roadmap inputs from planning tools
- Governance Review Flow — Approval checkpoints for roadmap publication
- Accessibility Contrast Pass — Improve readability and compliance in slides
- AI Layout Suggestions — Assist arrangement of roadmap sections and cards
- Template Marketplace — Reusable roadmap layouts for different teams
- Multi-Team Portfolio View — Aggregate roadmap across departments
- Scenario Planning Layer — Compare alternate roadmap assumptions
- Offline Editing Support — Continue work without network connection

Flow and arrows should remain technically coherent for a product-process infographic:
- Input sources feed roadmap planning cards
- Planning cards move through review and publication stages
- Shared systems support collaboration, export, analytics, and governance
- Longer-term items branch from completed foundational items
- Use short accurate arrow labels like "planning input", "review notes", "approved update", "published deck", "usage metrics", "future dependency"

Add a numbered legend (1-7) explaining the lifecycle in English:
1. Teams collect roadmap inputs and priorities
2. Near-term features are scheduled into quarter-based planning
3. Active work items move through in-progress delivery
4. Completed capabilities are marked shipped and reused
5. Shared platform improvements enable broader roadmap views
6. Mid-term initiatives build on stable foundation features
7. Long-term concepts remain planned pending validation and capacity

Visual style:
- Dark dashboard UI mood
- Pastel soft palette with muted lavender, mint, soft cyan, peach, pale yellow, and desaturated pink accents over charcoal or deep navy background
- Sharp status labels, crisp grid, subtle glow, clean separators, soft shadows
- Editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout
- Professional, realistic, product-management oriented, polished PPT-ready composition
- No exaggerated futuristic claims, use credible enterprise-software roadmap content
- Ensure quarter labels and horizon labels are accurate and visually distinct
- Emphasize card hierarchy, timeline readability, and progression from Now to Next to Later

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.