brainstorming

Clarify ambiguous feature requests by asking focused questions to uncover the purpose, audience, constraints, and desired outcomes. This requirement discovery process narrows vague ideas into a specific problem and solution direction through one-at-a-time questioning.

Explore trade-offs by comparing 2-3 viable approaches with clear pros, cons, and best-fit scenarios. This approach exploration validates explicit assumptions and helps select a well-scoped direction when multiple solutions are possible.

Turn a rough product idea into a structured handoff by capturing the chosen direction in a concise design summary. This design capture ensures the problem, users, constraints, and success criteria are clear and ready for planning.

Yes, requirement discovery is designed exactly for undefined scope. It supports early-stage product ideas by asking one question at a time until the problem, users, constraints, and success criteria become clear.

Requirement discovery works by asking one question at a time to validate explicit assumptions about the idea's purpose and audience. This iterative questioning continues until the problem, users, constraints, and success criteria are fully clear.

Avoid structured brainstorming when requirements are already clear, success criteria are defined, and a single valid approach exists. This process is specifically for unclear requirements, multiple possible solutions, or undefined scope.