--- title: "ServiceNow Four Zeros: adoption blueprints for autonomous IT" description: "ServiceNow's \"Four Zeros,\" posted October 19, 2026, is not a product but a guide to ordering ITSM, ITOM, and CMDB. The four goals, the phases and gates, and open questions." url: https://udon-dev.com/en/notes/servicenow-four-zeros-autonomous-it/ lang: en published: 2026-10-21 topic: [servicenow] tags: ["servicenow", "itsm", "itom", "cmdb", "ai-agent"] --- # ServiceNow Four Zeros: adoption blueprints for autonomous IT - Four Zeros is a set of four goals (drive manual support work, service outages, change friction, and compliance gaps toward zero) plus adoption blueprints for getting there. It is not a new product or license announcement - All four blueprints have six phases, with a gate after phase 3 and another at the end. Three of the four put the CMDB in order before the AI agents - The post doesn't explain how it relates to the similarly named Adoption Blueprints feature in Admin Center (Tokyo and later). Pricing, Japanese-language material, and whether it will appear in Admin Center are unknown On October 19, 2026, ServiceNow published "[Introducing the Four Zeros](https://www.servicenow.com/community/autonomous-it-blog/introducing-the-four-zeros-adoption-blueprints-for-autonomous/ba-p/3611878)" on the Autonomous IT blog in its official community. The title says "Adoption Blueprints," but this isn't a new product or an Admin Center feature. It's adoption guidance: for each of four goals, it lays out the order in which to combine ITSM, ITOM, and CMDB. The text is short and the concrete steps live in the slide images embedded in the post, so this article reads those images too. ## The four "zeros" and who owns them The post lists the outcomes an IT leader tracks as an "Autonomous IT Scorecard" and calls the first four "Autonomous Service Operations." Each outcome has an assigned owner role. | Zero | Owner | How the post describes it | |---|---|---| | Zero Touch Support (ZTS) | Service desk leader | Issues are resolved before anyone picks up a ticket. Routine requests and known fixes run automatically | | Zero Service Outages (ZSO) | Operations leader | Correlated events and impact scope let you act early, before a signal becomes an incident | | Zero Friction Change (ZFC) | Change and release leader | Risk is understood up front, so changes ship without stalling on approvals | | Zero Compliance Gaps (ZCG) | Operations and governance leader | The CMDB is accurate and every action leaves a record, so an audit only confirms what you already know | Below the scorecard image, a note says the projected outcomes are illustrative, not guaranteed. It's best to read "zero" as the name of a direction, not a promise that you'll get there. ## Adoption stalls at the seams between products According to the post, adoption stalls because products get rolled out one at a time and nobody designs the handoffs between them. ITOM spots anomalies through events and alerts, CMDB shows what the service depends on, and ITSM routes the work to the right people and changes and keeps the record. Running those three as one operation is what the post calls "ServiceOps," and the blueprints work backward from the outcome to map a path across those products. （図: An image from the ServiceNow Community post. Under the heading "The journey to Autonomous Service Operations," four boxes sit side by side: Zero Touch Support, Zero Service Outages, Zero Friction Change, and Zero Compliance Gaps. Below them are capability names such as L1 SD AI Specialist, DEX, Major Incident Mgmt., Change Mgmt., AIOps AI Specialist, SRE AI Agent, Service Observability, and Cert Mgmt., with an arrow along the bottom reading "From insights to Automation to Autonomy"） Source: [Introducing the Four Zeros (ServiceNow Community)](https://www.servicenow.com/community/autonomous-it-blog/introducing-the-four-zeros-adoption-blueprints-for-autonomous/ba-p/3611878) In this image, capabilities such as the L1 service desk AI specialist, the AIOps AI specialist, the SRE AI agent, change management, and certificate management sit below the four zeros. The image doesn't show which capability belongs to which zero. The [PDF](https://www.servicenow.com/community/s/cgfwn76974/attachments/cgfwn76974/autonomous-it-blog/5/1/Zeros%20Blueprints.20261020.pdf) attached to the post (12 pages) has a page listing the capabilities for each zero. For Zero Service Outages, for example, it lists the AIOps AI specialist, Event Management, Service Mapping, the SRE AI agent, and certificate management. The phrase along the bottom, "from Insight, through Automation, to Autonomy," uses the same words as the approach laid out in a February blog post. ### Continuing from the February and April posts On February 11, 2026, ServiceNow published [journey maps for two paths, Zero Touch and Zero Service Outages](https://www.servicenow.com/community/itsm-blog/autonomous-it-zero-touch-support-and-zero-service-outage-journey/ba-p/3487082). Customer administrators, implementation partners, and product owners built them together. They have three stages: Insight (turn on the core capabilities and make the environment visible and measurable), Automation (use AI and automation to cut manual work), and Autonomy (AI acts on its own within guardrails while people supervise). The same post says skipping steps leads to failure. Its examples: with thin knowledge, a virtual agent can't reduce tickets; with an incomplete CMDB, you can't act on AIOps alerts; and with messy incident data, change risk scores aren't reliable. An [April 20 post](https://www.servicenow.com/community/itsm-blog/a-new-servicenow-era-autonomous-it/ba-p/3528965) introduced "Autonomous IT Academy," a biweekly webinar series run by the product teams. Each session is meant to cover the adoption order, the prerequisite capabilities and licenses, and recommended KPIs. Four Zeros reads as those two paths plus two more, change management and compliance, rearranged as outcomes for each owner. ## All four blueprints use six phases and gates The four blueprints embedded in the post each have six phases. A "Gate to phase 4" comes after phase 3, and the end has a condition either for expanding to the next service or theme or for moving to production. Three of them (Zero Touch Support, Zero Service Outages, and Zero Compliance Gaps) start phase 1 by choosing one or two use cases and their owners, then installing plugins and AI skills. Only Zero Friction Change starts phase 1 with an inventory of 50 to 100 production services. （図: An image from the ServiceNow Community post. The heading reads "Zero Service Outages Blueprint" with the subtitle "ServiceOps (ITOM-ITSM-CMDB)." The top row shows the steps for phases 1 to 3 (Define, Prep, Discover, Map & Populate / Connection and Correlation / Add Context and Activate Specialist), and the bottom row shows phases 4 to 6 (Incident Process Refinement / Major Incident Process / Observation and Refinement). The right end of each row lists the conditions for moving to the next phase） Source: [Introducing the Four Zeros (ServiceNow Community)](https://www.servicenow.com/community/autonomous-it-blog/introducing-the-four-zeros-adoption-blueprints-for-autonomous/ba-p/3611878) In the Zero Service Outages image, you first populate the CMDB for the target scope with Discovery or agents, turn events into alerts with Event Management connectors, and check alert grouping. The gate to phase 4: for one service, CI and event ingestion are complete, knowledge and change records exist, and the AIOps specialist is running. The final gate lists values such as false grouping under 15%, false escalations under 20%, and triage accuracy over 75%. The order is to measure the quality of the AI's output in numbers before widening what the AI is trusted with. ## Change management runs in parallel before automating 80% Of the four, Zero Friction Change has the most specific numbers. （図: An image from the ServiceNow Community post. The heading reads "Zero Friction Change Blueprint" with the subtitle "Service-Centric CMDB + Change Orchestrator + Approval Automation." Six phases run from Phase 1, Foundation, through Change Orchestrator, AI Assessment, Validation, Automation, and Production. Along the bottom: "Gate to Production: AI accuracy ≥ manual review, zero critical failures, 90% of routine changes automated"） Source: [Introducing the Four Zeros (ServiceNow Community)](https://www.servicenow.com/community/autonomous-it-blog/introducing-the-four-zeros-adoption-blueprints-for-autonomous/ba-p/3611878) The flow in the image: 1. Inventory 50 to 100 production services and build a service-centric CMDB and simplified change models. The image calls this "non-negotiable" 2. Install Change Orchestrator and connect four subagents for preparation, scheduling, assessment, and quality checks 3. Train the risk model on 12 months or more of change and incident history 4. Run AI decisions side by side with human review and compare accuracy and speed. Changes keep flowing during this period 5. Low-risk changes (80%) are fully automated, medium-risk changes (15%) get a human check, and high-risk changes (5%) get human review 6. Move to production and improve while watching metrics and SLAs The gate to production: AI accuracy at or above human review, zero critical failures, and 90% of routine changes automated. The image also lists expected outcomes, such as incidents dropping from 12 to 8 per month and rollbacks from 8% to 4.8%. This image carries no disclaimer, but it makes sense to treat these the same way as the scorecard's "illustrative, not guaranteed" figures: a rough guide until you measure your own. The Zero Compliance Gaps image also starts phase 1 by measuring CMDB health and cleaning up duplicate CIs. It says that no compliance answer can be better than the quality of the CIs behind it. Every blueprint except Zero Touch Support puts the CMDB in order before the AI agents. Zero Touch Support starts with filling knowledge gaps and measuring device health (DEX). ## How this differs from Adoption Blueprints in Admin Center The name invites confusion with "Adoption Blueprints" in Admin Center. That's a built-in feature on Tokyo and later instances. According to a [2024 community post](https://www.servicenow.com/community/admin-experience-blogs/adoption-blueprints/ba-p/3131840), it offers six plans, such as "reduce incidents without service disruption." According to the [Zurich documentation](https://www.servicenow.com/docs/r/7LhbZn3yz3Q58qhjZoU9iQ/FNZzBSo0Cd88ZvNYYfCVeg), you open "All > Admin Center > Adoption Blueprints" with the admin role and pick a goal. The detail page shows how far you've gotten with installing the recommended apps and which app to install next. For now, the Four Zeros blueprints exist only as the post's images and the attached PDF. The post doesn't say whether they'll appear in Admin Center or whether you'll be able to track progress the same way. It only says that more concrete content will be added to the "Best Practice Library" over the coming months. ## Availability of the AI agents in the images The blueprints mention the L1 IT Service Desk AI Specialist, the AIOps specialist, an AI agent that renews certificates, and others. Coverage of Knowledge 2026 in May 2026 reported that the L1 specialist was already generally available. New IT specialists were slated for June ([diginomica](https://diginomica.com/servicenow-knowledge-2026-ai-control-tower-expands-autonomous-workforce-reaches-every-function-and), [ITdaily](https://itdaily.com/news/software/servicenow-rolls-out-ai-specialists-for-it-crm-hr-and-security/)). According to ITdaily, all the specialists run on top of CMDB, Workflow Data Fabric, Context Engine, and AI Control Tower. It also reported that these would be included by default in every product and package starting in April. The L1 specialist is the agent that handles IT requests autonomously, which I also covered in an earlier article, "[What is ServiceNow's \"Flow\"?](/en/notes/servicenow-flow-ai-service-desk/)" In the Zero Touch Support image, the order is to start in "Assist Mode," score responses on 50 to 100 incidents, and move to autonomous mode once quality holds. ## What's still unclear After reading the post and related material, I couldn't find answers to these: - Pricing and required licenses: the April post says the academy covers them, but the Four Zeros post doesn't mention them - Japanese-language material and availability for customers in Japan: I found no Japanese version and no plans for a Japan briefing - Outcomes beyond the first four on the Autonomous IT Scorecard: "the first four" implies more, but the post doesn't say what they are Compared with the February maps, what Four Zeros adds for the first time is the gate values for each phase. They look useful as a yardstick: line them up against your own numbers to see which phase you're in.