Jobs to Be Done Canvas: A Step-by-Step Guide

The Tool That Makes JTBD Actionable

Jobs to Be Done is a powerful theory. But theory without structure is philosophy, not strategy. The JTBD Canvas is the structured tool that transforms JTBD thinking into a documented, shareable, and actionable artifact that product teams can use to drive decisions.

If you have ever walked out of a JTBD workshop with sticky notes full of insights and no clear path forward, you know the problem. The Canvas solves it. It provides a single-page framework that captures the job, its context, the job map, desired outcomes, emotional and social dimensions, and the current competitive landscape — all in a format that a product manager can present to an engineering team, a VP can present to a board, or a cross-functional team can use as a working reference.

This guide walks through each section of the JTBD Canvas, explains what goes in it, shows common mistakes, and connects the Canvas to the broader Outcome-Driven Innovation (ODI) process. For the full JTBD methodology, see our Complete Guide to Jobs to Be Done.

The JTBD Canvas: Structure and Sections

The JTBD Canvas is organized into seven core sections. Each section captures a specific aspect of the job and its context. Think of it as a structured summary of your JTBD research — the deliverable that ensures alignment across your product team.

Section 1: The Job Statement

What goes here: A single, clear statement of the job the customer is trying to get done, following the syntax: [verb] + [object] + [contextual clarifier].

Example: “Transport materials from ground level to elevated work positions on construction sites.”

Common mistakes:

• Too narrow: “Operate the loader crane” is not a job — it embeds a solution. The job exists independently of any product.
• Too broad: “Complete construction projects successfully” is too abstract to be actionable. You need a level of abstraction where the job is specific enough to generate measurable outcomes but broad enough to encompass multiple solution categories.
• Solution-embedded: “Use our CRM to manage customer interactions” includes a solution. “Manage customer interactions across touchpoints and time” is solution-agnostic.

The test: If your job statement mentions a specific product, technology, or brand, it is too narrow. If it describes an entire business function or life goal, it is too broad. The right level typically describes a goal that a single person can accomplish in a defined context.

Section 2: Job Executor

What goes here: A clear description of the person who performs the job. Not the buyer, not the decision-maker — the executor.

Why this matters: In B2B, the job executor is often different from the buyer. A loader crane operator executes the job; a fleet manager buys the crane. A nurse administers enteral feeding; a hospital procurement committee buys the feeding system. The Canvas should specify the executor because their outcomes drive product design, even when someone else signs the purchase order.

What to include:

• Role/title
• Context in which they perform the job
• Frequency of job execution
• Expertise level (novice, experienced, expert)
• Key constraints they face (time pressure, regulatory requirements, physical environment)

Common mistake: Defining the executor as a persona rather than a role. “Efficient Eva, 38, works at a mid-size hospital” is a persona. “ICU nurse responsible for administering and monitoring enteral feeding during 12-hour shifts” is a job executor description. The persona tells you who she is. The executor description tells you what she does and under what constraints.

Section 3: Job Map

What goes here: The eight stages of the Universal Job Map, each populated with the specific activities the job executor performs at that stage.

The eight stages:

1. Define — Determine what needs to be done, plan the approach
2. Locate — Find and gather inputs, materials, information
3. Prepare — Set up the environment and resources
4. Confirm — Verify readiness before execution
5. Execute — Perform the core task
6. Monitor — Track progress and performance
7. Modify — Make adjustments when needed
8. Conclude — Finish, document, clean up, prepare for next cycle

How to populate it: For each stage, write 2-4 sentences describing what the job executor does. Draw from your JTBD interview data (see our interview guide for the process).

Common mistakes:

• Skipping stages: Not every stage is equally important for every job, but every stage exists. Even if the Modify stage is brief (“if the lift goes wrong, abort and restart”), it should be documented. Skipping stages means skipping outcomes.
• Mixing stages: “Set up the equipment and begin the procedure” conflates Prepare and Execute. Keep them separate. The boundary between preparation and execution is where many underserved outcomes live.
• Describing product features instead of job activities: “The display shows the load weight” is a product feature. “Verify that the load weight is within the crane’s capacity for the current configuration” is a job activity. The Canvas should describe what the executor does, not what the product does.

Section 4: Desired Outcomes

What goes here: The specific, measurable criteria the job executor uses to judge how well the job is getting done, organized by job map stage.

Outcome statements follow the syntax: [Direction of improvement] + [metric] + [object of control] + [contextual clarifier]

Examples organized by stage:

Prepare:

• “Minimize the time it takes to configure the system for the specific procedure type”
• “Minimize the likelihood of selecting an incorrect setup configuration”

Execute:

• “Minimize the variability in performance across different operating conditions”
• “Minimize the force required to make precise adjustments during the procedure”

Monitor:

• “Minimize the time between a deviation occurring and being alerted”
• “Minimize the number of separate information sources that must be checked during the procedure”

Conclude:

• “Minimize the time required to complete mandatory documentation after the procedure”
• “Minimize the effort required to clean and prepare the equipment for the next use”

