brainstorming

Guided brainstorming clarifies ideas and requirements before design by providing a structured workflow with questions, alternative design options, and incremental validation prompts to align cross-functional teams. This prevents misalignment and rework.

The best way to run ideation with cross-functional teams is using a structured brainstorming workflow that discovers user intent, proposes 2-3 design approaches with trade-offs, and validates each step incrementally to align goals and constraints.

During early-stage feature planning, you compare design approaches by evaluating 2-3 proposed options with their respective trade-offs, selecting a recommended path, and validating choices through incremental questions before finalizing the design.

Yes, you can generate design documentation directly from a brainstorming session. Validated designs are documented automatically to docs/plans/YYYY-MM-DD-<topic>-design.md when continuing, ensuring ideas are captured as concrete design plans.

Guided brainstorming works effectively for early-stage product ideation by applying a structured process that shapes ideas into concrete designs, aligns goals and constraints, and incrementally validates proposed design options before implementation.