brainstorm

To frame product discovery problems before planning, use structured questioning and verification to identify and reframe the core issue. This reduces misalignment and rework by ensuring teams understand the problem before proposing solutions.

The best way to structure brainstorming for ambiguous architecture decisions is applying a multi-phase discovery workflow. This guides teams from initial problem assessment through Socratic verification to a formal handoff with documented decisions and open questions.

Yes, you can use a phase-driven workflow to document early-stage product research. It structures thinking across sequential phases, captures decisions systematically, and ultimately produces a formal brainstorm document for clear handoff to planning.

Socratic verification surfaces risks during early-stage planning by applying structured questioning to explore multiple approaches. This process reveals hidden context from past work, validates assumptions, and highlights alternatives before committing to a specific solution.

You should not use structured problem reframing when the problem scope is already well-defined, fully validated, and unambiguous. In such cases, skipping the multi-phase discovery process avoids unnecessary overhead and allows teams to proceed directly to execution.