A director proposes decommissioning the entire existing service management toolset and processes on day one of a transformation, on the grounds that a clean slate avoids inherited bad habits. Which guiding principle argues against this, and why?
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 Focus on value, because the cost of rebuilding always exceeds the value the new toolset would create
'Focus on value' is about linking work to value for the service consumer and other stakeholders, not a cost-benefit rule about rebuilds. A rebuild can create value; the objection here is that the current state was never assessed.
Not correct Keep it simple and practical, because a clean slate always produces more steps than it removes
A rebuild is not automatically more complex, and this principle is about the number of steps in a way of working, not about whether to retain existing assets.
Correct Start where you are, because the current state should be assessed first so that anything already delivering value is retained rather than rebuilt
Correct. The principle explicitly cautions against starting over; existing services, processes, people and tools should be examined and reused where they support the target state.
Not correct Think and work holistically, because a clean slate would fail to account for all four dimensions of service management
A holistic view would indeed be needed when designing the replacement, but the principle that speaks directly to not throwing away what already exists, and to assessing the current state first, is 'start where you are'.
Why
'Start where you are' says that services and methods already in place should be measured and assessed directly, because they usually contain elements that can be reused to reach the desired state. Discarding everything wastes value that already exists and destroys the baseline needed to judge whether the change improved anything.
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