Product Loop

Aligns development teams directly with user value metrics instead of feature checklists, minimizing feature bloat.

Input

An initial feature idea or raw user problem statements.

Output

A validated target problem definition and a scoped feature requirement doc (PRD).

1. Identify the Core User & Problem

Start by mapping out who the target users are and the specific value proposition we are testing. Answer: What is the user trying to achieve, and why can't they do it today?

2. Define the Minimum Usable Product (MUP)

Differentiate between 'nice-to-have' features and the absolute minimum set of capabilities needed to solve the core problem. Focus heavily on utility over aesthetics at this stage.

3. Measure & Iterate

Ship to a subset of users, observe their interaction behaviors (not just feedback surveys), and loop their usage data back into product planning.