Start with delivery architecture, not just a schedule
A ServiceNow project is not simply a sequence of configuration tasks. It is a coordinated delivery system involving product ownership, platform governance, technical architecture, security, data, integrations, testing, training, and adoption. The project manager’s first job is to make those workstreams visible and connect their dependencies.
Scope must be expressed in platform terms
Generic scope statements are not enough. Define which modules, processes, integrations, data sources, environments, personas, and release outcomes are in scope. Then make exclusions explicit. This prevents every new request from being treated as an implied requirement.
Build governance before the backlog grows
Decide who can approve scope, accept stories, resolve design disputes, and make release decisions. A RACI helps, but governance also needs cadence: backlog refinement, sprint reviews, RAID review, architecture decisions, security checkpoints, and executive escalation paths.
Plan around dependencies, not just dates
The critical path often lives outside configuration: identity and access, MID servers, network rules, data readiness, certificates, security approvals, integrations, and stakeholder availability. Track these as first-class schedule items with owners and required-by dates.
Use the RAID log as a management system
A RAID log is useful only if it drives action. Review it routinely, distinguish risks from active issues, identify decision deadlines, assign accountable owners, and escalate based on impact rather than volume.
Testing and cutover are delivery phases, not closing tasks
UAT, training, deployment readiness, and cutover should be designed while development is still underway. Define entry and exit criteria, defect thresholds, rollback conditions, production validation, hypercare ownership, and communications before the final sprint.
Keep status reporting decision-oriented
Strong status reporting answers four questions: Are we on track? What changed? What could stop us? What decisions are needed? Everything else is supporting detail. Executives need signal, not a transcript of activity.