ITSM, or IT service management, is how an IT team delivers and supports the technology a business depends on. It covers everything from fixing a broken laptop to approving a major system change, organized as repeatable processes instead of ad-hoc heroics.
Most IT teams start informally: someone emails, someone fixes it, nobody writes it down. That works until the team grows, the systems multiply, and the same problems keep coming back. ITSM is the discipline that replaces that informal pattern with something a business can rely on.
What ITSM actually covers
ITSM is usually described as a set of practices, and the core ones are the same in almost every organization. Incident management restores service when something breaks. Problem management finds and fixes the root cause so it does not break again. Change management controls how systems are modified, so a fix for one team does not break another.
Around those three sit the supporting practices. Service request management handles the routine asks: new accounts, new laptops, access to a system. Asset management tracks what the organization owns and where it is. Knowledge management captures answers so the next person with the same problem finds them without opening a ticket.
None of these practices is complicated on its own. The value of ITSM is that they connect: an incident links to the problem that caused it, the problem links to the change that fixes it, and the change links to the assets it touches. That chain is what turns firefighting into management.
ITSM vs. ITIL
ITSM is the discipline; ITIL is the framework most teams use to practice it. ITIL, now in its fourth version, describes the practices above in detail and adds guidance on value, governance, and continual improvement.
A team does not need to adopt all of ITIL to do ITSM well. Many teams start with incident and request management, add change control when a bad change causes an outage, and add problem management when the same incidents keep recurring. That order — driven by real pain, not by a textbook — is usually the right one.
Tip: Start with the practice that hurts most. If outages are chaotic, fix incident management first. If changes keep breaking things, start with change control. A framework adopted to solve a real problem sticks; one adopted for its own sake does not.
The ITSM software landscape
ITSM work happens in a platform, and the platform matters. A good ITSM tool gives the team a single queue, a service catalog users can actually find, a knowledge base, asset and configuration data, and automation that routes and escalates without human effort.
The market ranges from enterprise platforms such as ServiceNow, built for large organizations with complex processes, to mid-market tools such as Freshservice and Jira Service Management, to budget options such as ManageEngine ServiceDesk Plus. The right choice depends on team size, process maturity, and budget — not on which vendor has the longest feature list.
How to tell if ITSM is working
The test is not whether the team follows the process, but whether the business notices the difference. Incidents get resolved faster. The same problem stops recurring. Changes go in without surprise outages. Users can find answers themselves instead of opening tickets.
Measure that with a small set of numbers and review them monthly: mean time to repair, first-contact resolution rate, ticket volume by category, SLA compliance, and customer satisfaction. If those numbers move in the right direction, ITSM is working. If they do not, the process needs adjusting, not more process.
Try the tool
A service level agreement is the promise at the heart of ITSM: how available a service will be, and what happens when it is not. Run your SLA percentage through the SLA uptime calculator to see the downtime it actually allows per month and per year, and use that number when you set targets your team can keep.