jobs-to-be-done

Identify customer jobs to be done through discovery interviews and job atlas mapping.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sachio222/based-stack --skill jobs-to-be-done-sachio222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/sachio222/based-stack/tree/main/jobs-to-be-done
Command: npx skills add https://github.com/sachio222/based-stack --skill jobs-to-be-done-sachio222

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams move from guessing what customers want to a rigorous, jobs-based understanding of the progress customers seek. It guides discovery, interviews, and strategy around what job is being hired, why, and how to design around it.

Core Features & Use Cases

  • JTBD statement creation: articulate a customer job in the context of use, progress, and outcome.
  • Forces of progress analysis: map Push, Pull, Anxiety, and Habit to explain adoption dynamics.
  • Competitive landscape by job: identify non-obvious competitors and alternative hires.
  • Customer discovery interviews: reconstruct purchase and usage journeys to reveal hidden jobs.
  • Job atlas and design alignment: map related jobs, emotional/social dimensions, and consumption chain.
  • Design for the job: align metrics, roadmap, and organization to job completion.

Quick Start

Begin by interviewing 10 recent customers to uncover the core job, then draft a job statement in the format When [circumstances], I want to [progress], so I can [outcome].

Frequently Asked Questions about jobs-to-be-done

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

FAQPage Schema
How do I write a jobs-to-be-done statement for product strategy?

A jobs-to-be-done statement is articulated using the format: When [circumstances], I want to [progress], so I can [outcome]. This structure guides product strategy by focusing on the specific progress a customer seeks rather than product features.

What is the best way to uncover customer jobs during discovery interviews?

The best way to uncover customer jobs is by conducting discovery interviews with at least 10 recent customers to reconstruct their purchase and usage journeys. This process reveals the hidden jobs customers are actually hiring a product to do.

How does forces of progress analysis explain product adoption dynamics?

Forces of progress analysis explains product adoption by mapping four forces: Push, Pull, Anxiety, and Habit. This framework identifies what drives customers toward a new solution and what barriers prevent them from switching.

Can I use jobs-to-be-done theory for competitive analysis and churn reduction?

Yes, jobs-to-be-done theory applies directly to competitive analysis and churn reduction by identifying non-obvious competitors and alternative hires. It maps the actual jobs customers need completed to reveal why they switch products.

What is a job atlas and how does it align product roadmaps?

A job atlas maps related customer jobs, including emotional and social dimensions, along the consumption chain. Aligning product roadmaps to this atlas ensures metrics and organizational design directly support core job completion.

Do I need to conduct non-consumption analysis to build a job-based product strategy?

Yes, non-consumption analysis is required to build a job-based product strategy. It identifies alternative hires and validates that proposed solutions align with the core job, ensuring the roadmap targets actual market gaps.