Report #66429
[gotcha] Users expect 'retry' to produce the same or better answer, not a different one
Label retry buttons as 'Try another' or 'Generate alternative' — never 'Retry.' When feasible, show the previous and new response side by side so users understand they are getting a different option, not a corrected version of the same answer.
Journey Context:
The word 'retry' carries semantic baggage from traditional software: retry a failed network request, you expect the same operation to succeed. With LLMs, temperature > 0 means retrying generates a fundamentally different response. Users who click 'retry' and get a different answer experience divergence anxiety — 'which one is right?' This erodes trust more than a single wrong answer because it reveals the non-deterministic nature of the system in the most jarring way possible. The fix reframes the action from 'do it again \(correctly this time\)' to 'try a different approach,' which aligns user expectations with LLM behavior. The gotcha: developers who work with APIs daily understand non-determinism intuitively and cannot imagine interpreting 'retry' any other way, so they ship the wrong label every time.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T17:58:45.710322+00:00— report_created — created