Which guiding principle considers which parts of an existing process should be kept by identifying how they contribute to value creation?
D. Keep it simple and practical
Explanation
The ITILGuiding Principle is covered in Section 4. 3 Page 58
Progress iteratively with feedback
Resist the temptation to do everything at once. Even huge initiatives must be accomplished iteratively. By organizing work into smaller, manageable sections that can be executed and completed in a timely manner, the focus on each
effort will be sharper and easier to maintain.
Improvement iterations can be sequential or simultaneous, based on the requirements of the improvement and what resources are available. Each individual iteration should be both manageable and managed, ensuring that tangible results
are returned in a timely manner and built upon to create further improvement.
A major improvement initiative or programme may be organized into several significant improvement initiatives, and each of these may, in turn, comprise smaller improvement efforts. The overall initiative or programme, as well as its
component iterations, must be continually re-evaluated and potentially revised to reflect any changes in circumstances and ensure that the focus on value has not been lost. This re-evaluation should make use of a wide range of feedback
channels and methods to ensure that the status of the initiative and its progress are properly understood.
Collaborate and promote visibility
When initiatives involve the right people in the correct roles, efforts benefit from better buy-in, more relevance (because better information is available for decision-making) and increased likelihood of long-term success.
Creative solutions, enthusiastic contributions, and important perspectives can be obtained from unexpected sources, so inclusion is generally a better policy than exclusion. Cooperation and collaboration are better than isolated work, which is
frequently referred to as `silo activity'. Silos can occur through the behaviour of individuals and teams, but also through structural causes. This typically happens where functions or business units in an organization are impeded or unable to
collaborate, because their processes, systems, documentation, and communications are designed to fulfil the needs of only a specific part of the organization. Applying the guiding principle of think and work holistically (see section 4. 3. 5) can
help organizations to break down barriers between silos of work.
Think and work holistically
No service, practice, process, department, or supplier stands alone. The outputs that the organization delivers to itself, its customers, and other stakeholders will suffer unless it works in an integrated way to handle its activities as a whole,
rather than as separate parts. All the organization's activities should be focused on the delivery of value.
Services are delivered to internal and external service consumers through the coordination and integration of the four dimensions of service management (see Chapter 3). Taking a holistic approach to service management includes
establishing an understanding of how all the parts of an organization work together in an integrated way. It requires end-to-end visibility of how demand is captured and translated into outcomes. In a complex system, the alteration of one
element can impact others and, where possible, these impacts need to be identified, analysed and planned for.
Keep it simple and practical
Always use the minimum number of steps to accomplish an objective.
Outcome-based thinking should be used to produce practical solutions that deliver valuable outcomes. If a process, service, action, or metric fails to provide value or produce a useful outcome, then eliminate it. Although this principle may
seem obvious, it is frequently ignored, resulting in overly complex methods of work that rarely maximize outcomes or minimize cost.
Trying to provide a solution for every exception will often lead to over-complication. When creating a process or a service, designers need to think about exceptions, but they cannot cover them all.
Instead, rules should be designed that can be used to handle exceptions generally.
The Best choice to select is "Keep it simple and practical"
Axelos. (2019). ITIL Foundation ITIL 4 Edition. Norwich,: The Stationery Office.