product-lens-reviewer

To review a product planning document for misaligned goals, you challenge the core premise and evaluate whether proposed work matches stated objectives. This surfaces disconnects between strategic goals and feature scoping.

Premise challenge in product scoping asks if you are solving the right problem, defining the actual outcome, and what happens if you do nothing. You need this process during strategic planning to reveal flawed problem framing before development begins.

To assess if a roadmap creates future rigidity, perform a trajectory check to evaluate whether the plan moves toward the system's natural evolution. This analysis identifies strategic plans that lock teams into inflexible implementation paths.

The best way to find cheaper implementation alternatives during feature scoping is to surface paths that deliver 80% of value at 20% of cost. This analysis identifies efficient routes within your planning documents to optimize resource allocation.

Yes, this planning review approach works for strategic roadmap critiques across product teams. The protocol applies broadly to feature scoping and roadmap reviews by evaluating goal-requirement alignment and prioritization coherence in any planning document.

You should not use a structured critique for product planning reviews when a document covers operational execution rather than strategic planning. The five-step protocol specifically targets premise validation and goal alignment, not routine task tracking.