How many outcomes per stage: A well-mapped job typically has 50–150 total desired outcomes, distributed across all eight stages. The Execute stage usually has the most (30-40), but significant outcomes exist at every stage.

Common mistakes:

• Writing solutions instead of outcomes: “Have an automatic calibration feature” is a solution. “Minimize the time it takes to calibrate the equipment before use” is an outcome.
• Being too vague: “Make the process faster” is not measurable. “Minimize the time it takes to transition from standby to operational mode” is measurable.
• Missing the direction of improvement: Every outcome should start with “minimize” (or occasionally “maximize,” though “minimize” covers most cases because you are minimizing time, effort, likelihood of error, variability, etc.).

The desired outcome statement is the fundamental innovation metric. It is what customers use to measure value, even if they have never articulated it explicitly. The Canvas section on desired outcomes is where the real intellectual work happens — getting these statements right is the difference between a tool that drives innovation and a poster on a wall.

Section 5: Emotional and Social Jobs

What goes here: The emotional experiences the executor wants to have (or avoid) and the social perceptions they want to create (or prevent) while performing the job.

Emotional jobs examples:

• “Feel confident that the procedure will succeed”
• “Avoid the anxiety of equipment failure during a critical operation”
• “Feel in control of the process at all times”

Social jobs examples:

• “Be perceived by colleagues as technically competent”
• “Demonstrate to management that the investment in new equipment was justified”
• “Avoid being seen as the person who caused a delay or error”

Common mistakes:

• Dismissing them as soft: In B2B, emotional and social jobs consistently account for 30-40% of underserved outcomes. Leaving this section empty is leaving market intelligence on the table.
• Confusing emotional jobs with user satisfaction: “Feel satisfied with the product” is not an emotional job. Emotional jobs relate to the experience of performing the job, not the experience of using the product. “Feel confident that the diagnosis is correct before communicating it to the patient’s family” is an emotional job.

For a comprehensive treatment of these dimensions, see Functional, Emotional, and Social Jobs: Understanding the Full Picture.

Section 6: Current Solutions and Alternatives

What goes here: Every way the job executor currently accomplishes the job or parts of the job. This includes:

• Your product
• Direct competitors’ products
• Products from adjacent categories
• Manual methods and workarounds
• “Do nothing” (tolerating the current situation)

Why this matters: The Canvas should capture the full competitive landscape as seen through the job lens, not the product lens. A loader crane’s competition includes not just other loader cranes but telehandlers, tower cranes, and manual methods. A feeding pump’s competition includes gravity feeding sets, manual syringe feeding, and oral nutritional supplements.

What to note for each alternative:

• Which stages of the job does it address?
• Which outcomes does it serve well?
• Which outcomes does it leave underserved?
• What trade-offs does the executor accept when using it?

Section 7: Opportunity Landscape

What goes here: A summary of the quantitative analysis — which outcomes are underserved, which are overserved, and what strategic opportunities emerge.

This section is populated after the quantitative survey phase. For each outcome, the opportunity score = Importance + max(Importance - Satisfaction, 0). Outcomes with scores above 12 (on a 10-point scale) represent significant underserved needs. Outcomes with scores below 6 are overserved.

What to capture:

• Top 10-15 underserved outcomes (highest opportunity scores)
• Overserved outcomes (candidates for feature reduction or cost optimization)
• Segment-level variation (do different customer segments have different patterns of unmet needs?)
• Strategic direction: given the opportunity landscape, what type of innovation strategy is appropriate? (Differentiated, discrete, dominant, or disruptive — the four ODI growth strategies)

Filling the Canvas: A Practical Walkthrough

Let us walk through filling a JTBD Canvas for a specific example: an enteral feeding system in a hospital ICU setting.

Step 1: Define the Job

After initial discussions with the product team and 5-6 exploratory interviews with ICU nurses:

Job statement: “Deliver precise nutritional support to critically ill patients who cannot eat orally.”

Job executor: ICU nurse responsible for administering and monitoring enteral feeding during 12-hour shifts. Manages 2-4 patients simultaneously. Works under time pressure with frequent interruptions. Must document all feeding activities for compliance.

Step 2: Map the Job

Based on 18 JTBD interviews with ICU nurses across four hospitals:

1. Define: Receive the nutrition order from the physician/dietitian. Determine the feeding schedule, formula type, and rate based on the patient’s current condition.
2. Locate: Gather the formula, feeding set, pump, and patient chart. Verify formula availability.
3. Prepare: Set up the feeding pump, prime the tubing, connect to the patient’s access device, program the pump settings.
4. Confirm: Verify pump settings against the order. Confirm the tube placement (particularly for nasogastric tubes). Check for any contraindications.
5. Execute: Initiate the feeding. Manage the infusion alongside other patient care responsibilities.
6. Monitor: Check feeding progress at regular intervals. Monitor for tolerance issues (residual volumes, discomfort, aspiration risk). Respond to pump alarms.
7. Modify: Adjust feeding rate if tolerance issues arise. Pause or stop feeding if complications occur. Coordinate with the physician on protocol changes.
8. Conclude: Disconnect the feeding set. Flush the access device. Document the feeding session (volume delivered, duration, any complications, tolerance assessment).

