OtherIntermediateClaude
In discovery, 'seamless' is a clue, not a requirement
Words like simple, fast or intuitive hide constraints: ask what would make it NOT be that way and write it down before moving on.
Listen, translate into requirements, assumptions and constraints, and note them down. Each item goes into a row: what the stakeholder said, the implicit constraint, the architecture decision it forces and the assumption to confirm. Finish the round of questions before proposing a design: a convincing sketch makes the constraints stop showing up.
Example
Question: "What would make this NOT feel seamless?" Typical answer: "waiting more than 2 s" → p95 ≤ 2 s; "technical errors" → safe failure with no internal details.