Coronavirus Articles

Every new tool promises to simplify IT operations and somehow adds another layer of complexity instead. Rui Alves argues that bolting AI onto a tangle of disconnected systems just gives you automation without intelligence, and that the CTOs getting real value in 2026 are doing the unglamorous work first: connecting service management, monitoring, assets, FinOps, and governance into a single operational layer. A practical checklist for what AI-ready operations actually require.
Compliance evidence is usually assembled from scattered systems, but one source often hides in plain sight: your ITSM platform. Mahati Dwibhashi of ManageEngine shows how change records, access approvals, incident logs, and asset data, captured as a byproduct of daily operations, double as audit evidence for frameworks like SOC 2 and ISO 27001. She covers where ITSM stops and security tools take over, and the small workflow tweaks that make the data audit-ready.
Many IT service desks still operate with a “very important person” (VIP) list (after all, it’s a long-held IT support best practice). However, given the importance of technology to business operations and outcomes, the VIP list is showing its age. And more importantly, it’s likely getting in the way of something more useful to your organization. Does your IT service desk need a VIR list?
Every few years, the IT industry settles on a new savior. Agile. Then DevOps. Now AI. The pattern, as Kaimar Karu sees it, is that organizations adopt each one without first knowing what they want from it, and then act surprised when the results don’t live up to the hype. In this episode of Roman Jouravlev’s Conversations with Giants series, Kaimar covers the iron curtain still sitting between ITIL and DevOps, why the ITIL guiding principles are a net rather than a recipe, why AI should never be the goal in itself, and the skills technology won’t easily replace.
IT support teams often spend all their time reacting to issues – resetting passwords, restoring services, responding to issues (incidents), and managing major incidents such as outages. In this article, learn how problem management helps eliminate root causes, reduce repeat incidents, lower costs, and shift IT from firefighting to prevention.
Most organizations overestimate what a single CMDB “transformation” can do and underestimate the power of a stream of small, compounding design and automation decisions. This article explains the benefits of the latter over the former.
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 rather than treating the buzzwords as a checklist.
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, why the guiding principles were ITIL Practitioner’s most important contribution, 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 project work compete for the same people, and reactive always wins. His fix is bifurcated execution, separating the two into distinct streams with protected capacity, so AI initiatives stop drifting toward urgency.
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 joined as a Developer Experience (DevRel) consultant at one of Kazakhstan’s largest banks with 700+ 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 promised.
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, they paste the error into an AI tool and get a fix in seconds. The problem is solved, but no incident was recorded. Judin Joan Soundarya S of ManageEngine looks at what shadow AI costs problem management and security operations, and the practical ways ITSM platforms can regain that visibility without slowing users down.
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 them to look for. He also offers the questions to put to any vendor claiming agentic AI.
For over 20 years, ITSM has repeated the same failures. Through ABC cards, Paul Wilkinson reveals how culture, leadership, and behavior – not tools or frameworks – consistently derail success. As AI becomes the latest “shiny new thing,” the question remains: why hasn’t the industry learned?