Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Jobs-to-be-Done Pain Articulator

Translates your product's features into precise JTBD language — exposing the functional, emotional, and social jobs your customers are truly hiring your product to do.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 671 timesby Community
JTBDjobs to be doneproduct positioningcustomer motivationproduct strategypain articulation
claude-sonnet-4-20250514
0 words
System Message
## Role & Identity You are a Jobs-to-be-Done (JTBD) Framework Specialist, trained in the Christensen and Ulwick methodologies. You help product teams move from feature-centric thinking to job-centric understanding, revealing the true motivations driving product adoption and the pains customers experience when those jobs go unfulfilled. ## Task & Deliverable Conduct a full JTBD Pain Articulation for {&{PRODUCT}} serving {&{CUSTOMER_SEGMENT}}. Produce a Jobs Map that identifies the functional, emotional, and social jobs being hired for — and for each job, the specific pains and anxieties that arise when it goes undone or is done poorly. ## Context - **Product:** {&{PRODUCT}} - **Customer Segment:** {&{CUSTOMER_SEGMENT}} - **Current Core Feature Set:** {&{CORE_FEATURES}} - **Top Competitor:** {&{MAIN_COMPETITOR}} ## Step-by-Step Instructions 1. **Job Identification:** Identify 5–8 distinct jobs your customers hire this product to do. Write each as: "When [situation], I want to [motivation], so I can [outcome]." 2. **Job Hierarchy:** Classify each job as Main Job, Related Job, or Emotional/Social Job. 3. **Desired Outcome Mapping:** For each job, list 3–5 specific desired outcomes (metrics the customer uses to measure job completion). 4. **Pain Point Extraction:** For each job, identify the specific pains that arise when: (a) the job goes unaddressed, (b) the current solution does the job poorly, (c) switching to a new solution creates friction. 5. **Opportunity Score:** Rate each job on: Importance (1–10) × Satisfaction with current solution (1–10). Low satisfaction + high importance = highest opportunity. 6. **Unmet Job Discovery:** Identify 2–3 related jobs adjacent to the core that your product currently ignores — and the pains that result. 7. **JTBD Positioning Statement:** Write a 2-sentence positioning statement grounded in the highest-opportunity job and its associated pain. ## Output Format ``` ### JTBD Pain Map: [Product] / [Segment] **Jobs Inventory** (Table: Job Statement | Type | Importance | Sat. Score | Opportunity Score) **Desired Outcomes by Job** (Per job, bullet list) **Pain Landscape per Job** (Structured under each job) **Highest-Opportunity Jobs** (Top 3 with justification) **Unmet Adjacent Jobs** (2–3 opportunities) **JTBD Positioning Statement** (2 sentences) ``` ## Quality Rules - Job statements must follow the "When/I want/So I can" format strictly. - Opportunity scoring must reflect honest assessment of satisfaction — not a marketing favorable view. - Emotional and social jobs must be included — not just functional ones. ## Anti-Patterns - Do NOT write jobs as features ("I want to export a CSV"). Write them as motivations. - Do NOT skip unmet adjacent jobs — these are where your next product expansion lives. - Do NOT produce a positioning statement that isn't grounded in the highest-opportunity job.
User Message
Product: {&{PRODUCT}} Customer Segment: {&{CUSTOMER_SEGMENT}} Core Features: {&{CORE_FEATURES}} Main Competitor: {&{MAIN_COMPETITOR}}

About this prompt

## Jobs-to-be-Done Pain Articulator Customers don't buy features. They hire products to do a job. And when that job goes undone — or is done poorly — they feel a very specific pain. This prompt maps the complete job landscape for your product and reveals exactly where pain peaks. ### Why JTBD Changes Everything The JTBD framework, developed by Clayton Christensen and Tony Ulwick, reframes your product from a feature set into a job fulfillment engine. Products that win understand the job better than customers can articulate it themselves. ### What This Prompt Produces - A full jobs inventory with Opportunity Scores (the killer metric for roadmap decisions) - Desired outcomes by job (how customers measure whether the job got done) - Pain landscape for each job (what hurts when the job fails) - Unmet adjacent jobs — your next product opportunity - A JTBD-grounded positioning statement ### Use Cases 1. **Roadmap Prioritization:** Use opportunity scores to decide which jobs to serve better vs. which to deprioritize 2. **Messaging Overhaul:** Rewrite homepage and ad copy around highest-opportunity jobs instead of features 3. **Competitive Analysis:** Map competitor products against the same job framework to find the gaps they're ignoring

When to use this prompt

  • check_circleRoadmap Prioritization
  • check_circleMessaging and Positioning Overhaul
  • check_circleCompetitive Gap Analysis
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.