Originally written in French. Translated by AI — the meaning has been preserved, not the prose.
Short definition
The level of classification of customer feedback at which the customer expresses a business objective, an organizational constraint, an operational priority, a risk or an ambition to transform — without yet talking about usage or product.
Full definition
In its ordinary sense, "business stake" designates anything that matters to an organization's activity, including its processes and its tools. The acceptation is broad and quickly blurs into "important subject".
In the classification of customer feedback worked on here, the term designates a precise tier: the one where the customer talks about their activity and not about their tool. "Harmonize practices across several teams", "reduce a compliance risk", "improve steering", "absorb growth without hiring more" are business stakes. None mentions a screen, a feature or even an act of work.
A business stake remains valid if the product is replaced by another: it belongs to the customer, not to the solution.
Usage in the field
This level feeds trade-offs of product strategy and segment — which accounts to serve, which promise to keep — rather than the roadmap or the backlog. It comes into play in qualifying an account, in preparing a product committee and in writing a positioning.
Synonyms and variants
Business stake, business objective, driver, the customer's reason to buy.
Not to be confused with
- Use case / JTBD — what the customer is trying to accomplish in their work, expressed as an action: qualifying an incident, comparing several entities. The stake says why the activity matters, the use case says which action carries it.
- Product capability — what the tool should make possible: configuring alerts, managing rights. The vocabulary there is already that of the solution.
- Local friction point — a screen, a filter, a precise behaviour judged annoying.
Examples
"Absorb growth without hiring more" — the customer asks nothing of the product, they state the constraint they operate under.
"Reduce a compliance risk" — an objective that pre-exists the product and would outlive it.
Ambiguities / debates
The border with the use case is debatable when the customer phrases their objective with an action verb: "steer my sites" can be read as an ambition to steer or as the action of comparing several entities. The criterion retained here: if the sentence describes a sought state for the activity, it is a stake; if it describes an act of work performed, it is a use case.