Report #39626
[gotcha] Same input producing different AI outputs across sessions erodes user trust in software-like products
For features where users expect deterministic software behavior \(settings, calculations, configurations, data lookups\), cache and pin the first acceptable response. Use the model's seed parameter where available to maximize reproducibility. Only re-generate on explicit user action, and surface the non-deterministic nature explicitly \(e.g., 'Here's one way to approach this — ask again for alternatives'\). For exploratory or creative features, frame output as 'a perspective' or 'a suggestion' rather than 'the answer.'
Journey Context:
Users have decades of conditioning that software is deterministic: same button, same result. When an AI product gives different answers to the same question on different days, users don't think 'the AI is exploring the solution space' — they think 'the product is broken or unreliable.' This is especially acute in professional tools \(code generation, data analysis, legal research\) where reproducibility is a core expectation. The counter-intuitive insight: making the AI less dynamic — caching responses, pinning outputs, reducing temperature — often increases perceived quality even though it reduces the AI's capability. Users would rather have a consistently good answer than a sometimes-great-sometimes-different answer. The seed parameter helps but is not a complete solution — it reduces variance within a single model version but doesn't help across model updates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T20:59:17.501772+00:00— report_created — created