ITSM in Transition: From ITIL v3 to Modern Service Management
ITIL v3 formalised ITSM – but it also made it bureaucratic. Many companies implemented the processes so rigidly that the actual purpose got lost: helping people get their work done.
ITIL 4 corrected that course. The focus is now on value co-creation, service value streams and the insight that processes serve the flow of value – not the other way round. Jira Service Management (JSM) is the tool that puts this philosophy into practice.
"The purpose of the service value system is to ensure that the organization continually co-creates value with all stakeholders through the use and management of products and services."
— AXELOS, ITIL 4 Foundation (2019)
What Sets JSM Apart from Classic ITSM Tools
Developer-friendly
JSM is the only ITSM tool that is natively connected to a development platform. Jira Software, Bitbucket, Opsgenie and Statuspage together form a closed loop from incident to resolution. When an incident comes in, the team can see the related commit, the deployment pipeline and the change request straight away.
Self-Service Portal
The JSM customer portal is intuitive and customisable. Employees find answers in the knowledge base (connected to Confluence) before they raise a ticket. That cuts ticket volume by 20-40% – if the knowledge base is well maintained.
Automation
JSM Cloud offers powerful automation: auto-triage, SLA management, escalations, notifications. In The DevOps Handbook, Kim, Humble, Debois and Willis describe the principle “Automate all the things” – JSM makes that possible for service processes.
Implementation Approach: Crawl, Walk, Run
Crawl: IT Help Desk
The classic starting point: a service desk for IT requests. Incident management, service requests, SLA tracking. This is productive within a few weeks – and delivers value right away.
Walk: IT Service Management
Expansion to change management, problem management and asset management. This is where the integration with Jira Software (changes are linked directly to deployments) and Confluence (knowledge base) begins.
Run: Enterprise Service Management
JSM beyond IT: HR ticketing, facility management, legal requests, finance processes. Every department gets its own portal with its own workflows – but on one shared platform. Read more in our article on Enterprise Service Management.
The Most Common JSM Implementation Mistakes
Too Much ITIL, Not Enough Pragmatism
ITIL is a framework, not a law. Implement the processes you need – not every one that is in the book. Mark Schwartz writes in The Art of Business Value: “We need to stop treating IT like a cost center and start treating it like a value creator.” That applies to ITSM in particular.
Underestimating Portal Design
The self-service portal is the face of your IT service. If it is cluttered, slow or ugly, employees will keep sending emails or asking in chat. Invest in good portal design.
Neglecting the Knowledge Base
The Confluence integration is one of JSM's biggest advantages – but only if the knowledge base is actively maintained. Every resolved incident should come with the question: “Can we solve this with a KB article next time?”
Further Reading
- AXELOS (2019): ITIL 4 Foundation. TSO.
- Kim, G., Humble, J., Debois, P., Willis, J. (2016): The DevOps Handbook. IT Revolution Press.
- Schwartz, M. (2016): The Art of Business Value. IT Revolution Press.
