ITIL 4 SCM common mistakes
ITIL 4 SCM · Understand the traps and how to avoid them.
Treating the service value chain's six activities (plan, improve, engage, design and transition, obtain/build, deliver and support) as a fixed sequential pipeline and mapping a value stream as plan-then-engage-then-design in strict order.
Candidates carry over the old ITIL v3 lifecycle mental model (strategy, design, transition, operation, continual improvement) which was sequential, so they assume the ITIL 4 value chain is a linear process with a required start and end.
What to do instead
Memorise that the value chain is a set of interconnected activities combined in many different sequences tailored to each value stream. Practise drawing at least three value streams (e.g. a new service request, an incident resolution, a change deployment) and show which activities are used, in what order, and where loops back to improve occur. State explicitly that activities can be revisited and that not every value stream uses all six.
Answering practice questions by naming an ITIL practice where the question actually asks for a value chain activity, or vice versa, e.g. choosing 'incident management' when the correct answer is 'deliver and support'.
Practices and value chain activities overlap in vocabulary (support, transition, design), and candidates do not pause to identify what category of concept the stem is asking about before scanning the options.
What to do instead
Before answering, label the stem: is it asking about a practice (a set of organisational resources), a value chain activity (what the organisation does), a component of the service value system, or a governance element? Learn the practice purposes verbatim enough to distinguish them from activities, and use a two-column recall sheet to drill the boundary.
Confusing the purpose of the service desk with incident management, or problem management with incident management, and selecting the wrong practice when the scenario describes logging, categorising, prioritising, and escalating user contacts.
In real organisations these are often performed by the same team, so candidates reason from their workplace rather than from the defined purposes in the ITIL 4 practice guidance.
What to do instead
Anchor each practice to a one-line purpose: service desk captures demand for service resolution and is the entry point and single point of contact; incident management restores service quickly; problem management reduces likelihood and impact of incidents by managing root causes and known errors. Then practise classifying scenario sentences by which purpose they serve, not by which team would do the work.
Mixing up the four dimensions (organisations and people, information and technology, partners and suppliers, value streams and processes) with the components of the service value system, or omitting the external factors that affect all four dimensions.
Both models are 'lists of four or five things' presented early in the syllabus, and candidates memorise the labels without the relationship between them, so they cannot tell which model a question is probing.
What to do instead
Build a single mental diagram: the service value system is the whole system (guiding principles, governance, service value chain, practices, continual improvement) and the four dimensions are the perspectives that must be considered for every component within it. Note that each dimension is affected by external factors such as regulation, technology change, and competitor activity, and rehearse a scenario where one dimension is under-addressed.
Reciting the seven guiding principles as a list but failing to apply the correct principle to a described situation, for example choosing 'focus on value' when the scenario is about starting small and iterating.
The principles are short and easy to memorise by name, so candidates stop at recall and never learn the behaviour each principle recommends or the tension it resolves.
What to do instead
For each principle, write one sentence on what it recommends and one example of a decision it would drive. Then work scenario questions by matching the described behaviour to the principle's recommendation, not to the words in its name. Pay particular attention to 'progress iteratively with feedback', 'collaborate and promote visibility', 'optimise and automate', and 'keep it simple and practical', which are the most frequently confused.
Describing continual improvement only as a retrospective or a periodic review, and missing that it is a recurring activity embedded in every value chain activity and supported by a defined model and method.
Candidates equate continual improvement with project post-mortems or annual service reviews from their own experience, and skip the improvement activity inside the value chain.
What to do instead
Learn that continual improvement is both a value chain activity and a practice, that it applies at all levels, and that it uses a structured model (identify the approach, define what to measure, gather data, analyse, present and use the information) plus improvement methods and techniques. In value stream diagrams, always show where feedback loops feed the improve activity.
Treating change enablement as a single approval gate run by a change authority, and asserting that all changes must go to a change advisory board.
This reflects legacy change management habits and older exam language; candidates do not register that ITIL 4 replaced change management with change enablement and made change models and delegated authority central.
What to do instead
Learn change enablement's purpose: maximise the number of successful service and product changes by ensuring risks are properly assessed, authorising changes to proceed, and managing the change schedule. Know that different change models apply to different change types, that authority is delegated as close to the change as sensible, and that standard, normal, and emergency changes each follow different paths. Answer questions by asking which model and which authority level fits the risk described.
Choosing 'automate it' or 'buy a tool' as the answer to information and technology questions without first addressing data quality, information management, or whether the technology fits the value stream.
Candidates associate the information and technology dimension with tooling and assume more automation is always the ITIL-aligned answer, ignoring the principle of optimise and automate and the need for accurate, available, and secure information.
What to do instead
When a stem mentions information or technology, check three things in order: is the information accurate, complete, and available to the right people; does the technology support the value stream and the four dimensions; and only then whether automation removes the waste. Remember that automation should follow optimisation, and that information management covers how information is created, stored, used, and disposed of, including security and compliance.
Ignoring the supplier and partner dimension and the practice of supplier management, answering resourcing questions as if all capabilities are built in-house, and failing to distinguish insourcing, outsourcing, and multi-sourcing arrangements.
Many candidates work in organisations with a narrow supplier footprint, so partner and supplier considerations feel abstract, and the terminology of service integration and multi-sourcing is unfamiliar.
What to do instead
Learn the purpose of supplier management (ensure the organisation's suppliers and their performance are managed appropriately to support seamless provision of quality products and services) and how it interacts with service level management and the value chain's engage and obtain/build activities. Practise scenarios where a service depends on several suppliers and identify who owns end-to-end performance and how integration is achieved.
Answering resource-planning questions by reciting capacity and availability definitions without linking them to demand, workload, and the service value system, so answers miss the point that resources must be planned against forecast demand and service commitments.
Candidates treat capacity and availability as technical monitoring topics rather than as planning practices with defined purposes, and they do not connect them to service level management and the plan activity.
What to do instead
Learn the purposes: capacity and performance management ensures services achieve agreed performance and satisfy demand in a cost-effective way; availability management ensures services deliver agreed levels of availability. Then link them to demand forecasting, service level agreements, and the plan and improve activities. In scenario questions, look for signals about forecast demand, performance targets, and cost constraints before selecting an answer.