2.3 Stakeholders and Roles

Two Sides, and Three Roles Inside One of Them

Section 2.2 established that a service relationship is a cooperation between a service provider and a service consumer. This section defines those two parties precisely and then breaks the consumer side into the three roles the exam loves to test: customer, user, and sponsor. Getting these distinctions right is worth several marks, because at least one question almost always presents a scenario and asks which role a named person is playing.

Service provider and service consumer

A service provider is the organisation, or role, that supplies products and services to consumers. In a given relationship, one party takes on the provider role. A service consumer is the organisation, or role, that receives or consumes services. Both are roles rather than fixed organisation types: the same organisation can be a provider to its customers and a consumer of its own suppliers at the same time. An internal IT department, for instance, is a provider to the business units it serves and a consumer of the SaaS vendors and network carriers it relies on.

Because these are roles, avoid assuming 'provider' always means an external company and 'consumer' always means an end user.

The Three Consumer-Side Roles

ITIL splits the generic service consumer into three specific roles. They are distinct responsibilities, and the same individual can wear more than one hat.

• Customer. The person or group that defines the requirements for a service and takes responsibility for the outcomes of service consumption. The customer is the 'what do we need and did we get it' role.
• User. The person or group that uses the service day to day. The user is the 'hands on the keyboard' role.
• Sponsor. The person or group that authorises the budget for service consumption. The sponsor is the 'who pays' role.

A worked example

Imagine a company buying a cloud expense-management service. The finance director decides the money can be spent and signs off the contract, so she is the sponsor. The head of finance operations specifies which features and service levels are required and will be judged on whether expenses are processed accurately and on time, so he is the customer. The employees who log in every week to submit receipts are the users. Three different people, three different roles. Now change the scenario to a sole trader who chooses the tool, pays for it, and uses it herself: one person holding all three roles at once.

The roles are still distinct even when combined in one person, which is exactly the subtlety the exam probes.

Why the Distinctions Matter

Separating these roles is not academic. Their interests can conflict, and good service management keeps all three satisfied. Users may want more features and speed; sponsors may want lower cost; customers must balance both against the outcomes they are accountable for. A service that delights users but blows the sponsor's budget, or hits budget but fails the customer's required outcomes, is not succeeding. This is also why user experience (the user's view) and customer experience (the customer's view) can diverge, a point developed in section 2.6.

Beyond the consumer side: other stakeholders

Beyond provider and consumer, ITIL recognises a wider set of stakeholders who have an interest in the relationship, including employees, shareholders, partners and suppliers, governments and regulators, and society at large. Version 5's emphasis on sustainability widens this further, since environmental and social stakeholders can be affected by how a service is designed and run. For Foundation, focus on the provider, the consumer, and the three consumer-side roles, but be ready to recognise that value is co-created among a broader stakeholder set.

Common exam traps

• Customer versus user. The customer defines requirements and owns outcomes; the user merely uses the service. A question describing someone who sets requirements and is judged on results is pointing at the customer, even if that person never logs in.
• Sponsor is about money, not usage. The sponsor authorises budget. If a scenario stresses who approved the spend, that is the sponsor, regardless of whether they use the service.
• One person, several roles. Do not assume the three roles must be three different people. In small organisations they frequently collapse into one, yet each role's responsibility still exists.
• Provider and consumer are roles. The same organisation can be both, in different relationships, at the same time.

One more scenario

A hospital contracts a clinical-records platform. The chief medical officer signs off the funding, making her the sponsor. The clinical-systems lead specifies the required features and safety outcomes and is accountable for them, making him the customer. The nurses and doctors who chart patient notes are the users. If a question then says the nurses find the interface slow, that is a user concern; if it says the required audit outcomes were not met, that is a customer concern; if it says the budget was exceeded, that is a sponsor concern.

Mapping each complaint back to the role it belongs to is a fast way to answer role questions correctly, and it reinforces why keeping all three roles satisfied at once is the real mark of a well-run service.