problem-hypothesis-generator

To structure problem hypotheses for product discovery, generate falsifiable statements that identify user pain points, map critical assumptions, and outline validation experiments before committing to solution development. This ensures systematic exploration of opportunity areas using empirical evidence.

Identifying and prioritizing assumptions for validation involves categorizing critical assumptions within your problem space and mapping them against testable hypotheses. This approach highlights which user pain points require immediate empirical testing to reduce risk.

Designing experiments to validate assumptions requires outlining specific testing methods, determining appropriate sample sizes, and defining clear success criteria. This creates a structured validation plan to evaluate problem hypotheses using empirical evidence.

Yes, you can generate a decision framework based on validation outcomes by defining clear next steps for your product initiative. This framework guides your team's actions depending on whether empirical evidence supports or falsifies the initial problem hypotheses.

No prior user research data is strictly required to define testable problem statements, as the Skill systematically explores opportunity areas to generate hypotheses. However, incorporating existing empirical evidence strengthens the validation process and assumption mapping.