Long-range roadmaps balance strategic vision with practical sequencing.
Inputs:
- Business strategy — where is the company heading?
- Current state — what's in the org now? Gaps? Tech debt?
- Salesforce platform direction — what's coming from Salesforce?
- Industry / regulatory shifts — emerging compliance needs.
- Stakeholder priorities — what does each leader care about?
Structure:
Year 1: Foundation
- Address critical gaps and tech debt.
- Stand up CoE / governance.
- Implement DX, CI/CD.
- Stabilise existing functionality.
- Quick wins for stakeholder confidence.
Year 2: Expansion
- New cloud / module rollouts (e.g., add Service Cloud to existing Sales Cloud).
- Major integrations.
- Industry Cloud adoption if applicable.
- AI / Einstein features.
- Multi-region / multi-currency.
Year 3: Optimisation & Innovation
- Advanced analytics (CRM Analytics, Data Cloud).
- Agentforce / AI agents.
- Advanced integrations.
- Strategic acquisitions of Salesforce capability (like new Industry Clouds).
- Continued tech debt management.
Quarterly milestones:
Within each year, quarterly themes:
- Q1: foundation work.
- Q2: net-new feature.
- Q3: optimisation.
- Q4: stabilisation, prepare for next year.
Themes vs specific features:
- Themes for years 2-3 (e.g., "Customer 360" or "Service Excellence").
- Specific features only for the next 2-3 quarters.
- The further out, the more theme-based; the closer in, the more specific.
This avoids the trap of committing to specific features 24 months out (priorities will change).
Validation:
- Review with sponsor + leadership monthly during build-out; quarterly during steady state.
- Adjust based on business changes, platform updates, lessons learned.
Reporting:
- Tracker dashboard: roadmap with status (planned / in-flight / delivered / deferred / cancelled).
- Quarterly roadmap review with stakeholders.
- Year-end retrospective of what shipped vs planned.
Common pitfalls:
- Over-detailed multi-year roadmap — locks in plans that don't survive change.
- Wishlist masquerading as roadmap — ambitious plans without sequencing or resourcing.
- No alignment with platform direction — building features Salesforce will ship in 6 months.
- No retrospection — annual roadmap repeats without learning.
Senior consultant insight: roadmaps are conversations, not contracts. They evolve. The discipline is keeping the document fresh, communicated, and aligned with reality.
The most valuable use of a roadmap: it forces leadership conversations. "Are we investing in customer experience or sales productivity?" The roadmap exposes the implicit choices.