1. Multiple practices addressing similar issues Incident Management, Problem Management, and Change Management all deal with resolving system health issues in different ways[7]. There is some overlap in their goals and processes.
  2. Redundant documentation and ticket creation The process of creating and passing around tickets for incidents, problems, and changes can be seen as redundant in some cases where an issue could potentially be resolved more directly[7].
  3. Overlap between ITIL 4 and other frameworks There is significant overlap between ITIL 4 practices and processes defined in other frameworks like COBIT[8]. Organizations may end up with redundant processes if implementing multiple frameworks.
  4. Similar activities across practices Many ITIL 4 practices involve similar activities around planning, monitoring, reporting etc. There may be some redundancy in how these common activities are carried out across different practices[2].
  5. Legacy processes carried over Some processes from previous ITIL versions were carried over into ITIL 4 practices, potentially leading to redundancies with newer concepts[4].
  6. Overlapping responsibilities Different practices may assign similar responsibilities to different roles, creating potential redundancies in accountability[2].