Hi Community,
I’m currently involved in the design phase of a global Source-to-Pay (S2P) program on ServiceNow for a multinational organization with a footprint across ~70–100 countries.
Scope includes:
- Sourcing & Procurement Operations (SPO)
- Supplier Lifecycle Operations (SLO)
- (APO potentially in future phases)
The current ERP landscape includes systems like Oracle Fusion and Sage across different regions.
We are entering an 8-week design phase focused on: (Do you think 8 week is enough?)
- Defining a global process model (To-Be)
- Identifying regional/local variations
- Establishing a scalable rollout strategy
I would appreciate insights from anyone who has led or supported similar large-scale, multi-country ServiceNow S2P (or adjacent workflows like HRSD/CSM/ITSM) programs.
Specifically looking for guidance on:
- Global vs Regional Design Approach
- How do you structure global template vs regional variations?
- What % standardization vs localization have you seen work in practice?
- Anchor Country Selection
- How do you identify anchor countries for global design?
- Do you base it on:
- Process maturity?
- Volume?
- System landscape?
- Geography?
- Country Grouping Strategy
- Have you grouped countries by region, system, or operating model?
- Any proven frameworks?
- Design Phase Execution
- For large programs, do you:
- Start with 2–3 anchor countries?
- Run parallel regional discovery?
- Or define global first, then validate regionally?
- Lessons Learned / Pitfalls
- What are common mistakes in global S2P design on ServiceNow?
- Anything you would do differently?
Appreciate any practical insights, especially from real implementations.
Thanks in advance!
