office-hours

To evaluate if a new product idea is worth pursuing, you need to surface core assumptions and clarify scope before committing resources. This framework guides you from problem clarity to MVP boundaries by exposing risky premises and testable hypotheses.

Yes, you can define MVP scope for a specific feature using builder mode. This mode handles incremental improvements by mapping feature boundaries and success criteria, while startup mode focuses on new 0→1 product directions.

The best way to articulate risky assumptions during concept evaluation is through a guided workflow that prompts you to define testable hypotheses. This process yields a structured product-thinking document detailing core risks and required scope.

To map MVP boundaries for a startup direction, trigger the evaluation flow and describe your idea in one sentence. The framework applies startup mode to guide you through premise validation, resulting in a concise document with defined boundaries and success criteria.

Startup mode focuses on 0→1 products for entirely new directions, while builder mode evaluates specific features for incremental improvements. Both modes output a product-thinking document that clarifies scope and drives decision making.

You should not use a structured framework for premise validation if your idea lacks a clear problem statement or if you are already past the early-stage concept evaluation phase and have committed resources to building the MVP.