jtbd-building

Map customer jobs and decision forces using JTBD frameworks.

389|121|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/menkesu/awesome-pm-skills --skill jtbd-building
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jtbd-building
Source: https://github.com/menkesu/awesome-pm-skills/tree/main/jtbd-building
Command: npx skills add https://github.com/menkesu/awesome-pm-skills --skill jtbd-building

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product teams design features by identifying customer jobs and the underlying push/pull dynamics, enabling decisions that go beyond explicit requests.

Core Features & Use Cases

  • JTBD Analysis: Capture functional, emotional, and social jobs and translate them into meaningful product opportunities.
  • Forces Diagram: Apply Push, Pull, Anxiety, and Habit forces to surface design priorities.
  • Templates & Guidance: Provide practical templates and real-world examples to operationalize JTBD in discovery and design.

Quick Start

Analyze a new feature by outlining the job to be done, the forces affecting choice, and the intended design outcomes in a concise template.

Frequently Asked Questions about jtbd-building

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

FAQPage Schema
What is a jobs-to-be-done framework for product design?

Jobs-to-be-done (JTBD) is a framework for product design that identifies customer jobs and the underlying push/pull dynamics shaping decisions, enabling teams to move beyond explicit feature requests.

How do I use a forces diagram to prioritize features?

A forces diagram prioritizes features by mapping Push, Pull, Anxiety, and Habit forces affecting customer choice, surfacing design priorities based on the push/pull dynamics of user decisions.

How do I capture emotional and social jobs in user research?

Capture emotional and social jobs during user research by analyzing customer jobs to translate functional, emotional, and social needs into meaningful product opportunities and actionable design outcomes.

Can I apply JTBD analysis during early product discovery?

Yes, you can apply JTBD analysis during early product discovery and feature ideation to map customer jobs, forces, and intended design outcomes using structured templates.

What is the best way to design features beyond explicit customer requests?

The best way to design features beyond explicit requests is using JTBD analysis to identify the underlying jobs and decision forces, operationalizing insights with structured templates and forces diagrams.

When should I not use the jobs-to-be-done approach for feature design?

The JTBD approach may not suit feature design when lacking sufficient customer insights to map functional, emotional, and social jobs, or when needing rapid execution without structured discovery.