product-diagnosis

To use customer signals for roadmap prioritization, cross-read customer profiles, CS history, issues, and PRD documents to extract root pain points. Apply RICE scoring to evaluate reach, impact, confidence, and effort for product direction alignment.

Separating customization from scalable features requires cross-analyzing customer documents to identify repeating pain points. You distinguish single-customer specific requests from underlying product direction signals that indicate broader market expansion potential.

RICE-based roadmap prioritization evaluates features using Reach, Impact, Confidence, and Effort metrics extracted from customer document analysis. It structures identified pain points into quarterly roadmap proposals spanning current period to Q+2 for product direction alignment.

WebSearch can optionally analyze competitive positioning during product diagnosis. The adversarial validation step reviews WebSearch reliability limits and customer bias to ensure data quality before finalizing RICE-based roadmap priorities.

Cross-source product diagnostic analysis requires customer profile markdown files, CS history records, issue logs, meeting minutes, and PRD/SRS artifacts. Onboarding and state transition documents can optionally map customer-journey bottlenecks comprehensively.

The adversarial validation step re-examines customer bias, How versus What confusion, and data gap areas to strengthen evidence quality. It self-validates RICE priorities and competitive analysis findings before finalizing quarterly roadmap proposals.