ServiceNow

Knowledge 2026 Top Takeaways

Seasoned Architect Shares His Learnings


We asked Billy Sprague, Head of Architecture at Astrica,  to share his Top Takeaways from K26. Here is what he said, in no particular order.

1. AI Governance Is the Real Game

The headline out of K26 is not a product launch. It is a structural declaration about where the control plane for enterprise AI is going to live. ServiceNow continues to position AI Control Tower as the architectural backbone that every AI investment in the enterprise passes through, regardless of origin.

Snap in Veza for access graph and enforcement, add Armis for device and asset visibility, and you have a model for AICT governing agent behavior, Veza governing what agents can reach and Armis governing the infrastructure they operate on.

2. Agentic AI Stopped Being a Roadmap Item

K26 made one thing very clear, ServiceNow is delivering AI that holds an identity, carries scoped permissions, and executes multi-step work autonomously inside live workflows, not just an assisting layer of technology. Specialists are in production across various applications such as IT, HR, CSM, and Security. The architectural implication of that shift is significant. These agents are not just a bolt-on; they need to be designed into the platform architecture from the start. Think about identity and access boundaries defined, approval chains mapped, escalation paths built, and audit trails baked in.

When someone asks how AI fits into their service delivery model, the answer can no longer be a chatbot bolted onto a portal. It must be a conversation about agent design patterns, governance guardrails, and how autonomous execution integrates with the workflows and data models already in place.

3. The Portal Era Is Over

Employee Slate went live and it is not an iteration on Employee Center. It is a different architectural foundation entirely. The portal navigation model is out. Conversation-first, AI-driven interaction is in, powered by Moveworks and built to evolve on a monthly release cadence.

The reason this matters architecturally is that legacy Employee Center design patterns, page layouts, catalog navigation structures, and portal information hierarchies do not translate cleanly into a Slate model. Anchoring the design to how Employee Center worked is in the past, we do not want to build technical debt. The new conversation starts with Slate's architecture: omni-bar interaction, personalized canvas, unified inbox, and enterprise search as the primary navigation layer. Design forward, not backward.

 

 

Billy Sprague is a technology leader and ServiceNow professional with more than 13 years of experience helping organizations improve HR and IT operations, workflow automation, and digital transformation initiatives. He is known for combining technical expertise with a collaborative leadership style and a strong focus on customer success. 

Similar posts

Get notified when new resources are added

Receive an email when new resources are published.  Stay current with the Astrica team!