Why USM and Systems Thinking Outperform Traditional ITSM Approaches
https://usmwiki.com/index.php/USM_and_ITIL,_SIAM,_DevOps,_etc.#The_Viable_System_Model_(VSM)

Why USM and Systems Thinking Outperform Traditional ITSM Approaches

Since USM is a method based on systems theory, it’s not too surprising that it outperforms traditional ITSM approaches to service management.

Service management has long been dominated by frameworks like ITIL. While these practice-based frameworks provide structure, they often struggle with adaptability, complexity, and unintended consequences. The Unified Service Management (USM) method, when combined with Systems Thinking, offers a powerful alternative—one that is both structured and flexible, enabling service teams to optimize their processes[i] dynamically.

In this blog, we’ll explore specific scenarios where USM and Systems Thinking outperform traditional ITSM approaches and highlight why ITIL and practice-based frameworks often fall short.

Challenges of Traditional ITSM Frameworks

ITIL and other practice frameworks have been widely adopted to bring structure and best practices to IT service management. However, these approaches have several common shortcomings:

  • Process Complexity: ITIL’s process-heavy approach often requires significant customization, increasing complexity and cost.
  • Siloed Execution: ITIL separates Incident, Change, and Problem Management, making cross-functional service improvements challenging[ii].
  • Slow Adaptation: ITIL’s bureaucratic Change Advisory Board (CAB) slows down innovation and adaptation.
  • Limited Systemic Analysis: Traditional frameworks focus on isolated fixes rather than understanding interdependencies and feedback loops within the service ecosystem.

While these frameworks provide value, they often struggle to address recurring issues, unintended consequences of changes, and scalability challenges. This is where USM and Systems Thinking can excel.?

USM and Systems Thinking: Opportunities for Integration

Both USM and Systems Thinking offer valuable insights into service management.

USM brings order and structure to service management. Systems Thinking helps organizations avoid rigid, short-sighted solutions. The combination enables both stability and adaptability—essential for long-term success.

While USM prescribes a standardized service management system with five core processes, it does not mean rigidity in execution. Two key concepts within USM actually enable flexibility:

Routines: Localized Process Execution

A routine is a localized variation of a process that fits the needs of a specific service team or context. It allows organizations to adapt USM’s processes without altering the fundamental system structure.

USM ensures a universal structure, but routines allow for localized adaptation, making the approach scalable across different service teams.

Recursion: Linking Service Teams in a Scalable Way

Recursion in USM means that each service team operates as a mini-service provider within a larger network. It allows decentralized control while maintaining consistency across service teams.?

USM ensures that service teams can scale autonomously while remaining coordinated. This prevents bottlenecks from central control and allows teams to evolve.

But while routines and recursion introduce adaptability, there are still some challenges where Systems Thinking can help:

Emergent, non-linear problems

Routines allow teams to handle complexity locally. Systems Thinking can add value by identifying hidden systemic dependencies (e.g., fixing one routine may cause issues elsewhere).

Unintended consequences of changes

USM’s recursion ensures changes remain within each service team’s control. Systems Thinking adds value by analyzing cross-team interactions, preventing localized fixes that cause larger system failures.

System-wide improvements

USM provides a structured system, avoiding chaos. Systems Thinking helps optimize entire service ecosystems, rather than just individual teams.

Leveraging Systems Thinking in Service Management with the USM method

The USM method enables a structured service management system that ensures consistency across service teams, regardless of which practice frameworks or standards they want to leverage.

Systems Thinking provides adaptability – enabling teams to optimize beyond rigid process execution.

ITIL’s process-heavy customization is slow and expensive, while USM scales effortlessly. Practice frameworks tend to rely on centralized governance, while USM enables autonomous service teams. Most practice frameworks lack an embedded approach for continuous self-improvement, while Systems Thinking and USM’s embedded feedback loops ensure adaptive optimization.

Instead of relying solely on traditional practice-based approaches, organizations should embrace USM’s simplified, recursive model alongside Systems Thinking’s holistic optimization techniques.

This hybrid approach delivers the best of both worlds—ensuring efficiency, adaptability, and resilience in service management.

Ready to join the USM Revolution?

Contact me today for:

?


[i] Note: It’s important to recognize that Systems Thinking has a traditional view of process. USM distinguishes between process and practice. Practices incorporate all classifications of the process hierarchy, including procedures and work instructions at lower levels. Process groups/workflows/value streams at higher levels of the process hierarchy, as well as lower level routines, are derived from a stable, non-redundant process model . USM’s view of process puts a non-redundant process model in the middle, allowing upper and lower levels of the process hierarchy to adapt and evolve within a stable and sustainable process model.

