jobs-to-be-done

Analyze customer behavior and product-market fit using the Jobs to Be Done framework.

Updated Jul 31, 2026

Search Tags:#user research #innovation #product strategy #customer discovery #jtbd #churn analysis

Ready to run

npx skills add https://github.com/fsolla/teqo --skill jobs-to-be-done-fsolla

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/fsolla/teqo/tree/main/.agents/skills/jobs-to-be-done
Command: npx skills add https://github.com/fsolla/teqo --skill jobs-to-be-done-fsolla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you move beyond superficial customer feedback to understand the fundamental motivations behind why users hire or fire products, preventing feature bloat and misaligned roadmaps.

Core Features & Use Cases

Framework Application: Apply the four forces of progress (Push, Pull, Anxiety, Habit) to analyze why users switch products.
Interview Reconstruction: Use timeline-based questioning to uncover the true circumstances and functional, emotional, and social dimensions of a job.
Use Case: If you are struggling with high churn, use this Skill to conduct timeline interviews with former customers to identify whether the failure occurred at the Big Hire (purchase) or the Little Hire (daily usage).

Quick Start

Use the jobs-to-be-done skill to analyze the four forces of progress for a user who recently switched from our platform to a competitor.

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 analyze customer churn using the jobs-to-be-done framework?▼

To analyze customer churn using the jobs-to-be-done framework, conduct timeline-based interviews with former customers to identify whether the failure occurred at the Big Hire (purchase) or the Little Hire (daily usage), evaluating the four forces of progress.

What is the best way to uncover user motivations beyond superficial product feedback?▼

Uncovering user motivations requires reconstructing the customer's timeline to reveal the functional, emotional, and social dimensions of the job they hired the product to perform, moving beyond superficial feedback to prevent misaligned roadmaps.

How do I apply the four forces of progress for competitive strategy and product switching analysis?▼

Apply the four forces of progress—Push, Pull, Anxiety, and Habit—to map the competitive landscape and analyze exactly why users switch from your product to a competitor, facilitating outcome-oriented feature prioritization.

Can I use timeline-based questioning for customer discovery and feature prioritization?▼

Yes, you can use timeline-based questioning during customer discovery to identify the true circumstances behind a user's progress, which directly drives feature prioritization by aligning product strategy with actual functional jobs.

When should I use jobs-to-be-done analysis instead of standard qualitative user research?▼

Use jobs-to-be-done analysis instead of standard qualitative user research when you need to identify underlying customer motivations for product-market fit, preventing feature bloat by focusing on the fundamental jobs users hire products to perform.