What is the Jobs to Be Done canvas — and what it captures that personas miss.
Short answer
The Jobs to Be Done (JTBD) canvas is a visual synthesis tool that documents the job a customer is trying to get done, the context in which they hire a product to do it, and the functional, emotional, and social outcomes they're seeking. It's populated from JTBD interviews and helps teams understand why customers switch — not just what features they use.
The Jobs to Be Done framework was developed by Clayton Christensen and colleagues at Harvard Business School and further operationalized by Bob Moesta and Chris Spiek at the ReWired Group. The canvas is a structured way to document the output of JTBD interviews.
Core sections of a JTBD canvas.
The Job Statement. A one-sentence description of what the customer is trying to accomplish, written from the customer's perspective: "When [context], I want to [motivation], so I can [desired outcome]." The job is functional — it describes an action and an outcome, not a feeling or a feature.
Context. When and where does the job arise? What triggered the need? Context explains why the customer is looking for a solution at this particular moment. Context is often situational: a life change, a growing frustration that crossed a threshold, an external event.
Functional outcomes. What does success look like practically? Getting the report finished faster. Having the data organized in one place. Shipping the code without downtime.
Emotional outcomes. How does the customer want to feel after the job is done? Confident. Relieved. In control. Proud. Emotional outcomes are often more stable motivators than functional ones — a customer switches products when the new one makes them feel differently, not just when it works faster.
Social outcomes. How does the customer want to be perceived by others because of their choice? This is the social signaling dimension — choosing the tool that their peers respect, that makes them look capable, that fits their professional identity.
Competing solutions (old job executors). What did the customer use before? The competition is not always another product — often it's a spreadsheet, a manual process, or the customer's own time. Understanding what was "fired" when your product was "hired" is as important as understanding why your product was chosen.
Anxiety. What almost stopped the customer from switching? What fears or frictions were in the way? This section surfaces the points of resistance that product, marketing, and onboarding need to address.
The switching story timeline. Many JTBD canvases include a timeline section: First thought → Passive looking → Active looking → Purchase decision. This is the chronological narrative of how the customer moved from awareness to adoption.
How it differs from personas. A persona says "Who is our user?" with demographic and behavioral details. A JTBD canvas says "Why did our user hire this product?" — the causal story behind the switch. Personas describe segments; JTBD canvases describe motivations. JTBD is more useful for copywriting, onboarding, and product positioning; personas are more useful for cross-team communication about who you're building for.
After JTBD interviews, synthesize findings onto a canvas whiteboard. Snap it with BoardSnap and the AI reads the job statement, context, outcomes, and switching story and produces a structured JTBD summary.
Frequently asked
Who created the Jobs to Be Done framework?
Clayton Christensen and his colleagues at Harvard Business School developed the foundational theory, with key contributions in his book *The Innovator's Dilemma* (1997) and later *Competing Against Luck* (2016). Bob Moesta operationalized the interview and canvas methodology through his work at the ReWired Group, making it a practical product development tool.
How many JTBD interviews do you need before building the canvas?
5–8 interviews to start, looking for pattern convergence. Build the canvas after each batch of 3–4 interviews and update it as new interviews surface new context or contradictions. The canvas is a living document during early discovery — it stabilizes once interviews stop producing new insights.
Is JTBD better than user stories?
They serve different purposes. User stories ("As a [user], I want to [action] so that [outcome]") are delivery tools — they communicate what to build to an engineering team. JTBD is a discovery tool — it explains why to build it at all. JTBD findings should feed into user stories, not replace them.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.