jobs-to-be-done
owl-listener/designer-skills
Map functional, emotional, and social jobs to uncover deeper user motivations beyond features.
What is jobs-to-be-done?
Jobs-to-Be-Done (JTBD) is a framework for understanding why users choose products by focusing on the underlying job they're trying to accomplish. Use this skill when you need to reframe design decisions around motivation, context, and desired outcomes rather than product features or user demographics.
- Identify core jobs users are trying to accomplish in specific situations
- Map three dimensions of jobs: functional (practical task), emotional (feeling), and social (perception)
- Define job lifecycle stages from discovery through conclusion
- Articulate outcome expectations that define success for each job dimension
- Analyze how current solutions underserve user needs
- Surface design opportunities by identifying gaps between jobs and existing products
How to install jobs-to-be-done
npx skills add https://github.com/owl-listener/designer-skills --skill jobs-to-be-doneHow to use jobs-to-be-done
- 1.Gather user research data (interviews, observations, or product context) if available
- 2.Identify the core job the user is trying to accomplish in a specific situation
- 3.Map the three job dimensions: functional task, emotional desire, and social perception
- 4.Define the full job lifecycle stages (define, locate, prepare, confirm, execute, monitor, modify, conclude)
- 5.Document outcome expectations for each dimension to clarify what success means
- 6.Analyze current solutions to see how users are hiring products for this job
- 7.Identify gaps and opportunities where current solutions fall short
- 8.Present findings in a structured JTBD map with clear design implications
Use cases
- Reframing a feature request to understand the underlying motivation and context
- Analyzing interview data to extract job statements and uncover unmet needs
- Comparing how different user segments "hire" competing products for the same job
- Identifying why a product launch failed by mapping misalignment between product and actual job
- Discovering new market opportunities by finding jobs that existing solutions underserve
- UX researchers conducting user research and analysis
- Product managers defining strategy around user motivation
- Designers reframing problems before ideation
- Teams conducting competitive analysis or market discovery
jobs-to-be-done FAQ
JTBD focuses on what users are trying to accomplish and why (motivation, context, outcomes), while personas describe who users are (demographics, behaviors). Use user-persona skill for demographic profiling; use JTBD when you need to understand deeper motivations.
Functional is the practical task (e.g., 'organize my files'), emotional is the feeling sought (e.g., 'feel in control'), and social is how they want to be perceived (e.g., 'appear organized and professional').
Follow the format: 'When [situation], I want to [motivation], so I can [expected outcome].' Example: 'When I'm managing multiple projects, I want to see all tasks in one place, so I can prioritize without context-switching.'
Yes. Different users or the same user in different contexts may hire a product for different jobs. Map each distinct job separately to avoid conflating different motivations.
Use the job mapping to prioritize features that directly serve the core job and its outcome expectations. Eliminate features that don't align with the job. Test design solutions against whether they reduce friction in the job lifecycle.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: jobs-to-be-done
description: 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.
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
- Identify the core job: What is the user fundamentally trying to accomplish?
- 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
- Define job stages: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
- Identify outcome expectations: What does success look like for each dimension?
- Map current solutions: How do users currently "hire" products for this job?
- Find opportunities: Where are current solutions underserving the job?
- Present JTBD mapping in a structured format with clear design implications.
Related skills
More from owl-listener/designer-skills and the wider catalog.
journey-map
Map a persona's end-to-end experience across stages, touchpoints, emotions, and pain points.
law-of-common-region
Apply visual boundaries and containers to group elements clearly, regardless of spacing.
law-of-proximity
Apply spatial closeness to group elements—the most fundamental Gestalt layout principle.
layout-grid
Define responsive grids with columns, gutters, margins, and breakpoint behavior for consistent page layouts.
loading-states
Design waiting experiences with spinners, skeletons, optimistic updates, and progressive reveal.
localization-design
Design UI that adapts to any language, script, and cultural context without breaking.