When we consider building effective teams and roles and competencies, what is TRUE about job?

A 'job' is a formal position within an organization's structure assigned to an individual. The ITIL framework distinguishes this from a 'role'. A single person holding one job title, such as 'IT Operations Analyst', may be required to perform several different roles as part of their duties. For example, they might act in the role of an incident resolver, a change implementer, and a problem analyst at different times. This distinction is crucial for building flexible and effective teams where responsibilities are clearly understood beyond just a job title.

A. This describes a historical trend in IT job design, focusing on technical silos, rather than defining what a job is in the modern, role-based context of ITIL 4.

B. This is the official ITIL 4 definition of a 'role', which is a set of responsibilities and authorizations, not a 'job'. A person in one job can have many roles.

D. This statement is conceptually confused. A value stream or service is contributed to by several departments; a job is a position typically held by one person within a department.

1. AXELOS. (2020). ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office).

Section 4.1.2.1 'Jobs and roles': "A job is a position within an organization that is assigned to a specific person. As part of their job, a single person may fulfil many different roles." This directly supports option C.

Section 4.1.2.1 'Jobs and roles': "A role is a set of responsibilities, activities, and authorizations granted to a person or team, in a specific context." This directly refutes option B by defining it as a 'role'.

Section 4.1.2.2 'Competencies': Discusses the shift from purely technical competencies (I-shaped) to broader skills (T-shaped), showing that option A is an outdated model, not a core definition.