Topic Cluster — Product Instinct Library

Product Instinct Library: From Pilot Prompt to Frame-Anchored Spec

The aggregated runtime behind every AI-spec generated across the five pilot templates — live counts, average ratings, and recurring framing patterns.

Every AI-spec generated across the four pilot templates feeds the library — the runs aggregate, the pilot ratings surface, and the framing patterns each template is anchored on show up live. Use this hub to see which spec template is being relied on most, where pilot ratings still drift below the 4-star bar, and which cluster post to send a teammate next.


Open audit view
success-metrics template
How Product Managers Define and Track Success Metrics — The PM's Framework for Choosing KPIs That Actually Guide Decisions

Five-component test (Outcome, Attribution, Leading, Comparability, Memorability) anchors every KPI the spec generator emits — so the metric tree matches the blog framework, and rejects any candidate that fails any component.

August 1, 2026 / 11 min read
competitive-research template
Competitive Analysis for Product Managers — The Framework for Choosing Comparison Axes That Actually Differentiate Vendors

Framework enforces three commitments: comparison axes picked by RELEVANCE to the brief, real concrete public sources per axis, and honest gaps the AI cannot settle from public data alone.

August 1, 2026 / 11 min read
discovery-plan template
Product Discovery & User Research for PMs — The PM's Framework for Choosing the Right Research Method for Every Decision

Three-method mapping anchors every research question: interviews for WHY (motivations and unmet needs), surveys for HOW MANY (prevalence and segmentation), analytics for WHAT USERS DID (real behavioural ground-truth).

August 1, 2026 / 11 min read
prioritization template
Prioritization Frameworks for Product Managers — How PMs Run a Strategic Filter, MoSCoW Triage, and Framework-Specific Scoring Pass

Four-layer stack governs the spec: every candidate passes a strategic filter, gets MoSCoW-tagged at the initiative level, is scored with the framework whose inputs the brief supplies, and is reviewed for framework-distribution dominance.

August 1, 2026 / 13 min read
feedback-triage template
How to Triage Customer Feedback Without Losing Your Mind — The PM's 4-Tier Rubric for Turning Inbox Chaos Into a Weekly Prioritized Decision List

Four-tier rubric anchors every feedback item the spec generator emits — so the tier assigned matches the blog framework, and rejects duplicate work, single-data-point noise, or critical items deprioritized as strategic.

August 2, 2026 / 11 min read

Recurring framing patterns the library enforces

  • success-metrics — 5-component test: Outcome, Attribution, Leading, Comparability, Memorability. A KPI is rejected by the spec generator if it fails any component.
  • competitive-research — axes chosen by relevance, concrete public sources per axis (G2, Crunchbase, ProductHunt, vendor docs), and honest gaps that need primary research.
  • discovery-plan — three-method mapping: interview = WHY, survey = HOW MANY, analytics = WHAT USERS DID.
  • prioritization — strategic filterMoSCoW triageframework-specific scoringframework-distribution review.
  • feedback-triage — 4-tier rubric: critical (blocker/churn — act within 48h), strategic (data-validated — next cycle), noise (single data point — log and ignore), duplicate (already captured — merge and move on), weekly cadence, each item tiered in under 60 seconds.

Where pilot ratings still drift

Pilots haven't rated enough runs yet for the library to surface common failure modes — refresh after the next 5 ratings.

Generate a frame-anchored spec in 90 seconds

ChiefProduct runs the four pilot templates with the same framing the library enforces — pick a template, paste a brief, and rate the output so the library stays honest.

Try ChiefProduct Free