Service management has always been about enabling business outcomes, yet many organizations still practice it as a technology management discipline. The question isn’t whether service management understands business value—the question is why organizational leadership, and IT cultures often fail to frame it that way.
Why we don’t understand
There are several reasons why service management is misunderstood—from both IT and non-IT perspectives.
- It’s an identity problem – Frameworks like ITIL® have emphasized value creation, outcomes, and services for years. Yet in practice, many organizations still experience service management as a collection of operational processes. There’s a gap between the theory and the implementation.
- The approach to service management adoption – This may have been one of the unintended consequences of widespread framework adoption. Organizations spent years implementing IT operational practices like incident management, change management, service request management, and maybe a few other practices…and stopped. Service management success was measured in terms of IT compliance with these practices and IT-defined performance measures rather than organizational outcomes. The conversation became “Did we follow the process?” instead of “Did the process improve customer outcomes?”
And when that happens, the organization naturally associated service management with bureaucracy instead of value creation.
- Leadership delegated – or ignored – service management instead of owning it – Many executives view service management as something to delegate to IT rather than as a management discipline that spans the enterprise. Consider how CEOs typically discuss strategic priorities in terms of customer experience, digital transformation, innovation, growth, and operational resilience. Rarely do CEOs discuss service management as a strategic differentiator. Ironically, these strategic priorities depend on the outcomes from good service management to realize strategic success.
- IT made service management about itself – IT initiated an implementation project without inviting non-IT colleagues to be part of the strategy or design of service management. As a result, many service management implementations are focused only on the work of (some parts of) the IT organization and not on the business of the business.
- IT reinforces the misconception – Many IT organizations continue to define themselves by technology rather than by the services and business outcomes they enable. Ask an infrastructure team what they do, and you’ll likely hear about managing servers, networks, cloud platforms, and endpoints.
Ask non-IT colleagues what they need, and you’ll hear things like closing sales, shipping products, collaborating with employees, and processing customer orders. Those are entirely different conversations. Technology should be discussed as an enabler, not the objective.
Why this matters now
I think the rise of AI makes this conversation even more important.
AI can make individual tasks dramatically faster. It can summarize incidents, route requests, answer questions, generate code, and automate workflows. But as I’ve said before, AI cannot compensate for a poorly designed service operating model. If the underlying service is fragmented, the data is inconsistent, ownership is unclear, or processes optimize local efficiency instead of customer outcomes, AI simply accelerates those shortcomings.
Organizations that will benefit most from AI won’t necessarily have the best AI. But they will have the clearest understanding of:
- the services they provide
- the outcomes those services are meant to achieve
- the governance to continually improve them
That’s the domain of mature service management—not as an IT function, but as a business capability.
Imagine a sales organization whose “service” is enabling representatives to close deals. If requests for pricing, CRM access, and contract approvals bounce across siloed teams and misaligned tools, AI chatbots and copilots will only help sales reps get faster (but poor) answers to a broken process. When service management focuses on the end-to-end sales outcome instead, AI can amplify a well-designed service rather than accelerate dysfunction.
It’s about the business
Here’s the deeper issue.
Many organizations still see service management as running services. I think the future of service management is managing the enterprise through services.
That’s a subtle but profound distinction. “Running services” is concerned with system availability, meeting SLAs, and resolving incidents. “Managing the enterprise through services” asks (and provides answers to) the following questions:
- Are customers accomplishing what they came here to do?
- Are employees able to deliver value without unnecessary friction?
- Are our services adapting as customer needs change?
- Are we creating outcomes that strengthen the business?
The first perspective is operational.
The opportunity is there…if we only take it
For me, that’s the opportunity for the profession. Service management doesn’t need to reinvent itself; it needs to reclaim its original purpose; it needs to reframe the conversation. Instead of being known for process governance or just as a service desk, it should be recognized as the discipline that enables organizations to consistently deliver value, improve experiences, and adapt with confidence.
In that framing, here are examples of some of the clearest indicators that service management is succeeding:
- Employee Experience – Employees spend more time creating value and less time dealing with technology challenges.
- Customer experience – Customer interactions are easier, which helps drive improved satisfaction.
- Revenue protection – Effective service management protects existing revenue by minimizing or eliminating the impact of disruptions to customer-facing systems.
- Time-to-market – New products and services reach customers faster.
- Strategic Execution – Good service management ensures that technology investments support, deliver, and sustain strategic goals and objectives.
When executives talk about digital transformation, operational resilience, and customer experience, they are already talking about the outcomes of service management—even if they don’t use that language.
It’s time for service management professionals to help leadership reframe the conversation from “IT processes” to “services that deliver strategic business outcomes.”
Share 