product-brainstorming

Structured product brainstorming uses a Frame–Diverge–Provoke–Converge–Capture workflow to expand the solution space. A thinking partner acts as an objective sparring partner to challenge assumptions, surface risks, and prevent premature convergence on ideas.

To frame a problem for product ideation, provide specific context and constraints. The session applies frameworks like How Might We, JTBD, and Opportunity Solution Trees to guide problem exploration and structure your thinking before generating solutions.

Yes, assumption testing is supported during early product discovery. The skill adapts to different modes including Problem Exploration and Assumption Testing, allowing you to stress-test thinking and surface risks in real-time before committing to a direction.

The best way to capture and converge brainstorming ideas is through a disciplined capture-and-converge workflow. After diverging to expand the solution space, the session converges by stress-testing the generated directions against your initial constraints and assumptions.

Yes, you must provide user-provided context and constraints before starting. Solution ideation requires a framed problem or opportunity to generate relevant brainstorm directions and effectively challenge your assumptions.

You should avoid using an AI thinking partner when you lack a clearly framed problem or cannot provide specific constraints. Problem framing requires user-provided context to generate diverse directions and challenge assumptions effectively.