Many organizations have invested heavily in IT service management (ITSM). Processes are standardized, service level agreements (SLAs) are defined, and performance dashboards are closely monitored. On the surface, it looks like things are under control: teams work together, incidents are resolved, and services are delivered. But beneath this polished surface lies a subtle and dangerous risk: people may be cooperating, but not collaborating. This distinction makes all the difference between ITSM that looks efficient and ITSM that actually delivers business value. This article explains why cooperation without collaboration in ITSM is a hidden risk.
Cooperation vs. collaboration in ITSM
These two terms are often used interchangeably, but in practice, they are worlds apart:
- Cooperation is transactional. Teams hand off deliverables, share updates, and respect boundaries.
- Collaboration is transformational. It requires co-creation around a shared goal, mutual accountability, and a focus on outcomes rather than just outputs.
In ITSM, many organizations unintentionally stop at cooperation. Each team optimizes its own performance, but the pieces don’t connect into seamless value streams. The result? Services that are well-managed on paper, yet misaligned with what the business actually needs.
Why does this collaboration in ITSM risk emerge?
Several systemic factors combine to create this risk:
- Fragmented key performance indicators (KPIs) and objectives and key results (OKRs). Many organizations still measure performance within silos. For example, the IT service desk is rewarded for closing tickets quickly, the infrastructure team for maintaining uptime, and the application team for delivering features. Individually, these metrics look positive. But together, they create a fragmented picture. A ticket may be “resolved within SLA.” However, if it required multiple handoffs and took weeks, the customer experience is still negative. This issue is recognized in ITIL 4, which emphasizes moving away from process-only metrics toward value-stream-oriented measures.
- Middle management myopia. Middle managers still often focus on optimizing their own department rather than the entire system. Without a “helicopter view” of strategic goals, they unintentionally reinforce silos. Michael Hammer’s famous Harvard Business Review article, “Reengineering Work: Don’t Automate, Obliterate” (1990), warned about this: organizations risk becoming efficient at the wrong things. That warning is as relevant in today’s digital service economy as it was in the early days of process reengineering.
- Individual reward systems. When performance management emphasizes individual heroics, it undermines collaboration in ITSM. For example, an operations engineer rewarded for uptime may resist changes that involve downtime, even if those changes support innovation. Or a developer rewarded for delivering features may push code into production without considering maintainability. Both individuals succeed in their own metrics, but the organization loses.
- Process-centric culture. ITSM has historically been process-driven, inherited from early ITSM frameworks. Compliance with the process becomes the primary goal. While processes are essential, managing them in isolation creates a false sense of control. The result is services that are “green” on the dashboard but fragmented in practice.
The consequences of cooperation without collaboration in ITSM
The absence of collaboration in ITSM doesn’t just slow things down; it also hinders progress. It creates structural barriers to value creation:
- Value streams cannot emerge. Without collaboration in ITSM, processes remain isolated. They never connect into end-to-end value streams that translate business strategy into delivered outcomes.
- Inefficient handoffs. Each team works well within its boundaries, but every handoff becomes a point of friction. Tickets bounce. Delays accumulate. Accountability is blurred.
- Strategic misalignment. Local optimizations may even contradict organizational priorities. A compliance team may achieve 100% policy adherence, yet introduce delays that make innovation impossible. Or an infrastructure team may hit uptime targets, yet block business-driven changes needed to enter new markets.
- Erosion of trust and morale. Teams feel like they are succeeding locally but failing collectively. Blame culture emerges at the seams between processes. Morale suffers, and so does retention.
Real-world illustration #1: The rise of DevOps
The DevOps movement is one of the clearest responses to this risk. For years, development and operations teams cooperated through formal handoffs – code was developed, tested, and then “thrown over the wall” to operations.
But there was no true collaboration. Developers were not accountable for uptime, and operations were not incentivized to facilitate change. DevOps broke this barrier by introducing shared accountability and shared metrics such as mean time to recovery (MTTR) and deployment frequency.
Real-world illustration #2: NHS Digital (UK Healthcare)
In large healthcare IT programs, rigid adherence to ITIL processes led to technically compliant but user-hostile systems. Clinical staff – the actual frontline end-users – were not meaningfully involved.
The absence of collaboration between IT and healthcare professionals resulted in systems that didn’t support real-world workflows. The services were “green” by IT standards, but “red” in terms of value.
Real-world illustration #3: Enterprise service management (ESM)
ESM-focused ITSM tool vendors have repeatedly reported that organizations adopting value stream mapping see greater business alignment.
Where value streams are not established, ESM tools become expensive process engines that are efficient at handoffs but ineffective at driving outcomes.
Mitigating this collaboration in ITSM risk
The absence of collaboration in ITSM is not inevitable. Organizations can take concrete steps to mitigate it:
- Shift to value-based metrics. Move beyond SLA compliance and siloed KPIs. Focus on shared business outcomes such as customer satisfaction, time-to-market, or cost-to-value ratio.
- Adopt value stream mapping. Use Lean techniques (e.g., Rother & Shook’s Learning to See) to visualize how value flows end-to-end. This fosters a shared understanding of what success entails.
- Create cross-functional governance. Establish roles such as value owners, use joint OKRs, or apply frameworks like SAFe’s program increment planning to align multiple teams.
- Foster a culture of collaboration. Run cross-team retrospectives. Hold joint problem-solving workshops. Recognize and reward collective achievements rather than just individual contributions.
The impact of cooperation without collaboration in ITSM
The risk of cooperation without collaboration in ITSM is dangerous because it hides in plain sight. On dashboards and reports, everything looks healthy. SLAs are green, processes are followed, and teams are busy.
But without collaboration, organizations remain fragmented. They optimize parts of the system at the expense of the whole. Value streams cannot emerge. Strategic goals stay out of reach.
True collaboration with shared goals, shared accountability, and shared value is the missing ingredient. Without it, ITSM (and ESM) remains a set of processes. With it, ITSM (and ESM) becomes a driver of strategy, innovation, and competitive advantage.
Ultimately, cooperation keeps the lights on. Collaboration lights the way forward.
Download the full SymphonyAI white paper: ITSM Risks into Growth Opportunities in 2026
Further Reading
David Billouz
David Billouz is the IT Axiologist. The IT Axiology is the philosophy of value applied to digital products and services. David owns a Master certificate in both ITILV3 and ITL4. He is also very active in the ITSM space as an author, an assessor, and a consultant. His work introduces innovative concepts such as the Value Level Agreement (VLA), Key Value Indicator (KVI), and the Value Management Database (VMDB), forming the foundation of a new era in enterprise service management focused on value co-measurement and realization.