Step 3: Capture Desired Outcomes

From the 18 interviews, 127 desired outcomes were captured. Here is a selection:

Prepare:

• “Minimize the time it takes to prime and set up the feeding system”
• “Minimize the likelihood of air entering the feeding line during setup”
• “Minimize the number of steps required to program the pump for a standard feeding order”

Confirm:

• “Minimize the time it takes to verify that pump settings match the physician’s order”
• “Minimize the uncertainty about whether the tube is properly positioned before starting the feed”

Monitor:

• “Minimize the time between a tolerance issue developing and becoming aware of it”
• “Minimize the number of false alarms that require the nurse to interrupt other tasks”
• “Minimize the effort required to assess gastric residual volume during the feeding”

Conclude:

• “Minimize the time required to document the feeding session in the patient record”
• “Minimize the likelihood of an incomplete or inaccurate feeding record”

Step 4: Capture Emotional and Social Jobs

Emotional:

• “Feel confident that the feeding is progressing safely while attending to other patients”
• “Avoid the anxiety of a feeding complication occurring while dealing with another patient”
• “Feel competent when managing complex feeding protocols”

Social:

• “Be perceived by the nursing team as reliable in managing enteral feeding”
• “Demonstrate to the charge nurse that feeding protocols are followed consistently”

Step 5: Map Current Solutions

• Fresenius Kabi Applix pump: Strong on Execute, moderate on Monitor, weak on Conclude (documentation)
• Manual gravity feeding: Low cost, but requires constant monitoring (poor Monitor stage)
• Parenteral nutrition (IV): Alternative job approach when enteral is not tolerated
• Oral nutritional supplements: Alternative when some oral intake is possible

Step 6: Populate the Opportunity Landscape

After surveying 280 ICU nurses across DACH-region hospitals, the highest-opportunity outcomes were:

1. Minimize false alarm frequency (opportunity score: 14.2)
2. Minimize documentation time (13.8)
3. Minimize uncertainty about tube position confirmation (13.1)
4. Minimize the effort to assess gastric residual volume (12.9)
5. Minimize the time to detect a tolerance issue (12.7)

The pattern: Monitor and Conclude stages dominated the opportunity landscape. The core Execute stage was relatively well-served by existing products.

From Canvas to Product Decisions

The completed Canvas is not an end in itself. It is the input to product strategy decisions. Here is how it connects to downstream activities:

Feature Prioritization

The underserved outcomes from the opportunity landscape become the criteria for evaluating feature concepts. Instead of debating which features to build, ask: “Which feature concepts address the outcomes with the highest opportunity scores?” This is a data-driven conversation, not an opinion-driven one.

Competitive Positioning

The Current Solutions section reveals where competitors are strong and where they are weak — at the outcome level, not the feature level. Position your product against the outcomes that matter most and where competitors fall short. For the complete process of translating Canvas insights into product specifications, see From JTBD to Product Requirements.

Market Segmentation

If the survey data reveals distinct customer segments with different patterns of unmet needs, the Canvas should be duplicated — one per segment. Each segment may require different product configurations, different messaging, and potentially different pricing.

Innovation Roadmap

The opportunity landscape provides a multi-year innovation roadmap. High-opportunity outcomes that can be addressed with current technology become near-term priorities. High-opportunity outcomes that require new technology become long-term R&D investments. Overserved outcomes become candidates for simplification or cost reduction.

Common Canvas Mistakes and How to Avoid Them

Mistake 1: Treating the Canvas as a One-Time Document

The Canvas should be a living document. Jobs do not change, but customer satisfaction shifts as competitors innovate and new solutions enter the market. Update the opportunity landscape annually (at minimum) through a refresh survey.

Mistake 2: Filling the Canvas Without Interview Data

A Canvas filled in a conference room by the product team — without customer interviews — is fiction. It reflects what the team believes customers need, which is precisely the assumption JTBD is designed to challenge. Always base the Canvas on actual interview data.

Mistake 3: Skipping the Quantitative Step

A Canvas with qualitative outcomes but no opportunity scores is incomplete. It tells you what outcomes exist but not which ones matter most. The quantitative survey is what transforms the Canvas from a descriptive tool into a strategic tool.

Mistake 4: One Canvas for Multiple Stakeholders

If the job has multiple executors (nurse, dietitian, patient), create a separate Canvas for each. Collapsing multiple executors into a single Canvas obscures the differences in their outcomes and creates a muddled picture that serves no one well.

Mistake 5: Ignoring the Emotional and Social Sections

In industrial and MedTech contexts, teams often fill the functional sections rigorously and leave emotional and social sections sparse or empty. This is a data gap that leads to strategic blind spots. Invest the interview time to populate these sections properly.

Frequently Asked Questions