A new incident categorization scheme has 140 categories, and analysts routinely pick the wrong one because the distinctions do not change how an incident is handled. What should the team do, and on which guiding principle should they rely?
ITIL 4 Foundation, objective 2. The ITIL guiding principles medium
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 Keep all 140 categories but automate the categorization, applying 'optimize and automate'
This automates a scheme that has already been shown not to help. The principle's own sequencing says optimize first; automating an over-complex scheme entrenches it.
Correct Reduce the scheme to the minimum set of categories that actually change how work is done, applying 'keep it simple and practical'
Correct. The principle calls for using the minimum number of steps needed to achieve an objective and removing anything that does not produce a useful outcome.
Not correct Keep the scheme and add training and reporting so accuracy is visible, applying 'collaborate and promote visibility'
Visibility of the error rate does not remove the cause. The scheme itself carries unnecessary complexity that produces no useful outcome.
Not correct Retain the scheme because a complete taxonomy supports end-to-end analysis, applying 'think and work holistically'
Working holistically does not mean maximizing detail. Holistic thinking would still reject categories that add effort without changing any decision or outcome.
Why
'Keep it simple and practical' is applied by asking what the minimum is that achieves the objective. Detail that does not alter how the work is done is complexity without value, and the principle says to eliminate it. Note the interaction with 'optimize and automate': automating the bloated scheme would be the wrong order.
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