jtbd

Conducts structured Jobs-to-be-Done analysis to identify customer needs and desired outcomes.

25|7|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xoai/sage --skill jtbd-xoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jtbd
Source: https://github.com/xoai/sage/tree/main/skills/jtbd
Command: npx skills add https://github.com/xoai/sage --skill jtbd-xoai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and templates (resource) components.

What problem does it solve?

This Skill helps you deeply understand customer needs by structuring analysis around the "Jobs-to-be-Done" framework, moving beyond surface-level feature requests to uncover core motivations and desired outcomes.

Core Features & Use Cases

  • Structured Analysis: Produces a comprehensive Jobs-to-be-Done analysis, including job performer, main job statement, process map, pains/gains, and desired outcomes.
  • Mode Flexibility: Supports 'fix' (update existing analysis), 'build' (quick job framing), and 'architect' (full, in-depth analysis) modes.
  • Use Case: When launching a new product or feature, use this Skill to ensure it's designed to solve a real customer job, not just a perceived problem. It helps define what success looks like for the customer and where current solutions fall short.

Quick Start

Use the jtbd skill to perform a full jobs-to-be-done analysis for our new project management tool.

Frequently Asked Questions about jtbd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a Jobs-to-be-Done analysis to uncover customer needs?

To conduct a Jobs-to-be-Done analysis, define the job performer, main job statement, process map, pains, gains, and desired outcomes. This structured approach moves beyond feature requests to reveal core customer motivations for product strategy.

What is outcome-driven innovation and how does it define product success?

Outcome-driven innovation defines product success by identifying desired customer outcomes rather than feature requests. It uses a Jobs-to-be-Done framework to map the job process and specify what success looks like for the customer during product launches.

How do I prioritize my product roadmap based on customer jobs?

Prioritize your product roadmap by mapping customer jobs and identifying desired outcomes. Structured JTBD analysis highlights where current solutions fall short, allowing you to align features with real customer motivations and desired success metrics.

Can I update an existing jobs-to-be-done framework without starting over?

Yes, you can update an existing jobs-to-be-done framework using the 'fix' mode. This allows you to revise your current customer research analysis, refining the job performer, pains, and gains without rebuilding the entire process map from scratch.

When should I use a full JTBD analysis versus quick job framing?

Use full JTBD analysis for in-depth product strategy requiring complete process maps and desired outcomes, or use quick job framing for immediate needs discovery. Choose 'architect' mode for comprehensive analysis and 'build' mode for rapid job framing.

Why does my product messaging fail to connect with customer motivations?

Product messaging fails when it focuses on features rather than customer jobs. By defining the main job statement and desired outcomes through JTBD analysis, you can align your messaging with core customer needs and actual success criteria.