brainstorming

Structured brainstorming clarifies what to build by enforcing phased thinking, starting with assessing requirement clarity through signals like ambiguity and conflicting viewpoints. It guides decision-making by asking targeted questions to uncover intent, users, and constraints before design.

The best way to explore approaches during feature ideation is to propose 2-3 concrete options, each with explicit pros, cons, and best-use scenarios. This structured comparison ensures you evaluate trade-offs before committing to a specific implementation path.

Your project needs brainstorming if it exhibits signals like requirement ambiguity, lack of constraints, or conflicting stakeholder viewpoints. Phase 0 quickly assesses these clarity signals to determine if structured ideation is necessary before moving forward.

During product planning, avoid jumping to implementation details too early, overcomplicating initial designs, and assuming requirements without validation. Applying YAGNI principles and incremental validation helps steer multi-stakeholder ideation away from these anti-patterns.

Capture brainstorming outcomes by logging decisions, findings, and constraints to persist the session's results. For handoff, present explicit options to proceed to planning, refine the approaches, or pause the project until more information is available.