mcpField
J
jobs-to-be-done

jobs-to-be-done

github.com/owl-listenerDesign & UI3.1k2.1k installsUpdated 8w ago
Repository

About jobs-to-be-done

A UX research skill that applies Jobs-to-Be-Done to understand the motivations behind user behavior. It maps job dimensions, lifecycle stages, desired outcomes, current solutions, and design opportunities.

Key features

  1. 01Map functional, emotional, and social jobs
  2. 02Outline job lifecycle stages
  3. 03Define success outcomes
  4. 04Review current solutions
  5. 05Identify underserved opportunities

Use cases

  1. 01Exploring motivations behind product use
  2. 02Mapping a user's end-to-end job
  3. 03Finding gaps in existing solutions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-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