JTBD Canvas

Structured workshop synthesizing JTBD research into a visual canvas mapping job context, struggle, alternatives considered, decision criteria, and desired outcome.

Process

Key Fields

Question it answers	What is the core job definition based on research? What outcomes matter most? How can success be measured by job outcomes instead of feature adoption?
Participants & timing	4-8 team members (product, design, business) · 2-3 hour workshop · 1-2 weeks refinement
AI compatibility	AI generates initial canvas drafts from research data and identifies conflicting job interpretations; workshop facilitation requires human judgment.
Output	1-3 completed JTBD canvases, job outcome metrics, strategic implications, roadmap recommendations aligned to job

Use when

Competitive category where differentiation is unclear
Team is misaligned on why customers will choose the product
Metrics focus on feature adoption rather than outcome achievement
Building a new product or category with uncertain positioning

Skip when

Job definition is already clear and documented
Insufficient qualitative research data to ground the canvas

Common Mistakes

Canvas as decoration

Completing the template as a framework exercise then ignoring the insights in product decisions. Use canvas findings to make specific choices: feature priority, messaging, success metrics.

Conflating job with solution

"Job" becomes "they need a mobile app" instead of "they need to track time with minimal friction across contexts." Job describes the outcome, not the solution.

Generic canvas that describes everyone

A job so broad it applies to 80% of users provides no differentiation. The best job definitions are specific enough to exclude users who do not need it.