se-brainstorm

Structured brainstorming for software projects uses a guided, phase-based conversation to surface goals, constraints, and success criteria. This process explores options and aligns stakeholders before you draft a requirements document.

Yes, you can use guided brainstorming for non-software product ideas by engaging a universal-brainstorming mode. This mode handles non-software domains by guiding users through phases and decision criteria to surface what to build.

The best way to align stakeholders on product scope is through one-question-at-a-time collaboration. This guided approach surfaces assumptions, constraints, and success criteria to prevent unclear scope and missed decisions.

To determine what to build, you can use a phase-driven flow that guides you from Phase 0 to Phase 4. This structured brainstorming surfaces a synthesis that informs the requirements doc and planning phase, including scope boundaries.

No, structured brainstorming does not replace the requirements planning phase. It precedes planning by outputting a synthesis of key questions to resolve and scope boundaries, which directly informs and prepares the requirements capture.