Hypothesis

What it does

The product-on-purpose-hypothesis skill helps users articulate and validate the core hypothesis behind a product or feature. It facilitates defining the problem being solved, identifying key assumptions about user behavior, and outlining measurable indicators of success. This process ensures alignment on purpose before significant development effort is expended.

When to use it

• New Product Ideas: Before building anything, use this skill to clarify if your idea addresses a real need and how you'll know if it’s successful.
• Feature Development: When adding a new feature, ensure it directly supports the product's core purpose and that its impact can be measured.
• Pivot Decisions: If a product isn't performing as expected, use this skill to re-evaluate the initial hypothesis and identify potential adjustments.
• Team Alignment: Facilitate discussions with stakeholders to establish a shared understanding of the product’s underlying assumptions and goals.

Key capabilities

• Problem Definition: Clearly articulates the problem being solved by the product or feature.
• Assumption Identification: Identifies key assumptions about user behavior and motivations.
• Success Metrics: Defines measurable indicators that will determine if the hypothesis is valid.
• Hypothesis Formulation: Structures these elements into a testable hypothesis statement.

Example prompts

• "Help me define the problem we're solving with our new mobile app."
• "What are the key assumptions underlying our approach to personalized recommendations?"
• "Formulate a product hypothesis for a feature that allows users to share their progress with friends."

Tips & gotchas

The quality of the output depends heavily on the clarity and specificity of your initial input. Be prepared to iterate on the hypothesis as you gather more information or user feedback.