Organizations, service providers and service consumers

Every service involves at least two parties: one that provides and one that consumes. ITIL gives these parties precise names and breaks the consumer side into three distinct roles: customer, user and sponsor. Confusing these roles is one of the most common reasons services disappoint. A service can satisfy the people who pay for it while frustrating the people who use it, or delight users while failing the sponsor who must justify its cost. This lesson defines organizations, service providers and service consumers, explains the customer, user and sponsor roles, and shows how one organization can play several roles at once.

Organizations

ITIL defines an organization as a person or a group of people that has its own functions with responsibilities, authorities and relationships to achieve its objectives. The definition is deliberately broad. An organization can be:

• A single person, such as a freelance consultant or a customer buying a phone plan.
• A team or department, such as the payroll team or the IT operations group.
• A whole company, charity or government department.
• A group of organizations working together, such as a joint venture or a consortium.

Organizations vary in size and complexity, and in their legal form, from sole proprietors to multinational corporations and public bodies. What they share is that they have objectives and the responsibilities and authority to pursue them. In a service relationship, organizations take on the roles of provider and consumer.

Service providers

A service provider is the role an organization plays when it provides services to consumers. Being a provider is a role, not a type of organization. An internal IT department is a service provider to the rest of the company. A cloud company is a provider to its customers. A government agency providing passports is a provider to citizens. A single developer who maintains a small library for others is, in a sense, a provider too.

To provide services well, a provider needs a clear understanding of who its consumers are, what they want to achieve, what other parties are involved, and what its own role is. ITIL stresses that providers should look beyond the immediate consumer to the wider network of stakeholders, including suppliers, partners and regulators.

Service consumers

A service consumer is the role an organization plays when it receives services. Like the provider role, it is a role rather than a type of organization. The same organization can be a consumer of some services and a provider of others. A hospital consumes cloud, electricity and medical supply services while providing health services to patients. An IT department consumes services from telecom and software suppliers while providing services to employees.

Being a consumer is more complex than it first appears. ITIL identifies three roles within the consumer side, and in many organizations they are played by different people with different interests.

Customer, user and sponsor

The three consumer roles are:

• Customer: a person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
• User: a person who uses services.
• Sponsor: a person who authorizes budget for service consumption.

In a household buying a home internet plan, one person might hold all three roles: they decide what speed they need (customer), use the connection (user) and pay the bill (sponsor). In a large company buying a customer relationship management system, the roles are usually split:

• The head of sales is the customer, defining what the system must do and answering for whether it helps the sales team hit its targets.
• Hundreds of sales representatives are users, working in the system every day.
• The chief financial officer is the sponsor, approving the budget and expecting a return on it.

Each role judges the service by different criteria. Users care about ease of use, speed and reliability in their daily work. Customers care about whether the service supports the outcomes they are accountable for. Sponsors care about cost, value for money and alignment with the organization's plans. A provider that listens to only one of these roles will build a service that disappoints the others.

When roles conflict

Conflicts between consumer roles are normal. A sponsor may push for the cheapest option, while users need a more expensive tool that saves them hours each week. A customer may specify a long list of features that users never use, adding cost and complexity. Users may request changes that make their own work easier but undermine the outcomes the customer is accountable for, such as skipping a compliance step.

Service providers can help by making the trade-offs visible. For example, showing the sponsor the cost of user time wasted by a slow tool can change the conversation from "cheapest license" to "lowest total cost". Bringing users into requirement discussions helps customers avoid specifying features nobody needs. Relationship management, covered in lesson 7, is the practice that keeps these conversations going.

One organization, many roles

Because provider and consumer are roles, organizations play several at once. A regional bank, for example, consumes cloud hosting, card processing and software licenses from suppliers. It provides banking services to retail customers and small businesses. Inside the bank, the IT department provides services to branches and head office, which in turn consume them. A single employee might be a user of the bank's internal email, a customer for a new analytics tool their team requested, and a sponsor for a small budget line.

Recognizing these chains matters because a problem in one link often surfaces somewhere else. If the cloud company has an outage, retail customers cannot use mobile banking, and they blame the bank, not the cloud company. Lesson 8 returns to these chains and the wider service ecosystem.

Internal and external consumers

Some practitioners treat internal consumers (colleagues in the same organization) as less important than external, paying customers. ITIL encourages the opposite habit: apply the same service thinking to both. Internal services enable the external ones; a slow internal purchasing service can delay a product launch just as surely as a supplier failure. The differences are in governance and funding. Internal services are often funded centrally or charged back to departments, and their "customers" cannot always switch to an alternative provider. That makes listening to them even more important, because dissatisfaction may not show up as lost business.

Roles in exam scenarios

Foundation questions often describe a scenario and ask which role a person plays. A reliable approach is to ask three questions in turn. Does this person define the requirements and answer for the results? Then they are the customer. Do they use the service in their work or life? Then they are a user. Do they approve the money? Then they are the sponsor. If the scenario describes one person doing all three, as with an individual buying a personal phone plan, the answer is that one person holds all three roles. Watch for distractors such as "service owner" or "supplier", which are real roles but belong to the provider side or to the supply chain rather than to the consumer.