mcpField
J
jobs-to-be-done

jobs-to-be-done

github.com/infrasity-labsDesign & UI15078 installsUpdated 18w ago
Repository

About jobs-to-be-done

A UX research skill for mapping user Jobs-to-Be-Done with the JTBD framework. It guides researchers from the core job and its functional, emotional, and social dimensions through job stages, success outcomes, current solutions, and design opportunities.

Key features

  1. 01Identify the core user job
  2. 02Map functional, emotional, and social dimensions
  3. 03Outline job lifecycle stages
  4. 04Define outcome expectations
  5. 05Review current solutions and opportunities

Use cases

  1. 01Analyzing interview data for user motivations
  2. 02Mapping a product task across its lifecycle
  3. 03Turning unmet needs into design implications

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/infrasity-labs/dev-gtm-claude-skills --skill jobs-to-be-done

After installing, type/jobs-to-be-donein Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported