Architectural roadmaps differ from product roadmaps. They focus on platform health, capability, and strategic direction.
Components:
1. Current state.
- Where is the architecture today?
- Capabilities, debt, gaps.
2. Future state vision (3-5 years).
- Where should we be?
- Capabilities, scale, alignment.
3. Path between.
- Phases, milestones.
- Sequencing.
- Dependencies.
4. Key initiatives.
- Modernisation.
- New capability adoption.
- Tech debt reduction.
- Compliance initiatives.
5. Investment requirements.
- People (architects, devs, admins).
- Tools (DevOps, monitoring, etc.).
- Salesforce add-ons (Shield, CRM Analytics, Data Cloud).
- Budget over time.
6. Risks and dependencies.
- Salesforce platform direction.
- M&A possibilities.
- Regulatory changes.
7. Success metrics.
- How will we measure progress?
Granularity:
- Year 1 — specific projects, deliverables.
- Year 2 — themes, planned projects.
- Years 3-5 — strategic direction, less detail.
Stakeholder views:
- Technical — detailed for architects, engineers.
- Strategic — for executives, sponsors.
- Tactical — for delivery teams.
Cadence:
- Quarterly review and adjustment.
- Annual major refresh.
- As-needed for major changes (M&A, leadership change).
Communication:
- QBRs with leadership.
- Architects' guild internal.
- Newsletter for broader audience.
- Documentation hub persistent.
Common pitfalls:
- Static roadmap — frozen 18 months ago, ignored.
- Wishlist masquerading as roadmap — no resourcing.
- No stakeholder buy-in — ignored when reality demands.
- Too detailed years out — locks in plans that won't survive.
- No metrics — can't measure progress.
Senior architect insight: roadmaps are conversations, not contracts. They evolve. Discipline is keeping them current and aligned with reality.
The senior framing: the best roadmaps are tools for alignment. They focus stakeholder energy. They expose trade-offs. They provide context for prioritisation decisions.
Without a roadmap, decisions are ad-hoc. With one, they fit a coherent direction.