Assign business ownership and technical service ownership before implementation starts, then estimate capacity from the work queue. An employer-posted State Street Archer support role with a June 2026 closing date included production support, integrations, access management, monitoring and incident/change records; it is a useful example of operational duties, not a staffing benchmark or a currently open vacancy. Employer posting. (statestreet.wd1.myworkdayjobs.com)
Our proposed ownership model is:
| Role | Accountable for |
|---|---|
| Executive sponsor | Outcomes, priorities and funding |
| Business product owner | Process design, backlog and stakeholder decisions |
| Data/content owners | Taxonomies, control libraries, obligations and record quality |
| Platform administrator | Configuration, permissions, reports and release execution |
| Technical service owner | Integrations, monitoring, incidents and technical dependencies |
| Assurance owners | Testing methods, conclusions and evidence expectations |
Estimate recurring workload using actual task volumes: onboarding, permissions, reassignment, failed jobs, content changes, report requests, training and releases. Add capacity for absence and peak reporting periods rather than assuming the primary administrator is always available.
Require the buyer’s administrator to perform a change and diagnose a failed integration during handover. Supplier-led learning can supplement this: ServiceNow publishes implementation and configuration tutorial series, but training availability is not evidence that your team has operational capacity. Tutorial index. (servicenow.com)
Sources cited on this page
- Employer posting ↗statestreet.wd1.myworkdayjobs.com
- statestreet.wd1.myworkdayjobs.com ↗statestreet.wd1.myworkdayjobs.com
- Tutorial index ↗www.servicenow.com