All examples for Pain Point Prioritizer

Knowledge Worker Productivity Pain Points

Simple baseline prioritization of 3 common productivity pain points (slow email, notifications, file finding) with scoring methodology and product opportunity angles.

Input

What you provide to the skill

Pain points: 1. Slow email 2. Too many notifications 3. Hard to find files. Which is most urgent?

Output

What the skill generates for you

Pain Point Prioritization Report

Scoring Methodology

Each pain point scored on 4 dimensions (0-100):

  • Urgency: How desperately do users want this solved? (language intensity, emotional weight)
  • Frequency: How often does this occur? How many people affected?
  • Impact: What’s the cost in time, money, relationships, or wellbeing?
  • Solvability: Can a product actually solve this? Is the solution in scope?

Final Score = (Urgency × 0.35) + (Frequency × 0.25) + (Impact × 0.25) + (Solvability × 0.15)


Priority Rankings

Rank #1: Hard to Find Files

Final Score: 73/100

Dimension Score Reasoning
Urgency 75 Moderate frustration - slows work but doesn’t create crisis
Frequency 85 Daily occurrence for knowledge workers
Impact 70 Time waste (5-20 min/day = 2-8 hours/month productivity loss)
Solvability 85 Search tools, file organization systems, tagging can directly solve

Why #1: Highest frequency creates daily friction that compounds over time. Occurs multiple times per workday for anyone managing multiple projects or files. Clear product opportunities exist (better search, auto-tagging, AI-powered file retrieval).

Product Opportunity Angle: Smart file organization systems, semantic search tools, automated tagging based on content/context, unified search across cloud services.


Rank #2: Too Many Notifications

Final Score: 71/100

Dimension Score Reasoning
Urgency 80 High frustration - “constant interruptions”, “can’t focus”
Frequency 80 Constant/hourly occurrence throughout workday
Impact 65 Attention fragmentation, reduced deep work capacity
Solvability 70 Notification management tools exist but require user discipline/configuration

Why #2: Very high urgency due to attention/focus impact, but slightly lower solvability because it requires behavior change and cross-app coordination. Users often feel helpless against notification overload.

Product Opportunity Angle: Intelligent notification filtering, focus mode automation, notification batching by priority, AI-powered “important vs noise” classification.


Rank #3: Slow Email

Final Score: 61/100

Dimension Score Reasoning
Urgency 60 Annoying but accepted as norm - low desperation language
Frequency 70 Daily touchpoint but not constant like notifications
Impact 60 Delays responses by minutes/hours, not catastrophic
Solvability 65 Technical solutions exist but often infrastructure/provider limited

Why #3: Lower urgency because users have adapted to current email speeds. Impact is moderate - delays are measured in minutes/hours not days. Solvability is constrained by email infrastructure beyond user control.

Product Opportunity Angle: Email client optimization, caching strategies, faster search indexing, offline-first email apps.


Recommendation

Build for Pain Point #1 (Hard to Find Files) because:

  1. Highest combined score (73)
  2. Daily occurrence with cumulative time waste = measurable ROI
  3. High solvability - clear product categories exist (search, organization, AI tagging)
  4. Users actively seek solutions (validation of willingness to adopt new tools)

Consider Pain Point #2 (Too Many Notifications) as secondary because:

  1. Higher urgency (attention/focus impact resonates emotionally)
  2. Growing problem as app ecosystem expands
  3. Could differentiate with intelligent filtering vs. simple on/off controls

Deprioritize Pain Point #3 (Slow Email) because:

  1. Lowest urgency - users have adapted to current speeds
  2. Infrastructure constraints limit product-level solutions
  3. Limited differentiation opportunity in crowded email client market