Read any ITSM platform brochure today and the same cluster of AI terms stares back: agentic AI, AI agents, RAG, AIOps, MCP. The vocabulary is moving faster than most IT teams can keep up with. Raghav S of ManageEngine explains what each one means in an ITSM context, how they differ, and how to tell which capability fits a problem you have.
Value is what the customer decides it is, not what the IT department or a framework says. It’s the test Stuart Rance has applied across a thirty-year career: would anyone on the receiving end say your work created value for them? In episode three of Conversations with Giants he explains why he hates tool replacement projects, and why using agentic AI to cut headcount is the wrong use of the technology.
If AI is the strategic priority, why are the teams meant to implement it still buried in ticket queues? John Mathieu of Allari argues the blocker isn’t culture, skills, or tooling but the operating model itself: reactive work and AI projects compete for the same people, and reactive always wins. His fix is bifurcated execution, separating the two into distinct streams with protected capacity.
This article takes my less-than-stellar experience with Uber and considers it through an ITSM lens. Hopefully, it might also make you think about the services your IT organization offers and delivers, and how they are perceived by your end-users/customers.
When Askar Aituov joined as a Developer Experience consultant at one of Kazakhstan’s largest banks, with 700-plus engineers, he expected the usual challenges: stakeholder alignment, change resistance, legacy tooling. What he didn’t expect was to watch a mature ITIL 4 implementation quietly fail to deliver what it was supposed to. This article walks through what went wrong, and why.
This article explores the role of maturity models in Service Management and ITSM – what they do well and where they often fall short – and introduces a more practical approach your organization can adapt to drive meaningful improvement.
It’s 9am and a sales manager hits a VPN error before a client call. Rather than wait on a service desk ticket, she pastes the error into an AI tool and gets a fix in seconds. Problem solved, but no incident recorded. Judin Joan Soundarya S of ManageEngine looks at what shadow AI costs problem management and security operations, and how ITSM platforms can regain visibility.
Everyone is selling agentic AI, but the gap between the weakest and strongest versions is enormous. Manish Sharma of Rezolve.ai sets out a four-stage maturity model for AI in ITSM, from legacy retrieval through reactive assistants and process agents to true agentic systems that reason, act across connected systems, and catch problems nobody asked. He also gives you the questions to put to any vendor claiming agentic AI.
For over 20 years, ITSM has repeated the same failures. Through the ABC cards, Paul Wilkinson has spent decades tracing how culture, leadership, and behavior consistently derail success, not tools or frameworks. AI is now the latest shiny thing being sold to organizations that haven’t fixed the underlying pattern. This article looks at why the industry still hasn’t learned, and what it would take.
ITSM tool migration is inevitable. The ITSM tool landscape is constantly shifting. Products are sunsetted, licensing models change, companies merge and consolidate platforms, and organizations simply outgrow their ITSM tools. At some point, you’ll migrate ITSM tool, whether you planned to or not. This article will help you!
What happened to ITSM evangelists? Explore why they disappeared, the value they brought, and why the ITSM industry needs them more than ever in 2026.
The mismatch between producer effort and user value is something Mark Smalley, IT Paradigmologist and author of nine books on digital and service management, has been thinking about for decades. In this article on the first episode of Roman Jouravlev’s Conversations with Giants series, Mark covers several ideas that have held up across four decades in ITSM.
A ticket gets escalated, comes back marked “add notes before escalation,” gets reassigned, then returns with “should have been resolved at L1.” Meanwhile the end-user is still waiting. Eusoph Simba argues the ticket ping-pong between support tiers isn’t an escalation problem but a problem with how we frame support levels. He makes the case for treating every ticket as an issue to solve, escalating on capability rather than hierarchy, and a simple standard format that breaks the loop.
This article by Daniel Breston is about neurodivergence in ITSM and was sparked (pardon the pun) by his attendance – and what he did and didn’t feel – at the Service Desk Institute (SDI) SPARK26 event.
ITIL (Version 5) describes the guiding principles as “recommendations that can guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.” This article walks through what the principles are, how they’ve evolved from ITIL 4, and how ITSM leaders can put them to use today.