MCPInstall

define-jtbd-canvas

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.

Installs
774
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/product-on-purpose/pm-skills --skill define-jtbd-canvas
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads define-jtbd-canvas automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

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

When NOT to Use

  • You need a person-shaped artifact (goals, behaviors, quotes) for design or marketing work -> use foundation-persona; the canvas captures the job, the persona captures the person
  • You have no customer research yet -> synthesize interviews first with discover-interview-synthesis; the canvas's insights must trace to research, not assumptions
  • You are framing one specific problem to solve now -> use define-problem-statement
  • You need to map opportunities to a measurable outcome for prioritization -> use define-opportunity-tree

Instructions

When asked to create a JTBD canvas, follow these steps:

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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. A complete canvas fills every template section: Job Overview; Job Performer; The Circumstance; Job Statement; Functional Job; Emotional Job; Social Job; Competing Solutions; Hiring Criteria; Insights and Implications; Supporting Quotes; and Questions for Further Research.

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.

FAQ

What does the define-jtbd-canvas skill do?

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.

How do I install define-jtbd-canvas?

Run npx skills add https://github.com/product-on-purpose/pm-skills --skill define-jtbd-canvas in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/define-jtbd-canvas/ (personal) or .claude/skills/define-jtbd-canvas/ (project).

Which AI agents can use define-jtbd-canvas?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is define-jtbd-canvas safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains define-jtbd-canvas?

It is published by product-on-purpose in product-on-purpose/pm-skills. It has 774 recorded installs.

More from product-on-purpose/pm-skills

View all →

deliver-acceptance-criteria

product-on-purpose/pm-skills

Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.

Testing & QA1.1K installs

deliver-prd

product-on-purpose/pm-skills

Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.

deliver-user-stories

product-on-purpose/pm-skills

Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.

deliver-edge-cases

product-on-purpose/pm-skills

Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.

Testing & QA878 installs

discover-competitive-analysis

product-on-purpose/pm-skills

Creates a structured competitive analysis comparing features, pricing, and positioning across 3-5 direct and indirect competitors, with a 2x2 map and actionable strategic recommendations. Use before entering a market, planning differentiation, or after losing deals. For market size rather than competitor positioning, use discover-market-sizing instead.

define-problem-statement

product-on-purpose/pm-skills

Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.

Business & Finance821 installs

Popular other skills

View category →

hyperframes-cli

heygen-com/hyperframes

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

1.3M installs

triage

mattpocock/skills

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

1M installs

ask-matt

mattpocock/skills

Ask which skill or flow fits your situation. A router over the skills in this repo.

778.4K installs

to-questionnaire

mattpocock/skills

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

508.9K installs

wait-what

mattpocock/skills

Stop. That last message did not land: re-pitch it.

459.7K installs

loop-me

mattpocock/skills

Grill me about specs for the workflows I want to build, within this workspace.

447.9K installs