User

Definition and neighbouring roles

A user is whoever performs the task in the product. This is the definition adopted by the guide. Read the User glossary entry with the task as the reference point.

The neighbouring roles have different definitions. The buyer signs the contract and answers for the budget. The operator sustains the product through support, implementation or administration. An internal customer is an area of your own company that uses the product to serve the external customer. Identify the user by task performance, not by budget responsibility or product support.

Where the term matters in practice

The distinction matters when interpreting requests. The guide states that users usually want fewer steps and less waiting. Buyers usually want control, predictability and proof of compliance. These are usual concerns, not replacements for the role definitions.

Connect the user to the context of use: the physical and temporal conditions in which the task happens. Examine the environment, device, time available and interruptions. A useful customer profile describes observed behaviour around a task: who performs it, how often, under what pressure and with what consequence when it goes wrong.

Use that profile to inform choices between competing requests. If both requests are legitimate and the data does not settle the choice, the guide directs the decision back to the product’s stated direction.

Applying the distinction in CPM-E preparation

When studying a scenario, ask who performs the task, who signs and answers for the budget, and who sustains the product. Then connect the task to observed behaviour and conditions of use.

The guide treats preparation as developing judgement, not merely memorising definitions. Use this distinction alongside the Certified Product Manager Enterprise certification page when organising your CPM-E preparation.