jobs-to-be-done

Map user Jobs-to-Be-Done across functional, emotional, and social dimensions.

2.0k|325|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill jobs-to-be-done-owl-listener
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/jobs-to-be-done
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill jobs-to-be-done-owl-listener

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Identify core jobs and map functional, emotional, and social dimensions.
  • Define job stages and outcome expectations to guide product decisions.
  • Present JTBD mapping with design implications to inform strategy and design.

Quick Start

Analyze a product context and map its Jobs-to-Be-Done to drive design decisions.

Frequently Asked Questions about jobs-to-be-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is Jobs-to-be-Done mapping and how does it reveal user motivations?

Jobs-to-be-Done (JTBD) mapping is a UX research framework that uncovers deeper user motivations by analyzing functional, emotional, and social dimensions of behavior to guide product strategy.

How do I map job stages and outcome expectations for product design?

To map job stages and outcome expectations, you analyze a product context to define the user's core job sequence, capturing expected outcomes at each stage to directly inform design implications and decisions.

Can I use Jobs-to-be-Done to identify opportunities in my current solutions?

Yes, Jobs-to-be-Done analysis identifies current solutions and gaps within job stages, mapping unmet outcome expectations to reveal clear product opportunities and strategic design implications.

When do I need Jobs-to-be-Done mapping in UX research?

You need Jobs-to-be-Done mapping in UX research when you must reframe product decisions around core user motivations, moving beyond surface behavior to understand functional, emotional, and social drivers.

What is the best way to structure a Jobs-to-be-Done framework for strategy?

The best way to structure a Jobs-to-be-Done framework is to sequentially define the core job, map its functional, emotional, and social dimensions, outline job stages, and present outcome expectations with actionable design implications.

Does Jobs-to-be-Done mapping work without existing user research data?

Jobs-to-be-Done mapping requires a defined product context to analyze, but it can structure existing assumptions into functional, emotional, and social dimensions to systematically guide subsequent research and design.