An improvement lead argues that 'collaborate and promote visibility' means every decision must be agreed by all stakeholders before proceeding. How should this be corrected?
ITIL 4 Foundation, objective 2. The ITIL guiding principles hard
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Not correct Visibility means publishing performance reports to executives, so stakeholder agreement is irrelevant
Visibility is broader than executive reporting; it means the work and its status are apparent to those who need to see it. And stakeholder involvement is far from irrelevant.
Not correct Collaboration applies only within the service provider organization, not to consumers or suppliers
Wrong in scope. The principle covers customers, users, suppliers and partners as well as internal teams.
Correct Collaboration does not require consensus; the aim is to involve the right people so that decisions are better informed
Correct. The principle is explicit that collaboration does not mean consensus. Insisting on unanimity slows decisions without improving them.
Not correct Collaboration should be replaced by clear escalation paths so that a single accountable owner decides everything
Single-owner decision-making is not the correction offered by this principle; the principle keeps the right people involved while accepting that not everyone must agree.
Why
The principle asks for the right people to be involved in the right roles, so that decisions draw on the information and buy-in that only those people can supply. It is explicit that collaboration is not the same as consensus: requiring everyone to agree before anything moves is a misreading that paralyses work.
Where this comes from
- Cited
- ITIL 4 syllabus clause 2
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 2 and space the ones you get wrong.
More questions on this objective
- A team has been asked to replace an ageing service desk tool. Before designing anything, the team inventories the existing tool's integrations, workflows and data, and finds that several components work well and can be carried forward. Which guiding principle is the team applying? machine-checked
- An organization decides to introduce robotic process automation for its user access request handling. Its ITIL adviser insists that the approval steps are first reviewed and the redundant ones removed. What is the reasoning behind this advice? machine-checked
- A programme has been running for eleven months with no deliverable released, because the team intends to hand over the complete solution in one go. Which guiding principle is being ignored? machine-checked
- A manager plans a service improvement using only the monthly summary reports produced by the supplier, and does not observe how the service actually runs. Which guiding principle most directly cautions against this? machine-checked
- During an improvement review, a team finds that a weekly reconciliation report is produced, circulated and archived, but no one uses it for any decision. Which guiding principle states directly that an activity like this should be eliminated? machine-checked
- A change to a payment service is planned by the application team alone. When deployed, it breaks a downstream reporting service and leaves the support team without updated documentation. Which guiding principle would most likely have prevented this? machine-checked