product-strategy

To validate a product feature hypothesis, you must answer six mandatory discovery questions covering user personas, problem definitions, and success metrics. This YC-inspired assessment framework ensures rigorous hypothesis validation before development begins.

The best way to prioritize MVP scope is using a four-tier scope classification model that categorizes features into Expansion, Selective, Hold, or Reduction modes. This CEO Scope Mode ruthlessly minimizes MVP scope and optimizes resource allocation.

You can determine if your team is solving a real problem by applying six forced YC-style questions to validate user personas and problem definitions. This structured evaluation prevents the build-first-think-later anti-pattern by ensuring evidence-based assessment.

You need a structured product strategy assessment before starting any new feature to ensure the team is solving a real problem and that the MVP scope is minimized. It is required when product management workflows demand rigorous hypothesis validation.

You optimize resource allocation by categorizing features into a four-tier scope classification model: Expansion, Selective, Hold, or Reduction modes. This CEO Scope Mode determines implementation readiness and directs resources toward validated initiatives.

The framework is limited to evaluating product feature viability through six mandatory discovery questions and a rigid four-tier scope classification. It should not be used when you need flexible, unstructured brainstorming or want to bypass strict hypothesis validation.