jtbd-framing
The Jobs-to-be-Done framework as applied product methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking.
Install / Use
npx skills add rampstackco/claude-skills --skill jtbd-framingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of jtbd-framing
jtbd-framing scores 86/100 on our quality scale, 2459th of 4,700 Development & Engineering skills we index.
Its SKILL.md is 21 KB long, well organised into 14 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 902 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so jtbd-framing is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
jtbd-framing compared with similar skills
All 4 of these similar skills score higher than jtbd-framing; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| jtbd-framing (this skill)by rampstackco | 86 | 902 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install jtbd-framing?
- Run
npx skills add rampstackco/claude-skills --skill jtbd-framing. The install tabs above show the steps for each supported agent. - Which AI agents does jtbd-framing work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is jtbd-framing safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is jtbd-framing still maintained?
- The repository was last updated about 2 months ago, so jtbd-framing is actively maintained.
Skill content
View source on GitHubname: jtbd-framing description: "The Jobs-to-be-Done framework as applied product methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity (discovery, prioritization, positioning) and where it becomes performative ritual (job-statement workshops that do not drive decisions, persona-theater disguised as JTBD). Triggers on jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional emotional social jobs, outcome-driven innovation. Also triggers when a team is over-relying on feature-request lists or persona archetypes that do not drive product decisions, when a positioning conversation needs the framing JTBD provides, or when discovery is producing outputs that do not connect to product strategy." category: product catalog_summary: "Jobs-to-be-Done framework. Job statements, struggling moments, hire/fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD earns its keep and where it becomes performative" display_order: 11
Jobs-to-be-Done Framing
A senior product leader's playbook for the Jobs-to-be-Done framework as applied methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity and where it becomes performative ritual.
JTBD has become one of the more cited and less practiced frameworks in product. Teams cite it in strategy docs, run job-statement workshops, produce wall-sized artifacts, and continue building from feature requests and persona archetypes the next quarter. The methodology gets the credit; the practice gets skipped.
This skill is JTBD as applied product methodology. The framework's actual contribution: surfacing what users are trying to ACCOMPLISH (the job) rather than treating users as preference-aggregators (feature requests) or demographic archetypes (persona theater). When the framing is grounded in struggling moments and hire/fire criteria, it produces decisions; when it stops at the job-statement worksheet, it produces ritual.
This skill is honest about both modes. JTBD genuinely earns its keep in discovery, prioritization, and positioning when applied with rigor. It becomes ceremony when teams treat job statements as deliverables rather than as analytical tools.
The voice is the senior product leader who has used JTBD well and watched plenty of teams use it badly. Concrete, opinionated about what the framework actually contributes, willing to call out where it gets oversold.
When to use this skill: applying JTBD to a discovery cycle, replacing persona-driven prioritization with job-driven prioritization, reframing positioning around what users hire the product to do, or auditing whether existing JTBD work in the org is driving decisions.
What this skill is for
This skill spans JTBD as a framing technique within product work. The PM-skill distinction:
discovery-research-synthesisis broader synthesis discipline; JTBD is one framing technique within it.jtbd-framing(this skill) is the specific JTBD methodology, its strengths, and its failure modes.pm-spec-writingis downstream: specs reference jobs as input.creative-directionis positioning territory; JTBD informs positioning but does not replace creative direction.roadmap-planningis downstream: roadmap can be organized around jobs rather than features.
The audience: senior PMs, product directors, product strategists, agencies running discovery and positioning work, in-house teams considering or already using JTBD.
What is not in scope: other product strategy frameworks (Wardley mapping, North Star, OKRs); the broader synthesis discipline (discovery-research-synthesis covers it); the demographic-persona work that sometimes gets confused with JTBD.
Feature-request-list vs persona-theater vs job-framing
The keystone framing.
Feature-request-list. "Users want X, Y, Z." Treats users as preference-aggregators. The product team builds the most-requested features. Output: a product that satisfies stated preferences but misses what users were actually trying to accomplish. Users do not always know what would solve their problem; they describe symptoms, not solutions. Feature-list-driven products often improve incrementally without becoming meaningfully better.
Persona-theater. Demographic personas with cute names. "Marketing Manager Maria, 35, urban, Pinterest user, drinks oat milk lattes." Decorative, not decision-driving. Persona characteristics rarely correlate with what the user needs from the product; demographic detail substitutes for behavioral insight. Personas in the wild often live as wall posters that nobody references in actual prioritization debates.
Job-framing. Users hire products to do jobs. The job is what the user is trying to accomplish, not who the user is or what features they request. The framing surfaces struggling moments (when do users feel pulled toward an alternative); hire criteria (what makes them adopt a product); fire criteria (what makes them switch away). Output: product decisions grounded in user motivation rather than user description.
The litmus test. Take a product decision the team is debating. Can JTBD ground the decision? "Should we build feature X?" Reframed: "What job would feature X help users do? What job is currently done badly that this addresses?" If the JTBD framing produces clearer arguments on both sides, the framing is earning its keep. If the JTBD framing just adds vocabulary without resolving the debate, the framing is ritual.
The job statement structure
The canonical structure: "When [situation], I want to [motivation], so I can [outcome]."
Situation. The context, trigger, or moment when the job becomes active. Not a demographic; a moment.
- "When my team is rolling out a new feature and I need to communicate it to customers..."
- "When I am preparing the quarterly board deck..."
- "When I get a customer escalation outside of business hours..."
Motivation. What the user is trying to do in that situation.
- "...I want to write a clear announcement that explains what changed and why it matters..."
- "...I want to assemble revenue and engagement data into a coherent narrative..."
- "...I want to triage and respond without disrupting my evening too much..."
Outcome. What success looks like; what the user is trying to achieve by doing the job.
- "...so I can ship the rollout without flooding support with confusion."
- "...so I can answer the board's likely questions before they ask them."
- "...so I can address the customer's concern while still being present at home."
The structure forces specificity at all three levels. Vague situations, vague motivations, or vague outcomes produce job statements that drive nothing.
Detail in references/job-statement-structure-patterns.md.
Identifying struggling moments
Jobs become visible at struggling moments: when the user's current solution is failing them, when the alternative tools they have feel inadequate, when they would actively prefer a different way of doing the job.
The signal. Users describe friction in their current approach. They describe workarounds. They describe wishing they had something better. They describe specific moments when the current approach broke down.
The methodology. Discovery interviews surface struggling moments through specific prompts: "Walk me through the last time you did X." "What was hardest about that?" "What would you have done differently if you could?" Specific recent moments produce richer data than abstracted descriptions of "how I usually do this."
The pattern recognition. Across many users, struggling moments cluster. The same kinds of friction recur. The clusters reveal the jobs that are not currently being done well in the market.
The pitfall. Teams that interview without grounding in specific moments produce abstracted job descriptions that cannot drive decisions. "Users want to be more productive" is not a struggling moment; "I lost an hour on Tuesday assembling the board metrics from three different dashboards because none of them had the slice I needed" is.
Detail in references/identifying-struggling-moments.md.
Hire and fire criteria
Why users adopt a product (hire), why they switch away (fire). The two questions ground the framework in real decisions users make.
Hire criteria.
- The struggling moment the user is trying to solve.
- The alternatives they considered or tried first.
- What made the chosen product the answer (vs the alternatives).
- The expected job output: what the user expected to accomplish with the product.
Fire criteria.
- The struggling moment that recurred even with the chosen product.
- The alternative that started looking better.
- What tipped the user from "considering switching" to "switching."
- The job output that the chosen product failed to deliver consistently.
Why hire/fire matters.
- Hire criteria reveal what the product needs to be excellent at to win adoption.
- Fire criteria reveal what the product needs to maintain to retain users.
- The two are often different: features that win adoption are not always the features that prevent churn.
The methodology. Customer interviews surface hire/fire through specific prompts: "What were you doing before you adopted X?" "What made you switch?" "If you switched away from X tomorrow, what would the trigger be?" Recent switch decisions are particularly rich; users remember the specific moment.
Detail in references/hire-and-fire-criteria.md.
Functional, emotional, and social dimensions of jobs
Jobs have three dimensions. Strong JTBD work surfaces all three; weak work treats jobs as functional only.
Functional dimension. What the user is mechanically trying to accomplish.
- "Assemble the quarterly board deck."
- "Track team OKR progress."
- "Onboard a new engineer to the codebase."
Emotional dimension. How the user feels (or wants to feel) doing the job.
- "Confident that the deck represents the team's actual progress, not a polished version."
- "In control of the OKR check-in cadence, not behind on it."
- "Helpful to the new engineer without becoming their full-time guide."
Social dimension. How the user wants to be perceived doing the job.
- "Seen by the board as a competent leader who knows the numbers."
- "Seen by direct reports as someone who follows through on commitments."
- "Seen by the new engineer as a senior who invested in their onboarding."
Why three dimensions matter.
- Products that win on functional alone often lose to alternatives that also serve emotional and social.
- Some product decisions hinge on emotional dimensions ("the user wants to feel in control"); functional analysis alone misses these.
- Social dimensions inform positioning more than functional descriptions do.
The discipline. For each job statement, ask the three dimensions explicitly. Most early job statements are functional-only; the addition of emotional and social often reveals what the product actually needs to address.
Detail in references/functional-emotional-social-dimensions.md.
Where JTBD adds clarity vs where it becomes ritual
The honest framing.
Where JTBD genuinely earns its keep.
- Discovery. When research is grounded in struggling moments and hire/fire decisions, JTBD surfaces the user motivation that feature-list discovery misses. Discovery interviews structured around jobs produce richer data than ones structured around feature preferences.
- **Prioritizatio
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
