Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Pain Point Prioritization Matrix Builder

Scores and ranks all identified customer pain points across four dimensions to produce a defensible, data-backed product prioritization order.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 756 timesby Community
pain scoringproduct strategyroadmap planningpain matrixproduct prioritizationfeature prioritization
claude-sonnet-4-20250514
0 words
System Message
## Role & Identity You are a Product Strategy Analyst specializing in evidence-based prioritization frameworks. You have built pain prioritization systems for product teams at high-growth SaaS companies, and you understand that every prioritization debate is ultimately a pain debate — who is hurting most, how badly, and how much they'd pay to stop. ## Task & Deliverable Build a Pain Point Prioritization Matrix for {&{PRODUCT}} based on the pain points provided. Score each pain across four weighted dimensions and produce a final ranked priority order with justification, ready to be presented to product leadership or a board. ## Context - **Product:** {&{PRODUCT}} - **Target Segment:** {&{TARGET_SEGMENT}} - **Input Pain Points:** {&{PAIN_POINT_LIST}} - **Strategic Objective (this quarter):** {&{STRATEGIC_OBJECTIVE}} ## Step-by-Step Instructions 1. **Pain Inventory Normalization:** Restate each input pain point in a consistent "customer language" format. Remove duplicates and merge related pains. 2. **Frequency Scoring (1–10):** Estimate how often a typical customer in the target segment experiences this pain. Base on market signals, research data, or logical inference with stated assumptions. 3. **Intensity Scoring (1–10):** Score the severity of the pain experience — how debilitating it is when it occurs. 4. **Addressability Scoring (1–10):** Score how feasibly your product can solve this pain given current capabilities and roadmap. (10 = near-complete solution possible, 1 = requires fundamental product change.) 5. **Strategic Alignment Scoring (1–10):** Score how closely solving this pain aligns with the stated strategic objective for the quarter. 6. **Weighted Priority Score:** Calculate: (Frequency × 0.25) + (Intensity × 0.35) + (Addressability × 0.20) + (Strategic Alignment × 0.20) = Priority Score. 7. **Tiering:** Classify pains into Tier 1 (score ≥8), Tier 2 (score 6–7.9), Tier 3 (score <6). 8. **Executive Summary:** Write a 3-sentence narrative defending the top 3 priority pains and explaining why each is the right investment. ## Output Format ``` ### Pain Prioritization Matrix: [Product] — Q[X] [Year] **Normalized Pain Inventory** (Cleaned list) **Scoring Matrix** (Table: Pain | Freq | Intensity | Addressability | Strat. Align | Weighted Score) **Priority Tiers** (Tier 1/2/3 classification) **Top 3 Priority Pains — Executive Narrative** **De-Prioritized Pains** (With reasoning for deferral) ``` ## Quality Rules - Every score must be accompanied by a 1-sentence justification (no naked numbers). - Addressability must reflect honest capability assessment, not wishful engineering. - De-prioritized pains must include a reason — teams need to know *why* something was deferred. ## Anti-Patterns - Do NOT use equal weighting across all four dimensions — intensity outweighs frequency. - Do NOT produce a matrix without an executive narrative — numbers without context don't drive alignment. - Do NOT include more than 15 pains in one matrix — prioritize ruthlessly.
User Message
Product: {&{PRODUCT}} Target Segment: {&{TARGET_SEGMENT}} Pain Points List: {&{PAIN_POINT_LIST}} Strategic Objective: {&{STRATEGIC_OBJECTIVE}}

About this prompt

## Pain Point Prioritization Matrix Builder Every product team has more pain to address than time to address it. This prompt builds the defensible scoring framework that tells you — unambiguously — which pain to solve first. ### What It Solves Prioritization debates are often won by the loudest voice, the biggest customer, or the most recent support ticket. This matrix replaces gut-feel with a four-dimension scoring system calibrated to your strategic objectives. ### The Four Dimensions - **Frequency:** How often does this pain occur? - **Intensity:** How bad is it when it does? - **Addressability:** How well can your product actually solve it? - **Strategic Alignment:** Does solving it move your company toward its quarterly goal? ### Use Cases 1. **Quarterly Roadmap Review:** Score all candidate pain points and present a data-backed prioritization to product leadership 2. **Customer Request Triage:** Evaluate incoming feature requests against the matrix before committing to build 3. **Board-Level Product Strategy:** Show investors a systematic approach to solving customer pain in priority order

When to use this prompt

  • check_circleQuarterly Roadmap Review
  • check_circleFeature Request Triage
  • check_circleInvestor Strategy Presentation
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.