Framework

Product Discovery Framework

Whether a product idea or backlog item is solving a validated customer problem, before development time is spent on it.

Map the user journey

Where the actual friction lives for the customer today.

Separate validated from assumed

Split the backlog into what's evidenced and what's a guess.

Prioritise by ROI, not volume

Rank by expected value delivered, not by how long the list is.

Write the PRD only after validation

Requirements get documented once the problem is confirmed, not before.

When we use this

When a team is building features faster than it's validating them.