User Satisfaction Depends on Delivered Quality Relative to Expectations

Usability researcher Jakob Nielsen argues that fluent AI writing makes users over-trust its facts, so teams must design user expectations as carefully as screens.

Jakob Nielsen writes UX Tigers, a blog on usability research. He argues that users judge a product against what they expected before first use, so the same AI output can delight one person and disappoint another. He warns that polished AI prose makes users assume the facts are equally reliable.

• Nielsen calls the gap between delivered and expected performance the expectation gap, and he says design, engineering and marketing all move it.
• He calls the shortfall between promises and delivery expectation debt, and he says one broken promise outweighs several kept ones.
• He recommends showing what the system checked, what it inferred and what still needs review, and showing typical results instead of best-case demonstrations.
• He suggests asking users what they expect before first use and comparing their experience afterwards.

Product and design teams can treat the claims around an AI feature as part of the design, reviewed alongside the interface. Nielsen offers principles, not a team's measured result.

Derived by Working Surface from the article; more in the Playbook. Source line: Conversational polish can therefore invite more delegation than the system's reliability warrants.

2 October 2026: teams building with AI agents are deciding in advance, and writing down, where the agent stops and a person checks: in product code, in what the product promises users, and in visibility of agent behaviour.