Free JTBD Canvas — Map Customer Jobs in 10 Minutes

Q: How do you write a JTBD outcome statement?

A JTBD outcome statement follows the format: "When [situation/context], I want to [job to be done], so I can [desired outcome], without [pain or friction]." The statement captures the trigger context, the core job, the success metric, and the barrier to remove. Good outcome statements are solution-agnostic — they describe the customer's goal without prescribing how to achieve it. Teams typically generate 3-5 variations to cover different contexts and priorities, then validate them through customer interviews.

Q: What is the difference between JTBD and user personas?

User personas describe who your customer is (demographics, role, behaviors), while JTBD describes what your customer is trying to accomplish regardless of who they are. A 25-year-old startup founder and a 55-year-old enterprise VP might have the exact same job-to-be-done: "reduce the time spent on status updates so the team can focus on building." JTBD is more actionable for product decisions because it directly connects to the value your product must deliver. Many teams use both — personas for marketing and JTBD for product strategy.

Fill in each section of the canvas to map the full context around your customer's job-to-be-done. Then generate formatted outcome statements you can use in product briefs, PRDs, and stakeholder presentations.

Based on the Jobs-to-Be-Done framework — the product strategy method used by Intercom, Basecamp, and thousands of product teams worldwide.

Build your full JTBD strategy with AI-powered research, personas, and competitor analysis.

Try Rock n Roll →

Quick Answer — What is a JTBD Canvas?

A JTBD canvas is a visual tool that maps the full context around a customer's job-to-be-done: the core job, the situation that triggers it, functional and emotional pains, social pressures, desired gains, current workarounds, and enablers. It helps product teams move from vague user stories to precise outcome statements that drive better roadmap decisions. The output format is: "When [context], I want to [job], so I can [gain], without [pain]."

Load a Template:

Main Job

The core job the customer is trying to get done.

Job Context

When and where does this job happen? What triggers it?

Functional Pains

Practical problems they face trying to do this job (3-5 entries, one per line).

Emotional Pains

How does failing at this job make them feel? (3-5 entries, one per line).

Social Pains

Social or status concerns related to this job (2-3 entries, one per line).

Desired Gains

What does success look like for this job? (3-5 entries, one per line).

Current Solutions

What do they use today to get this job done? (2-3 entries, one per line).

Enablers

What helps them get this job done better? (2-3 entries, one per line).

Build your full JTBD strategy in Rock n Roll

Our AI copilot turns your JTBD canvas into the documentation your team actually needs.

Product Strategy Brief with JTBD research, personas, and competitor analysis
Solution Blueprint covering requirements, user journeys, and UX flows
Implementation Plan with milestones, dependencies, and engineering prompts
Launch-ready handoff kits for Loveable, Bolt, V0, Cursor, Claude Code, or Codex

Generate My Plan

Frequently Asked Questions

What is the Jobs-to-Be-Done framework?

Jobs-to-Be-Done (JTBD) is a product strategy framework that focuses on the underlying goal — the "job" — a customer is trying to accomplish, rather than on demographic profiles or feature requests. Coined by Clayton Christensen in his work on innovation theory, the framework argues that customers "hire" products to get a specific job done. Understanding that job leads to better product decisions, clearer positioning, and higher adoption. A JTBD canvas maps the full context around that job: functional pains, emotional drivers, social pressures, current workarounds, and desired outcomes.

How do you write a JTBD outcome statement?

A JTBD outcome statement follows the format: "When [situation/context], I want to [job to be done], so I can [desired outcome], without [pain or friction]." The statement captures the trigger context, the core job, the success metric, and the barrier to remove. Good outcome statements are solution-agnostic — they describe the customer's goal without prescribing how to achieve it. Teams typically generate 3-5 variations to cover different contexts and priorities, then validate them through customer interviews.

What is the difference between JTBD and user personas?

User personas describe who your customer is (demographics, role, behaviors), while JTBD describes what your customer is trying to accomplish regardless of who they are. A 25-year-old startup founder and a 55-year-old enterprise VP might have the exact same job-to-be-done: "reduce the time spent on status updates so the team can focus on building." JTBD is more actionable for product decisions because it directly connects to the value your product must deliver. Many teams use both — personas for marketing and JTBD for product strategy.

How many jobs should a product address?

Most successful products focus on one primary job and 2-3 related jobs. Trying to address too many jobs leads to a bloated, unfocused product that does everything poorly. Start by identifying the single most important job your target customer needs done, then map the surrounding jobs that naturally cluster with it. For example, Slack's primary job is "keep the team aligned on what's happening right now," with related jobs like "find a past decision quickly" and "loop in the right person without a meeting."