[ii] The use of a non-redundant, integrated USM process model enables one standard model, allowing local teams to adapt using routines. Practice frameworks tend to encourage process customization, requiring complex alignment between practices.

Nigel Mercer

Region Manager - Middle East & Africa at APMG-International

3 周

Very informative

回复
David Mainville

Process Optimization | Digital Transformation | ITSM

3 周

Hi John Worthington, If organizations encounter difficulties with ITSM or ITIL, such as complexity, silos, or a lack of agility, it’s typically poor execution rather than the frameworks themselves. ITSM services have distinct lifecycles that begin with service strategy, followed by design, transition, operation and CSI. ITSM processes have well-defined interdependencies and include feedback loops and mechanisms for improvement.?ITSM advocates taking a holistic view of services, breaking down silos, and distinguishes between process, practice, and procedures That is why It’s called “service management” and not “implement stagnant processes”.? I see the beauty of a non-redundant model - doesn't matter if you're?changing a server or the hotel menu. ?But you can't sell that to the IT organization - it needs to be enterprise-wide. Unified Service Management (USM) might be one solution, but so can Business Process Management (BPM) or a combination of methodologies such as Design Thinking, Value Stream Mapping, and Agile.? In the end, it will always come down to a company’s culture, management style, and governance. That is what will separate failed service management implementations from successful ones.

Alan Nance

Strategic Technology Leader | Pioneer of XLA ITIL & Inducted to ITSM Hall of Fame | Top 25 HDI Thought Leader and Digital Experience Expert

3 周

John, you know my appreciation for USM. However, as far as I know, there is little evidence that USM outperforms ITSM. It should, and I expect it will, but until we see adoption in a scaled environment, doesn't it remain a well-argued thesis? The people who would benefit from USM should be the largest, most complex organizations, but as far as I can see, they are least likely to adopt it. Don't you agree that USM needs to be more consumable for the everyday person? Channeling my inner Socrates: "People love smart people but despise those that make them think."

Pieter Hoekstra

Founder & Managing Partner at Begrip | Moving People to Solution State

3 周

Very well written John, thanks!

要查看或添加评论,请登录

John Worthington的更多文章

  • Governance and the Value Maturity Model

    Governance and the Value Maturity Model

    Thanks to Matt Beran and Valence Howden for inspiring this post. Governance is often viewed as a balancing act between…

    1 条评论
  • Final Thoughts...

    Final Thoughts...

    Alignment is like herding a pack of wild dogs into the same alley and calling it order, while integration is breeding a…

    1 条评论
  • XLAs: The Next Evolution in Quality Assurance

    XLAs: The Next Evolution in Quality Assurance

    In today's experience-driven world, simply meeting technical requirements isn't enough. Businesses must ensure they are…

    2 条评论
  • Reminder

    Reminder

    If you missed last week's USM Open Meetup, don't worry! These are being held every second Monday of the month. Register…

  • Bridging the Gap Between Human-Centered Design and IT Service Management

    Bridging the Gap Between Human-Centered Design and IT Service Management

    When I first heard that HumanizingIT? was focused on IT and internal customers, I was skeptical. Wasn’t human-centered…

    8 条评论
  • Has Service Management Lost its Way?

    Has Service Management Lost its Way?

    Somewhere between the boardroom and the battlefield, a foul stench is settling over modern enterprises—a thick…

    4 条评论
  • A Bear’s Thoughts on Resilience, Friends, and Pots of Honey

    A Bear’s Thoughts on Resilience, Friends, and Pots of Honey

    Oh, bother. It seems that whenever I attend an OSC Meetup, my thoughts go bouncing off like Tigger—this way and…

    2 条评论
  • How to Avoid Automation Hell

    How to Avoid Automation Hell

    In the age of AI, the lack of a unified service management system may put you on a sure road to automation hell. USM…

    5 条评论
  • When Hair Splitting Matters: Services as Supported Facilities

    When Hair Splitting Matters: Services as Supported Facilities

    I admit when I first heard Jan van Bon talk about a service as a supported facility, and then get into functionality…

  • Are we shooting the messenger(s)?

    Are we shooting the messenger(s)?

    There’s little doubt that for many enterprises, middle management has become like a middle-aged waistline. But while…

    1 条评论

社区洞察

其他会员也浏览了