According to ITIL 4, one of the guiding principles is to progress iteratively with feedback. This means that IT service providers should break down complex tasks or changes into manageable chunks, seek feedback after each iteration, and use the feedback to improve and adapt their actions. Feedback is essential for co-creating value with customers and stakeholders, as well as for learning and improving the quality of IT services. Therefore, IT managers should establish effective feedback channels that enable two-way communication with staff and other parties involved in the IT service delivery. The best approach for establishing effective feedback channels is to research how individual teams communicate internally and use the most popular collaboration tools to collect feedback. This way, IT managers can leverage the existing communication preferences and habits of the staff, and avoid imposing a new tool or method that may not be suitable or convenient for them. By using the most popular collaboration tools, IT managers can also ensure that the feedback is timely, relevant, and accessible for all parties. This approach aligns with the ITIL 4 principle of collaborating and promoting visibility, which encourages IT service providers to work together across boundaries, share information, and make use of diverse perspectives and feedback. Therefore, the answer is A. Research how individual teams communicate internally and use the most popular collaboration tools to collect feedback. The other options are not the best approach for establishing effective feedback channels, because they either do not facilitate two-way communication, or do not consider the needs and preferences of the staff. For example, option B. Establish office hours where staff are encouraged to drop by without appointments and discuss any concerns they have, may not be convenient or practical for staff who work remotely or have different schedules. Option C. Initiate a project to select and implement a collaboration tool to facilitate two-way communication with staff, may take too long and may not match the expectations or requirements of the staff. Option D. Publish a printed weekly newsletter that clearly and consistently communicates change, may not be effective or efficient for collecting feedback, as it is a one-way communication channel that does not allow for immediate or interactive responses. References:

The 7 Guiding Principles of ITIL 4: Progress iteratively with feedback1

Guiding Principles of ITIL 4: Progress Iteratively with Feedback2

The customer journey and ITIL 43

 Design thinking and service-dominant logic have in common that both involve collaborating with customers to ensure their needs are met. Design thinking is a human-centered approach to problem solving that emphasizes empathy, creativity, and experimentation. Service-dominant logic is a framework for understanding value creation, which focuses on the exchange of services between two or more entities. Both concepts share the following principles:

Value is co-created by the provider and the customer in the context of use. The provider does not deliver value, but rather offers value propositions that the customer can accept or reject. The customer is an active participant in the value creation process, not a passive recipient of goods or services.

The customer is the ultimate judge of value. The provider cannot determine the value of the offering in advance, but rather has to understand the customer’s needs, preferences, and expectations. The provider has to engage with the customer in an ongoing dialogue and feedback loop to ensure that the offering meets or exceeds the customer’s expectations.

The offering is a holistic solution that integrates goods, services, and experiences. The provider does not differentiate between tangible and intangible products, but rather offers a complete solution that addresses the customer’s problem or opportunity. The provider has to design the offering in a way that delivers a positive customer experience and enhances the customer’s well-being. References:

Exploring Overlaps and Differences in Service Dominant Logic and Design Thinking

Service-Dominant Logic: Key Principles and History

Service-Dominant Logic and How It Reframes Our Business Operations

The New Paradigm: H2H Marketing

User communities are groups of people who share a common interest or need related to a service or product. They can be formal or informal, online or offline, and may be initiated by service providers or users themselves. User communities can provide valuable feedback, insights, and support for service providers, as well as enhance the user experience and satisfaction. Therefore, service providers may recognize and support user communities that are set up by users, as long as they respect their autonomy and do not interfere with their activities. User communities are not created by service providers to investigate the cause of problems (option A), nor should they be disbanded or merged into official groups (option C). User communities may or may not have super-users, who are users with advanced skills or knowledge who can help other users, but this is not a requirement for every user community (option D). References: ITIL 4 Foundation, page 77; ITIL 4 Specialist: Drive Stakeholder Value, page 33.

The correct answer is D. Identifying and making request for outstanding payments for the service. This is because the service provider should ensure that the financial obligations of the customer are fulfilled before the service is terminated. The service provider should also update the billing and accounting records, and close any open invoices or disputes related to the service12.

A. Ensuring that user access rights are revoked for all services is not the correct answer, because the service provider should only revoke the user access rights for the service that is being retired, not for all services. The service provider should also ensure that the customer data and assets related to the service are securely deleted or transferred, and that the service provider staff are reassigned or released12.

B. Providing information to users about how to contact the service desk is not the correct answer, because the service desk is not relevant for the service that is being retired. The service provider should provide information to users about how to access alternative or replacement services, if any, and how to provide feedback or complaints about the service retirement process12.

C. Creating training schedules for users on how to use the service is not the correct answer, because the service is being retired, not introduced. The service provider should not invest any resources or efforts in training users on how to use a service that will no longer be available. The service provider should instead focus on communicating the service retirement plan and timeline, and managing the expectations and emotions of the users12. References:

ITIL 4 Managing Professional Transition Module Sample Paper - English, page 10, question 3, answer D

ITIL 4 Managing Professional Transition Module Candidate Syllabus - English, page 11, learning outcome 1.5

Safety culture is a concept that refers to the shared beliefs, perceptions, and values in relation to risks within an organization. A safety culture encourages people to be open and honest about their mistakes, learn from them, and improve their performance. A safety culture also fosters trust, collaboration, and visibility among IT staff, which can help to obtain the information needed to resolve problems. According to ITIL 4, safety culture aligns with the guiding principle of “collaborate and promote visibility”, which states that “working together across boundaries produces results that have greater buy-in, more relevance to objectives, and increased likelihood of long-term success” 1. Safety culture is also one of the key elements of the high-velocity IT approach, which aims to enable organizations to thrive in the digital era 23. References:

ITIL 4 Information security and risk management practices: embedding safety culture and behaviour

Safety cultures and happy employees

The importance of Safety Culture in the success of IT

Comprehensive Explanation:

The practices have different purposes:

Incident Management:

Focuses on restoring normal service operation as quickly as possible after interruptions.

Service Desk:

Acts as the single point of contact for users, ensuring communication, updates, and support.

Option A correctly captures these distinct roles:

Incident management = restoration

Service desk = communication interface