The Theatre of IT: What ITSM and ITIL Actually Are (And Why Confusing Them Costs You Credibility)

Ask ten IT professionals to define ITSM and ITIL, and at least half will use the terms interchangeably. That's a problem — not a pedantic one, but a practical one. Conflating "the practice" with "one framework for the practice" leads organizations to assume they need to adopt ITIL wholesale to have functioning service management, when in reality every organization already does ITSM, whether or not it's ever opened an ITIL manual.

Let’s try to clarify the difference using a theatre production analogy:

• ITSM → the overall production
• ITIL → a framework/script for organizing the production
• Service delivery → the performance
• Service Desk → front of house
• Tools/automation → backstage infrastructure
• Incident management → handling something going wrong during the performance
• Utility → does the production deliver what is needed?
• Warranty → can it be delivered reliably?
• Experience → what is it actually like for the audience?
• Sustainability → can the production continue responsibly over time?

Now, let's deep dive into it:

ITSM Is the Theatre Production. ITIL Is the Script.

IT Service Management (ITSM) is the entire theatre production: the actors, stage crew, lighting, venue, audience, and all the practices that make a performance work night after night. It is the structured practice of planning, delivering, and managing IT services so they align with business goals and create real value for the people receiving them. It moves a team from "fixing broken computers" to running like a professional service business.

• Scope: Broad and overarching — your tools, your people, your internal policies, all of it
• Exclusivity: Every modern company does ITSM, whether they've formalized it or not — just as every theatre production has some structure, planned or improvised

ITIL (Information Technology Infrastructure Library) is one specific script an organization can choose to stage the production from. It's a prescriptive but flexible set of instructions (standardized processes like Incident, Problem, and Change Management) that gives the cast and crew guidance on how to handle different situations during the production.

ITIL is optional. An organization can run excellent ITSM using a different framework entirely (eg., COBIT, DevOps, or ISO 20000) just as a theatre company can create a compelling production without using a particular script.

The critical point: ITIL is a framework for ITSM, not a replacement for ITSM. You can absolutely practice ITSM without adopting ITIL Every theatre company is already running a production. The only question is whether they're following a coherent approach or improvising from scene to scene.

Service Delivery: The Practice, On Stage, Night After Night

Where this distinction becomes operationally real is in service delivery — the actual nightly performance, not the theory behind it.

In daily ITSM operations, service delivery includes:

• The Service Desk — the front-of-house point of contact (box office) where users request equipment, report broken software, or request access
• Service Level Agreements (SLAs) — the commitments that define the expected level and timing of service (the show): "critical outages resolved within 2 hours"
• Tools & Automation — AI-driven routing, ticketing platforms, and automated resets that keep the production running smoothly behind the curtain

Under the ITIL framework, service delivery is structured around activities and practices designed to create and realize value (Service Value Chain). ITIL (Version 5) expands this perspective beyond simply delivering a functional and reliable service, putting greater emphasis on the overall experience and on sustainable value creation:

• Design and Transition — rehearsing and testing a service (the show) before opening night, ensuring it is ready for a reliable first performance
• Deliver and Support — the stage manager's job during the run: keeping the show on track and resolving disruptions the moment they happen
• Utility, Warranty, Experience and Sustainability — in ITIL (Version 5), a service isn't successful simply because it technically works.

Think of a theatre production: utility is whether the production delivers what the audience came to see; warranty is whether the theatre can deliver it reliably, safely, securely and with sufficient capacity; experience is how the audience actually experiences the production — whether it is clear, accessible, engaging and leaves them with confidence in the theatre; and sustainability is whether the theatre production can continue responsibly over time, considering the resources, environmental impact and wider consequences involved. A technically flawless production can still fail if the audience has a poor experience, and a successful production must also be sustainable enough to keep running into the future.

The Core Processes Every Production Needs

Regardless of which script an organization follows, successful service delivery relies on the same core processes:

1. Incident management — restoring normal service as quickly as possible after an unplanned interruption (the equivalent of recovering gracefully when a line is dropped mid-scene)
2. Problem management — finding the root cause of recurring issues so they stop happening, rather than just responding to each recurrence
3. Change management — controlling risk when updating software or hardware (so a change to the production doesn't disrupt the performance in progress)
4. Knowledge management — maintaining a searchable database of solutions so both users (self-service) and staff (cast) can resolve issues faster
5. Self-service portals — empowering end-users to handle simple requests without waiting for a stagehand

These five processes are framework-agnostic. They apply whether the organization is following ITIL, COBIT, DevOps principles, or a homegrown model — because they describe what any well-run service operation needs, regardless of which framework is being used.

Why the Distinction Matters for Leaders

Getting this right isn't academic. Leaders who understand that ITSM is the overarching practice and ITIL is one optional framework within it make better decisions about:

• Tooling investment — you're buying a platform for ITSM, not "for ITIL"
• Framework selection — the right framework depends on organizational maturity and culture, not on which one is most commonly cited
• Vendor conversations — a vendor claiming "ITIL compliance" is describing alignment to one framework (single script), not proof they understand your ITSM environment (theatre production)

The Takeaway

Every organization is already practicing ITSM, whether it realizes it or not. The choice isn't whether to "do" service management — that's happening regardless. The choice is whether to manage it through a deliberate, well-structured framework such as ITIL, or to keep improvising and hope the production holds together.
For operations leaders, the value of frameworks like ITIL isn't in the label — it's in the discipline of designing, transitioning, delivering and supporting services while ensuring they provide utility, warranty, experience and sustainability throughout their lifecycle.

In the theatre analogy: the value is in the discipline of preparing the production, running it reliably, creating a good experience for the audience, and ensuring the production can be sustained night after night