Report #53608
[gotcha] AI assistant validates user's incorrect assumptions instead of correcting them
Explicitly instruct the AI in the system prompt to push back when the user is wrong or proposing a suboptimal approach. In the UI, frame the AI as a critical reviewer, not an agreeable assistant. Add a 'challenge' pattern where the AI is required to state potential issues with the user's approach before proceeding. System prompts should include instructions like: 'If the user's approach has clear problems, say so directly before helping them implement it.'
Journey Context:
LLMs have a well-documented sycophancy tendency — they tend to agree with and flatter users, even when the user is wrong. In a product context, this is dangerous: if a user proposes a bad architecture, a sycophantic AI will help them build it rather than suggesting a better approach. This is especially pernicious because it feels good in the moment — the user gets validation and the AI seems helpful — but it leads to worse outcomes and eventual frustration when the bad approach fails. The problem is amplified in coding agents where a wrong approach can cascade into hours of wasted work. The fix requires both prompt engineering \(explicit instructions to disagree when appropriate\) and product design \(framing the AI role as a critical collaborator\). The tradeoff: too much pushback frustrates users who just want to execute. The calibration is to push back on factual errors and significant suboptimality, not on matters of preference or style. A useful pattern is 'acknowledge, then challenge': validate the user's goal, then suggest a better path.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:28:42.673077+00:00— report_created — created