
ServiceNow cuts 287 California roles as it hires for AI skills
A 287-person California reduction in force takes effect on September 28, and ServiceNow says it will end 2026 with the headcount it started with.
Topic coverage
Source-linked reporting and practical patterns organized around a shared enterprise applications question.

A 287-person California reduction in force takes effect on September 28, and ServiceNow says it will end 2026 with the headcount it started with.

Cantor Fitzgerald raised its ServiceNow target on client checks describing tier moves for Now Assist. The renewal problem that creates is yours.

Raleigh's CIO says ServiceNow AI saved a month of time. The number only means something once you know whose month, measured how.

An accurate CMDB is a precondition, not a benefit. Discovery repays the spend only where change, triage, licence position or security response consume the data.

An employee who fails at self-service tries again tomorrow. A customer may just leave, and may hold a contract saying you owe them an answer.

A customer portal collects a page from every team that asks. Decide who owns the scope, where the logic lives and what anonymous visitors see.

Domain separation partitions ServiceNow data for a handful of real reasons and constrains the platform for years. Scoped apps and access control usually fit better.

One CMDB for ServiceNow CSM and ITSM saves real work until permissions, reconciliation and asset ownership pull the two populations apart.

Most teams buying ServiceNow need ticket capture, routing, knowledge and reporting. A real CMDB, cross-team SLAs and non-IT workflow are what justify the platform.

Serving external customers from the ServiceNow incident table holds up until an outage, when the internal clock and the contract clock stop agreeing.

When ITSM and security both claim the CMDB, reconciliation becomes everyone's second job, and nobody notices a stale record until a remediation deadline depends on it.

A ledger of what you skipped and a five-line summary do more for ServiceNow release review than reading the whole document ever will.

A catalog entry for a Power Platform flow should name who gets paged, what to check first, and who can switch it off. The design document stays where it is.

A blank escalation reason usually marks a case that skipped its normal owner. Name what the blank means and route it before you make the field required.

Most CMDBs are partly wrong, and the workarounds cost more than the errors. Where the effort pays: identification, relationships, precedence, retirement.

An account hierarchy records a commercial relationship. Case visibility is a separate decision, and the hierarchy setting is the one that leaks a child's cases.

Phase one lands or stalls on four calls made before build: real scope, named data owners, whether the CMDB is in, and a counted integration list.

Writing the two week handover runbook exposes every job only you can run, and the page telling your stand-in what not to attempt is the one that saves you.

Hypercare catches the loud failures. Notification rules that never fire, one-person assignment groups and SLA clocks on the wrong schedule wait for week two.

ServiceNow's ITSM products are applications on a platform. App Engine lets you build your own there, inheriting the workflow, approvals and catalog you already run.

Most CABs read thirty changes aloud and approve them in forty minutes. Here is a method that puts the meeting's attention on the two that could hurt you.

A practical method for keeping ServiceNow access requests auditable long after the project that justified them ends.

An agent assessing change impact trusts every CI and relationship it finds. Fix class ownership and identification rules before it goes live.

When a shared Power Automate flow fails, find the work that stopped, name one lead, and write the ServiceNow record before anyone resubmits a run.