Definition

Intent satisfaction is whether the resulting state of a user's activity matches the sought state their intent is directed toward, evaluated by the user at each scale their activity produces resulting states.

A judgment the user makes

The user holds a sought state — the condition they're moving toward — and their activity produces a resulting state, where the transition actually ends. Intent satisfaction is the alignment between the two: did what happened match what the user came for.

The user runs this evaluation, continuously, comparing each resulting state against the intent that brought them. It's the user's verdict that determines whether intent was satisfied, not the provider's account of what the offering delivered.

Three scales of evaluation

User activity produces resulting states at more than one scale at once, and the user evaluates intent satisfaction at each:

• Interaction scale — each discrete action produces an immediate resulting state. Clicking a button, submitting a form: produced in seconds, evaluated near-instantly against what the action was expected to do.
• Session scale — a bounded period of engagement produces a session-level resulting state. The user came to do something; by the end of the session it's done, partially done, or not done. Evaluated in minutes to hours.
• Lifetime scale — the long-arc relationship produces resulting states at the scale of the user's life with the offering in it. The user hired the offering for a larger outcome; over months or years, that outcome is being produced or not.

These scales run in parallel, not nested. Every interaction sits inside a session and every session inside a lifetime, and each scale carries its own intent and its own resulting state to be checked against it.

Every scale needs its own satisfaction

Because each scale carries its own intent, satisfaction at one scale doesn't transfer to another, and failure at any one degrades the experience on its own. A session can accomplish exactly what the user came for and still be built from interactions that confused or misdelivered along the way, leaving an outcome that worked but felt unreliable.

A session can also fail outright inside a relationship that might have produced the long-arc outcome eventually — and the user exits before that larger scale has time to materialize, which is one of the patterns behind starting churn. No scale covers for another; the provider has to produce satisfaction at each one the user experiences.

Small events predict large outcomes

The scales also inform each other. Small-scale resulting states do double duty: the user reads them as evidence about whether the larger scales will be satisfied. A failed interaction carries forward — the user treats it as a data point about whether the session and the lifetime will go well, not only as local friction.

Each small failure lowers the user's confidence that the larger outcome will arrive, and continuation becomes a worse bet as failures accumulate. This is what gives early-period and small-scale work leverage out of proportion to its size: the first interactions a user has are setting their prediction about everything that follows.

Example

A user sending their first invoice through a new billing tool holds a clear sought state — the invoice goes out. Uploading a logo fails twice; the address field rejects valid input.

The session might still end with a sent invoice. But each failed interaction has already operated as evidence that the larger task won't go smoothly. By the third failure the user is discounting the tool's chances before the session even resolves, and a working outcome may not be enough to undo the prediction the early interactions set. Interaction-scale failures degraded confidence in the session-scale outcome, independent of whether the session eventually succeeded.

See also

• Route efficacy
• Affordance
• Value milestone