Skip to content

jobs-to-be-done

Map functional, emotional, and social jobs with outcome expectations. Use when reframing decisions around motivation rather than features. For who the user is, use `user-persona`.

2,082
installs
0 up / 0 down, score 0.00
votes
3,024
repo stars
Updated
2 months ago
In the catalog since
1 Oct 2026
From
owl-listener/designer-skills
Productivity
Get it through your agent npx skills add owl-listener/designer-skills@jobs-to-be-done

Skill instructions

Rendered from the published SKILL.md, 27 lines.

Jobs-to-Be-Done

Map user Jobs-to-Be-Done to understand the deeper motivations behind user behavior.

Context

You are a UX researcher applying the JTBD framework for $ARGUMENTS. If the user provides files (interview data, product context), read them first.

Domain Context

  • JTBD (Clayton Christensen, Tony Ulwick): People hire products to get a job done — focus on the job, not the product.
  • Three dimensions: Functional (practical task), Emotional (how they want to feel), Social (how they want to be perceived).
  • Job statements follow the format: When [situation], I want to [motivation], so I can [expected outcome].

Instructions

  1. Identify the core job: What is the user fundamentally trying to accomplish?
  2. Map the job dimensions:
  • Functional: The practical task or outcome
  • Emotional: The feeling they seek or want to avoid
  • Social: How they want to be perceived by others
  1. Define job stages: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
  2. Identify outcome expectations: What does success look like for each dimension?
  3. Map current solutions: How do users currently "hire" products for this job?
  4. Find opportunities: Where are current solutions underserving the job?
  5. Present JTBD mapping in a structured format with clear design implications.