jobs-to-be-done

Use when asked to "jobs to be done", "JTBD", "why customers churn", "prep for customer interviews", "hire and fire products", or "find real competitors". Helps discover unmet needs and the context behind purchasing decisions. The Jobs to be Done framework (created by Clayton Christensen and Bob Moesta) explains why customers hire and fire products.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "jobs-to-be-done" with this command: npx skills add pmprompt/claude-plugin-product-management/pmprompt-claude-plugin-product-management-jobs-to-be-done

Domain Context

This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.

Input Requirements

  • Context about your product, feature, or problem
  • Relevant data, research, or constraints (recommended but optional)
  • Clear articulation of what you're trying to achieve

Jobs-to-be-Done (JTBD)

What It Is

Jobs-to-be-Done is a framework for understanding customer motivation. The core insight: people don't buy products, they hire them to make progress in their lives.

When someone buys a product, they're not buying features or benefits—they're hiring that product to do a job. Understanding that job unlocks everything: positioning, messaging, feature prioritization, and competitive strategy.

The key shift: Move from asking "What do customers want?" to asking "What progress are customers trying to make?"

When to Use It

Use JTBD when you need to:

  • Understand why customers buy (not just what they buy)
  • Discover your true competitive set (often not who you think)
  • Find product-market fit for a new product or feature
  • Improve positioning and messaging that resonates
  • Reduce churn by understanding why customers leave
  • Prioritize your roadmap based on real customer progress
  • Identify new market opportunities through struggling moments

When Not to Use It

  • There's no real customer choice (e.g., employer-mandated software)
  • The purchase is pure habit with no conscious decision
  • You want to validate a hypothesis you've already decided on

Resources

Books:

  • Demand-Side Sales by Bob Moesta
  • Competing Against Luck by Clayton Christensen
  • When Coffee and Kale Compete by Alan Klement

Further Reading

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

prd-writer

No summary provided by upstream source.

Repository SourceNeeds Review
General

feature-prioritization-assistant

No summary provided by upstream source.

Repository SourceNeeds Review
General

user-feedback-synthesizer

No summary provided by upstream source.

Repository SourceNeeds Review
General

product-led-growth

No summary provided by upstream source.

Repository SourceNeeds Review