2.6 Products, Services and Service Offerings

Products, Services, and What Providers Actually Package

The final piece of the key-terms vocabulary distinguishes a product from a service and breaks down what a service offering contains. Version 5 also formalises digital products and services and a set of experience concepts, so this section covers the terms most likely to appear as 'which of these is a good / a service action / a digital service' questions.

What is a product?

A product is a configuration of an organisation's resources designed to offer value to a consumer. The key words are configuration and resources. A product is assembled from the organisation's resources, and those resources map to the four dimensions: people, information and technology, value streams and processes, and partners and suppliers. A streaming platform, for example, is a product configured from servers and code (information and technology), engineers and support staff (people), the workflows that keep it running (value streams and processes), and CDN and payment vendors (partners and suppliers).

Consumers rarely see the whole product; providers usually expose only the parts relevant to a particular consumer group, packaged as offerings.

Product versus service

A service (from 2.1) enables value co-creation by facilitating outcomes without the consumer managing specific costs and risks. The contrast the exam draws is: a product is a configuration of resources, while a service is the means of enabling value co-creation using some of those resources. Products can, in principle, have ownership transferred; services are consumed through an ongoing relationship. One product can underpin several service offerings aimed at different consumer groups.

The Service Offering and Its Three Components

A service offering is a description of one or more services designed to address the needs of a target consumer group. An offering is built from three component types, and distinguishing them is a classic exam task:

• Goods — items where ownership is transferred to the consumer, who then takes responsibility for their future use. Example: a configured laptop handed to a new employee.
• Access to resources — the consumer is granted access under agreed terms, but ownership stays with the provider. Example: access to a managed analytics platform or a licensed application.
• Service actions — actions performed by the provider to address a consumer's need, on request or as agreed. Example: a service-desk agent resetting a password.

The most common trap is confusing access to resources with goods. If ownership transfers, it is a good; if the consumer only gets to use something the provider still owns, it is access to resources.

Digital Products and Digital Services

Version 5 makes the digital dimension explicit. A digital product is the configured asset itself (the app, the platform) that a provider builds and offers. A digital service is one delivered through digital channels (an online booking flow, a managed API) where the consumer interacts without owning the underlying platform. The exam tests whether you can tell a service relationship (ongoing consumption of a digital service) from a product sale (transfer of a digital product).

A cloud payroll application employees log into to view payslips is a digital service; the packaged application a vendor licenses out could be treated as a digital product.

Experience: UX, CX, and Human-Centred Design

Version 5 adds experience to the key-terms vocabulary because how a service feels affects whether its outcomes are perceived as valuable.

• User experience (UX) is the experience of the person directly using the service: usability, friction, task completion.
• Customer experience (CX) is the experience of the person who commissions or buys the service across the whole relationship, including outcomes and contractual dimensions.
• Because the user and the customer can be different people (see section 2.3), UX and CX can diverge, and a service can delight users while frustrating the customer, or vice versa.
• Human-centred design means designing products and services around people's real needs, behaviours, limitations, and context of use, rather than around internal convenience.

Version 5 also links sustainability and trust to experience: consumers weigh long-term environmental and social impact, and their willingness to rely on a digital service depends on trust. These 'softer' terms still remove or add perceived value, tying this section back to 2.5.

Common exam traps

• Goods versus access. Ownership transfer is the deciding test. Access to a platform the provider still owns is access to resources, not goods.
• Product versus service. A product is a configuration of resources; a service enables value co-creation. Do not call a configured resource set a 'service'.
• UX versus CX. UX is the direct user's view; CX is the broader customer's view across the relationship. They belong to potentially different roles.

Tie it back to value

Products, offerings, and experience all feed the value picture from earlier sections. A product supplies the configured resources; a service offering packages goods, access to resources, and service actions into something a target consumer group can obtain; and the experience of using it, including UX, CX, trust, and increasingly sustainability, shapes whether the resulting outcomes are perceived as valuable.

When a question mixes these terms, decide first whether it is asking about the configured resources (a product), the described package and its three components (a service offering), or the felt quality of use (experience), and the right answer usually follows directly from that one distinction.