Jobs to Be Done (JTBD) in Product Management: How pm-skills Structures Value Propositions

Jobs to Be Done (JTBD) is a product-strategy framework that defines value by the progress a customer seeks rather than demographic traits, and the pm-skills repository operationalizes this through a six-part value-proposition template that forces outcome-centric thinking.

The pm-skills repository (phuryn/pm-skills) provides AI-powered product management tools that embed Jobs to Be Done theory directly into actionable workflows. By shifting focus from "who is the user?" to "what outcome does the user want to achieve?", the framework helps product teams build compelling, testable value propositions rooted in customer progress.

What Is Jobs to Be Done (JTBD)?

Jobs to Be Done (JTBD) is a strategic lens popularized by Clayton Christensen and refined by Anthony Ulwick’s Outcome-Driven Innovation. It posits that customers "hire" products to accomplish specific jobs—functional, social, or emotional tasks that represent progress in their lives.

Unlike traditional segmentation based on demographics or psychographics, JTBD focuses on the circumstances of struggle and the desired outcomes of the user. Every purchase decision becomes an attempt to get a job done, and product value is measured solely by how effectively it enables that progress.

The pm-skills JTBD Framework for Value Propositions

In pm-product-strategy/skills/value-proposition/SKILL.md, the repository defines a six-part JTBD-framed template that structures value propositions around customer jobs rather than feature lists (see lines 35-36 for the core job definition).

The Six-Part Template

The template forces explicit articulation of the customer journey from struggle to solution:

1. Who – The target segment or persona experiencing the job.
2. Why (Problem) – The job the customer wants to get done, including desired outcomes and success metrics.
3. What Before – The current state, existing pain points, and workarounds.
4. How (Solution) – The specific mechanism by which the product solves the job.
5. What After – The measurable improved state post-adoption.
6. Alternatives – Competing solutions or substitute behaviors that accomplish the same job.

By anchoring the "Why" section explicitly to the JTBD, the framework prevents feature-centric thinking and ensures alignment with functional, social, and emotional customer needs.

How JTBD Integrates Across pm-skills

The JTBD philosophy extends beyond single artifacts into the broader product strategy workflow.

Startup Canvas Integration

The Startup Canvas skill (pm-product-strategy/skills/startup-canvas/SKILL.md) instructs users to define market segments using "Jobs to Be Done, desired outcomes, constraints" (lines 56-59). This ensures that market segmentation emerges from observable struggle and progress rather than abstract persona attributes.

When populating the canvas, users must articulate the JTBD for each segment, creating a direct link between market definition and value proposition.

Product Strategy Command

The Product-Strategy command (pm-product-strategy/commands/strategy.md) mandates "Value Propositions – JTBD-framed value for each segment" as a required step in the strategic planning process (line 42). This enforces consistency across the product lifecycle, ensuring that every strategic document references customer jobs and outcomes.

Practical Application: Creating JTBD-Driven Value Propositions

The repository ships these frameworks as Markdown-based AI prompts. Below are practical examples of invoking the JTBD-driven workflow.

Value Proposition Generation

To generate a JTBD-framed value proposition, invoke the skill with a product concept:

/value-proposition "A lightweight diagramming tool for remote teams"

The skill auto-populates the six-part structure:

**Who**: Remote-team members who need quick visual collaboration
**Why (Job to Be Done)**: When they need to illustrate ideas on the fly, they want a fast, intuitive diagram editor, so they can keep meetings productive without switching apps
**What Before**: Using whiteboards, PowerPoint, or overloaded design tools → friction, lost time
**How**: Real-time sync, drag-and-drop shapes, minimal UI, no-install web app
**What After**: Teams create clear diagrams instantly, decision-making speeds up, meeting focus improves
**Alternatives**: Miro (complex), PowerPoint (clunky), hand-drawn sketches (hard to share)

Startup Canvas JTBD Entry

For strategic planning, the startup canvas captures JTBD at the segment level:

/startup-canvas

When prompted for market segments, provide the JTBD context:

Segment: Freelance graphic designers
JTBD: Quickly produce client-ready mockups without expensive software
Desired outcomes: Reduce design time by 30%, lower cost per project
Constraints: Limited budget, need for easy sharing

The skill then embeds these details into the canvas, automatically populating the Value Proposition section using the six-part JTBD structure.

Summary

• Jobs to Be Done shifts product strategy from feature lists to customer progress, focusing on the outcomes users seek rather than who they are.
• The pm-skills repository implements JTBD through a six-part value-proposition template defined in pm-product-strategy/skills/value-proposition/SKILL.md.
• The framework integrates across Startup Canvas and Product Strategy commands, ensuring consistent job-centric thinking.
• By forcing articulation of the job, current pain points, and alternatives, the tooling enables testable, compelling positioning statements.

Frequently Asked Questions

What is the difference between JTBD and user personas?

Traditional user personas rely on demographic and psychographic attributes (age, role, preferences), while JTBD focuses on the circumstance and progress a user seeks. According to the pm-skills framework, a customer "hires" a product to accomplish a specific job, making the job itself the primary unit of analysis rather than the individual's traits.

How does the six-part template prevent feature-centric thinking?

The template in pm-product-strategy/skills/value-proposition/SKILL.md forces definition of the Why (Problem)—the customer's job and desired outcomes—before allowing description of the How (Solution). This sequencing ensures that features are justified by their ability to complete the job, not by internal technical capabilities or assumptions.

Can JTBD apply to B2B and enterprise products?

Yes. The pm-skills repository treats JTBD as universal across market types. In B2B contexts, the "job" often involves functional business outcomes (reduce processing time, increase compliance) and social dimensions (looking competent to stakeholders). The six-part template captures these through the "Desired outcomes" and "What After" sections.

Where does pm-skills source its JTBD methodology?

The repository references Clayton Christensen’s original JTBD theory and Anthony Ulwick’s Outcome-Driven Innovation, as noted in the root README.md. The implementation adapts these academic frameworks into practical AI prompts and Markdown-based skills for modern product teams.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}