Designing an HR Service in ServiceNow is not actually about building a form.
After working with HR organizations on HR Service Delivery initiatives, I've repeatedly seen the same pattern: teams spend significant time on configuration and catalog design, but far less time on the decisions that determine whether a service succeeds after go-live.
The paper focuses on the work that happens before and after configuration, including:
✅ How to structure HR Services using the HRSD COE data model
✅ Choosing the right fulfillment model (self-service, agent-led, or hybrid)
✅ Running effective HR Service design workshops
✅ Requirements gathering and end-to-end process mapping
✅ Organizational Change Management (OCM) for HRSD rollouts
✅ Knowledge article strategy and governance
✅ Metrics that actually matter after launch
✅ Service lifecycle management, updates, and retirement criteria
✅ Governance models that prevent long-term platform sprawl
One of the central themes of the paper is that an HR Service isn't simply a catalog item. It's the visible outcome of decisions around ownership, security, knowledge, fulfillment, measurement, change management, and governance.
In my experience, organizations rarely struggle because they cannot configure HRSD. They struggle because those decisions were never made explicitly or were made once and never revisited.
If you're an HR Service Owner, HR Operations Leader, COE Lead, HRSD Architect, or implementation practitioner, I hope this serves as a practical guide you can use in workshops, service reviews, and governance discussions.
