A phased approach to ServiceNow SPM implementation.
ServiceNow's recommended sequence shows SPM as a maturity journey: establish the foundations, add planning and governance progressively, and deepen capabilities as the organisation is ready.
Why sequence matters.
An SPM implementation can span demand, projects, financials, resources, planning, collaboration, agile delivery, integrations and AI. Implementing all of that at once is rarely the same as creating value quickly.
ServiceNow's Australia guidance uses a Foundation → Crawl → Walk → Run → Fly maturity model. We use the underlying principle rather than reproducing ServiceNow's visual: start with the capabilities that create dependable information and operating discipline, then build on them.
The phases are not separate products.
Capabilities introduced early can become more sophisticated later. Resource Management is a good example: ServiceNow places a basic form of resource capability in Foundation and broader Resource Management later in the maturity path. Enterprise Agile Planning and Now Assist are likewise shown at different levels of maturity.
The implication is important: maturity is not simply the number of modules switched on. It is also the quality of data, process, governance, adoption and connection between capabilities.
Use the roadmap as a planning aid.
The right implementation sequence depends on the starting point. Existing project governance, resource data, financial processes, portfolio maturity, delivery tooling and integration requirements can all change what should come first.