idea-refine

To turn raw product ideas into build-ready concepts, apply structured divergent and convergent thinking to restate the problem, generate high-quality variations, and stress-test directions. This process outputs a markdown one-pager with an MVP scope and a not-doing list.

The best way to frame a problem for product discovery is by restating your raw idea as a crisp How Might We question, then asking 3-5 sharpening questions to generate 5-8 high-quality solution variations using multiple ideation lenses.

To stress-test assumptions during concept validation, cluster resonating ideas into 2-3 distinct directions and evaluate them against user value, feasibility, and differentiation criteria to surface hidden assumptions before committing to an MVP.

Yes, you can use this approach to define an MVP scope and not-doing list by converging on the strongest direction and generating a build-ready markdown one-pager that explicitly details what to build and what to exclude.

The limitation of structured idea refinement is that it relies entirely on your raw project inputs and iterative questioning, meaning it cannot generate actionable MVP scope if the initial concept lacks basic context or clear user goals.

Idea refinement works for evaluating multiple solution directions by generating 5-8 candidate variations, clustering them into 2-3 distinct directions, and then applying critical convergent evaluation to select the strongest build-ready concept.