Begin with the outcome, not the screen
When someone asks for a dashboard, login page, checkout, or approval flow, the visible interface is only one part of the requirement. First clarify what people must accomplish, who is allowed to do it, and what should be true when the journey succeeds.
This keeps discovery grounded in the product outcome. It also prevents an agent from treating a familiar screen pattern as permission to invent business rules.
A useful question reduces uncertainty and teaches the user why the answer matters.
Make every question answerable
Technical questions become easier when they include a plain-language explanation and a concrete example. Instead of asking which authentication protocol to use, ask how people should enter the product and explain the tradeoff between a password, magic link, and an existing identity provider.
Offer a recommended default based on the stated product. The user can accept it quickly or replace it with something more appropriate.
- Explain the visible consequence.
- Give two or three realistic choices.
- Recommend one default and state why.
- Always allow a short custom answer.
Stop when the contract is testable
Discovery is complete when the requirement describes actors, states, rules, exceptions, constraints, and acceptance evidence clearly enough that UX and engineering can proceed without silently reopening fundamental decisions.
Unresolved choices can remain, but they must be visible. A named assumption is safer than a confident implementation built on a guess.