idea-refine

To refine a rough product idea, you restate it as a How Might We statement, answer sharpening questions, generate 5-8 variations, cluster them into 2-3 directions, and output a markdown one-pager with MVP scope. This structured divergent and convergent thinking turns vague ideas into actionable concepts.

Assumption testing and problem framing in product scoping involve stress-testing clustered idea directions for user value, feasibility, and differentiation while surfacing hidden assumptions. This process ensures your MVP scope targets the right validation targets before development begins.

You scope an MVP and create a Not Doing list by converging on a recommended direction after divergent ideation. The process outputs a structured markdown one-pager that explicitly defines what to build and what to deliberately exclude for sharper validation.

Yes, you can use divergent and convergent thinking for strategic evaluation of process ideas. The interactive flow restates any raw product or process idea as a How Might We statement, generates multiple variations, and stress-tests clustered directions for feasibility and user value.

The best way to turn vague ideation into actionable MVP planning is through an interactive flow that collects success and constraint inputs via sharpening questions. It generates 5-8 meaningful variations, clusters them into distinct directions, and produces a one-pager after confirmation.

You need structured idea refinement when you have early ideation, feature scoping, or plan stress-testing requirements but lack sharper positioning, constraints, and validation targets. It prevents premature building by surfacing hidden assumptions and defining a deliberate Not Doing list.