Operations | Monitoring | ITSM | DevOps | Cloud

In a rapidly changing field like technology, it's essential for IT leaders to stay up-to-date on the latest trends. And one of the best ways to do this is by reading thought-provoking tech books. In general terms, there are two kinds of books you can read. The first group consists of technical texts or those focused on frameworks, best practices, and other formal topics you want to expand your knowledge on.

Whether you know it or not, it’s quite possible that your organization has an IT Service Management approach. After all, every business wants to have the right capabilities to deliver value to its customers. But is it too possible? What’s the state of ITSM process adoption? That’s what we’re about to find out! In H1 2022, AXELOS created an IT Service Management (ITSM) Benchmarking Report for its myAXELOS subscribers.

Implementing a new service desk, however beneficial it may be, is fraught with challenges. In fact, if you google “Reasons why ITSM implementations fail,” there’s no dearth of articles and peer-reviewed research papers. But the truth is that the process is easier than it looks like – if you have an ITSM implementation roadmap and this helpful ITSM implementation checklist we’re about to provide you with.

If you're already versed in the changes to the traditional IT service management (ITSM) best practices that came with ITIL 4, you'll know that change management is now called change enablement, and there's minimal mention of the Change Advisory Board (CAB). But what does this mean for your IT organization? Do we still need the Change Advisory Board? Should we drop the CAB (if we had one)? Should we ignore ITIL 4's new change enablement guidance?

At this point, we all know that reporting is an essential part of ITSM. It helps us to have clear information about the performance of the service desk and the support team and thus make better decisions. ITSM reporting tools consist of dashboards and reports, and though it might seem great to have only two, this often poses a question: when should I use each one? If you find yourself having a hard time deciding, this article is perfect for you! We’re about to oppose dashboards vs.

On September 12, the White House ordered U.S. agencies to create a complete inventory of all third-party software they use within 90 days for IT security reasons. This could pose a real challenge for the heads of Executive Departments and Agencies, but with the right tool, this task can be easily automated.

We don’t know what the future holds. We never have and never will. But we can plan for the future based on assumptions and the insights provided by trusted industry sources. Bearing that in mind, we asked 11 IT professionals what they thought were the top IT skills in demand not for 2023 but 2025. Why, you may be asking yourself. Well, because we wanted to get a more midterm picture of what IT and IT service management (ITSM) industry authorities believe is in store for the next few years.

Although the word “contract” immediately takes us to the Legal department, it also has a lot to do with IT. Having a proper contract lifecycle management of IT and software assets not only helps organizations to reduce costs, but if connected to the assets themselves, it becomes an effective way to boost productivity. The easiest and quickest way to do this is using as your contract lifecycle management software – on top of being your ITAM tool. How?

Getting a unified IT asset inventory can be a headache. Thus, you might be tempted to postpone it. However, sooner or later, you’ll need to get it done. So, we'd recommend you'd better not procrastinate. Sounds a bit harsh, we know, and we understand the reason behind it too. This can be a pretty daunting task, especially if you have multiple files and apps, or untracked assets. But don’t panic! What if we told you you can have your inventory done in just a day?