idea-refine

To turn a raw product idea into a shippable one-pager, you need structured divergent and convergent thinking. This process refines vague concepts by defining target users, success criteria, and MVP scope while making hidden assumptions explicit through sharpening questions.

A How Might We framing restates a raw idea into an actionable question to structure product ideation. It enables divergent thinking to generate 5-8 grounded variations using multiple lenses like inversion, constraint removal, and audience shift for comprehensive concept exploration.

Prioritizing MVP scope and surfacing assumptions requires convergent evaluation that stress-tests clustered directions. This approach evaluates user value, feasibility, and differentiation while explicitly listing key assumptions, risks, and a Not Doing list to define buildable boundaries.

You can use idea refinement for process improvements, new concepts, and feature directions. The methodology applies broadly to any ideation session where assumptions must be surfaced and prioritized into an MVP-ready scope with explicit requirement attribution.

An MVP-ready product brief one-pager should include a problem statement, recommended direction, lightweight requirement attribution, assumption validation plan, MVP scope, explicit Not Doing trade-offs, and open questions to guide immediate build planning.

Idea refinement optionally scans project context when available but does not strictly require it. The process can refine half-formed ideas by asking sharpening questions to define target users and constraints, saving the final markdown artifact into the project's canonical ideas path.