jtbd-building

Apply Jobs-to-be-Done theory to analyze customer motivations and four forces.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/danfrdn/antigravity-config --skill jtbd-building-danfrdn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jtbd-building
Source: https://github.com/danfrdn/antigravity-config/tree/main/skills/jtbd-building
Command: npx skills add https://github.com/danfrdn/antigravity-config --skill jtbd-building-danfrdn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams design features that truly resonate with customer needs by applying the Jobs-to-be-Done (JTBD) framework, moving beyond surface-level feature requests to uncover the underlying motivations and desired progress in customers' lives.

Core Features & Use Cases

  • Jobs Theory Application: Understand customer needs through the lens of functional, emotional, and social jobs.
  • Forces Diagram Analysis: Map the push, pull, anxiety, and habit forces influencing customer adoption.
  • Use Case: When developing a new mobile banking app feature, use this Skill to identify the core job customers are trying to get done (e.g., "feel financially secure and in control") and design features that directly address the forces at play, ensuring higher adoption and satisfaction.

Quick Start

Use the jtbd-building skill to analyze the job for a new budgeting feature.

Frequently Asked Questions about jtbd-building

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

FAQPage Schema
How do I use Jobs-to-be-Done theory for product feature development?

Jobs-to-be-Done theory applies to feature development by analyzing customer motivations and desired progress to design features that address functional, emotional, and social jobs, ensuring higher adoption and satisfaction.

What is the four forces analysis in customer research?

Four forces analysis in customer research maps the push of current dissatisfaction, the pull of a new solution, anxiety about adoption, and existing habits that influence customer behavior and product adoption.

How to identify customer needs beyond surface-level feature requests?

Identify customer needs by uncovering the underlying functional, emotional, and social jobs customers are trying to get done, shifting focus from requested features to the desired progress in their lives.

When should I apply JTBD frameworks instead of traditional product design?

Apply JTBD frameworks when traditional product design yields low adoption, requiring a shift to map push, pull, anxiety, and habit forces to understand why customers hire or fire a feature.

Can I analyze emotional and social jobs for a mobile banking app feature?

Yes, analyzing emotional and social jobs for a mobile banking app feature identifies core motivations like feeling financially secure, enabling design that directly addresses adoption anxieties and habits.

What is the best way to map customer motivations for new feature ideation?

The best way to map customer motivations for feature ideation is applying Bob Moesta's frameworks to understand customer progress and the forces influencing their adoption decisions.