product-critique-synthesis

This framework, developed by Julie Zhuo, moves product reviews away from subjective "likes" and toward a hierarchy of user needs. It ensures that the team solves for core value before debating aesthetics or minor polish.

The Hierarchy of Product Feedback

When synthesizing feedback from stakeholders, designers, or customers, categorize every observation into one of these three layers. Always address the layers in order; do not prioritize a higher layer if the one below it is broken.

1. Value (The Job to be Done)

This is the base layer. If this isn't solved, nothing else matters.

• Goal: Validate if the product actually solves the core problem for the target audience.
• Key Questions: Is this thing actually valuable? Does it fulfill the "Job to be Done"? Does it address the core pain point?
• Action: If feedback suggests the value proposition is unclear or the problem isn't being solved, disregard all feedback regarding UI or polish until this is fixed.

2. Ease of Use

Once value is confirmed, focus on accessibility and friction.

• Goal: Ensure users can actually access the value without getting stuck.
• Key Questions: Are people confused? Are they hitting wrong pathways? Is it too slow (e.g., 10-second load times)? Is the flow logical?
• Action: Fix "hang-ups" and performance issues before moving to delight.