jobs-to-be-done

Document customer jobs, pains, and gains in a structured JTBD format.

Updated Aug 18, 2024
One-click install
npx skills add https://github.com/ch-m-n/dotfile --skill jobs-to-be-done-ch-m-n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/jobs-to-be-done
Command: npx skills add https://github.com/ch-m-n/dotfile --skill jobs-to-be-done-ch-m-n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams struggle to surface the true jobs customers hire their solution for, and this skill channels JTBD thinking to capture functional, social, and emotional motivations plus the pains and gains tied to them.

Core Features & Use Cases

  • Structured JTBD lens: Guides you through describing jobs (functional, social, emotional) before pairing them with pains, costs, mistakes, and unresolved problems to avoid mistaking features for outcomes.
  • Template-backed guidance: Points to the provided template and related persona/positioning skills so interviews and research notes feed directly into discovery, validation, messaging, and prioritization workstreams.
  • Real-world example: Use it during early discovery or repositioning to interview customers, document their current workarounds, and translate those insights into prioritized opportunities, messaging, and roadmap focus.

Quick Start

Document the jobs, pains, and gains for your target customer while following the JTBD template.

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 map customer jobs, pains, and gains during product discovery?

To map customer jobs, pains, and gains, document functional, social, and emotional jobs while pairing them with pains, costs, mistakes, and unresolved problems. This structured approach surfaces unmet needs and prevents mistaking features for outcomes during discovery.

What is the jobs-to-be-done framework used for in product strategy?

The jobs-to-be-done framework clarifies customer motivations during discovery, roadmap prioritization, and messaging workstreams. It captures functional, social, and emotional jobs to help teams translate research insights into prioritized opportunities and messaging focus.

Why do product teams mistake features for customer outcomes during discovery?

Product teams mistake features for outcomes when they fail to separate functional, social, and emotional jobs from associated pains and gains. Structuring discovery around the jobs-to-be-done framework avoids this misalignment by focusing on unmet customer needs.

How do I document customer workarounds and translate them into roadmap priorities?

Document customer workarounds by capturing functional, social, and emotional jobs alongside pains and gains in a structured template. These insights surface unmet needs, allowing you to translate discovery research into prioritized opportunities and roadmap focus.

Can I use jobs-to-be-done thinking for repositioning and messaging workstreams?

Yes, jobs-to-be-done thinking applies to repositioning and messaging workstreams by clarifying true customer motivations. Documenting functional, social, and emotional jobs paired with pains and gains validates positioning and surfaces competitive alternatives.

Do I need persona and positioning skills to validate customer jobs and pains?

Referencing persona and positioning skills validates your documented customer jobs and pains. Integrating these skills ensures interview notes and research feed directly into discovery, validation, messaging, and prioritization workstreams effectively.