Which guiding principle recommends eliminating activities that do not contribute to the creation of value?

The 'Keep it simple and practical' guiding principle advocates for using the minimum number of steps necessary to accomplish an objective. It emphasizes that any process, service, action, or metric that does not contribute to value creation is a source of waste and should be eliminated. This principle ensures that activities are outcome-based and focused on delivering tangible benefits to stakeholders, avoiding overly complex methods where a simpler approach would be more effective.

A. Start where you are: This principle advises leveraging existing services, processes, and tools rather than starting from scratch, focusing on assessment before action.

B. Collaborate and promote visibility: This principle focuses on working together, sharing information, and ensuring stakeholders understand the process, which facilitates better decision-making.

D. Optimize and automate: This principle is about maximizing the effectiveness of a resource or activity and using technology for efficiency, which typically occurs after non-value-adding steps have been removed.

1. AXELOS. (2019). ITIL® Foundation: ITIL 4 Edition. TSO (The Stationery Office).

Section 4.3.5

"Keep it simple and practical": "If a process

service

action or metric fails to provide value or produce a useful outcome

eliminate it. In a process

try to eliminate steps that do not contribute to the creation of value for any stakeholder." (p. 45)

Section 4.3.2

"Start where you are": This section explains the importance of observing what already exists and using measurements as a starting point for improvement. (p. 42)

Section 4.3.4

"Collaborate and promote visibility": This section details the need for involving the right people at the right time and making work visible to identify bottlenecks. (p. 44)

Section 4.3.6

"Optimize and automate": This section describes optimization as making something "as effective and useful as it needs to be" before considering automation. (p. 46)