brainstorming

Turn rough ideas into fully formed designs by using structured, collaborative questioning that gathers context, constraints, and success criteria one question at a time. This incremental validation reduces ambiguity early in project lifecycles.

Scoping features and eliciting requirements is best done through one-question-per-message guidance, proposing multiple approaches with trade-offs, and breaking work into small sections for iterative validation.

Yes, structured brainstorming proposes multiple design approaches with explicit trade-offs. It guides ideas from initial context gathering through incremental validation directly into a written design proposal for documentation.

Collaborative ideation validates constraints and success criteria by handling project context one question at a time. This structured questioning ensures incremental validation before finalizing the written design output.

Document design explorations by completing the brainstorming process, which concludes with a written design output. This output captures validated context, constraints, and proposed approaches generated during the ideation session.

Avoid using structured brainstorming for concept design when projects lack time for iterative, one-question-per-message validation, or when fully formed requirements and detailed design specifications already exist.