What is NOT a key factor when judging what to keep?

In the context of evaluating what to maintain within an ITIL framework, the key factors for judgment are deeply intertwined with value creation and simplicity. The focus on activities that contribute to value creation emphasizes that any retained processes or components should directly support the overall objectives of the organization and ultimately enhance customer satisfaction. Similarly, understanding how something contributes to value is vital because it ensures that resources are allocated effectively, allowing for informed decisions about what needs to be retained or improved.

Starting with an uncomplicated approach and then incrementally adding complexity is also important because it allows for a more manageable assessment process. This strategy enables organizations to focus on essential elements first, identifying what works well before layering on more complexity, which might complicate operations unnecessarily.

In contrast, recognizing the complexity of all systems, while valuable in some contexts, isn’t a primary consideration when determining what to keep. Complexity can often lead to confusion and can detract from clarity and focus on value. In an ITIL perspective, the aim is to simplify processes wherever possible to create value, rather than to be bogged down by the inherent complexity of different systems. Therefore, focusing on simplicity, clarity in value contribution, and value-driven decisions is more crucial than merely recognizing the complex nature of systems.