Define Jtbd Canvas
npx machina-cli add skill product-on-purpose/pm-skills/define-jtbd-canvas --openclawname: define-jtbd-canvas description: Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning. phase: define version: "2.0.0" updated: 2026-01-26 license: Apache-2.0 metadata: category: problem-framing frameworks: [triple-diamond, lean-startup, design-thinking] author: product-on-purpose
Jobs to be Done Canvas
A Jobs to be Done (JTBD) canvas captures the complete picture of why customers "hire" products to make progress in their lives. Based on Clayton Christensen's framework, JTBD goes beyond features and demographics to understand the underlying motivations—functional, emotional, and social—that drive customer behavior.
When to Use
- When deeply researching customer motivations before building
- To reframe product positioning around customer progress
- When existing personas feel too surface-level or demographic
- During competitive analysis to identify why customers switch
- When designing marketing messages that resonate
- To align team on who the customer really is and what they need
Instructions
When asked to create a JTBD canvas, follow these steps:
-
Identify the Job Performer Define who is doing this job. Go beyond demographics to capture the circumstance they're in. The same person can have different jobs in different situations.
-
Articulate the Circumstance Describe when and where this job arises. Jobs are triggered by specific situations. Understanding context helps predict when customers will seek a solution.
-
Write the Job Statement Use the format: "When [situation], I want to [motivation], so I can [desired outcome]." The job statement captures the core progress the customer seeks.
-
Define the Functional Job What is the practical task the customer needs to accomplish? This is the tangible, measurable part of the job. Be specific about what "done" looks like.
-
Capture the Emotional Job How does the customer want to feel during and after the job? Emotional jobs often drive decisions more than functional ones. Include both desired feelings and feelings to avoid.
-
Identify the Social Job How does the customer want to be perceived by others? Social jobs relate to status, identity, and relationships. Not all jobs have strong social dimensions.
-
Map Competing Solutions What are customers currently "hiring" to do this job? Include direct competitors, indirect alternatives, and non-consumption (doing nothing). Understanding current solutions reveals what to compete against.
-
Define Hiring Criteria What makes customers choose one solution over another? What are the "must haves" vs. "nice to haves"? This informs positioning and prioritization.
Output Format
Use the template in references/TEMPLATE.md to structure the output.
Quality Checklist
Before finalizing, verify:
- Job statement follows "When... I want... so I can..." format
- Circumstance is specific (not just "anytime")
- Functional job describes tangible outcome
- Emotional job includes how customer wants to feel
- Competing solutions include non-obvious alternatives
- Insights are based on research, not assumptions
Examples
See references/EXAMPLE.md for a completed example.
Source
git clone https://github.com/product-on-purpose/pm-skills/blob/main/skills/define-jtbd-canvas/SKILL.mdView on GitHub Overview
Defines a Jobs to be Done canvas that captures why customers 'hire' a product by detailing functional, emotional, and social motivations. Rooted in Christensen's JTBD framework, it helps teams move beyond demographics to understand the progress customers seek and how to position offerings.
How This Skill Works
It guides you through a structured sequence: identify the job performer and circumstance, craft the Job Statement in the When..., I want..., so I can... format, and then define the functional, emotional, and social jobs. Finally, map competing solutions and define hiring criteria to reveal gaps and positioning opportunities.
When to Use It
- When deeply researching customer motivations before building
- To reframe product positioning around customer progress
- When existing personas feel too surface-level or demographic
- During competitive analysis to identify why customers switch
- When aligning the team on who the customer really is and what they need
Quick Start
- Step 1: Identify the Job Performer and Circumstance
- Step 2: Write the Job Statement and define Functional, Emotional, and Social jobs
- Step 3: Map competing solutions and define Hiring Criteria
Best Practices
- Start with a precise Job Statement in the When... I want... so I can... format
- Define Functional, Emotional, and Social jobs separately and clearly
- Map current solutions, including non-consumption, to identify gaps
- Ground insights in research data rather than assumptions
- Align hiring criteria with product strategy and positioning
Example Use Cases
- SaaS onboarding: when I begin a new project, I want to set up a workspace quickly, so I can start delivering value fast
- Mobile banking: when I need to transfer money, I want a quick, secure process, so I can complete transactions without anxiety
- Online education: when I study a course, I want clear progress feedback, so I can stay motivated and finish on time
- Ride-hailing app: when I travel in a new city, I want reliable pickup options, so I can reach my destination with minimal planning
- Home repair service: when a problem arises, I want trusted technicians and transparent pricing, so I can fix it with confidence