Jobs to be done framework

What is the Jobs to Be Done Framework?

Definition and origin

Jobs to be done (JTBD) is a customer-centric framework that centers on understanding the progress people seek in specific circumstances. Rather than simply cataloguing product features, JTBD asks what goal a customer is trying to achieve and why the current options fall short. The concept gained prominence through theory and practice developed by Clayton Christensen and colleagues, who argued that people “hire” products and services to make progress in their lives. Over time, the framework broadened from innovation theory into a practical toolkit for product, marketing, and education teams seeking deeper customer insight.

Key ideas and terminology

At its core, JTBD focuses on jobs, outcomes, and hiring decisions. A “job” is the trigger-driven progress a user seeks, often with functional, social, and emotional dimensions. An “outcome” is a desired result, typically measurable and constrained by time, money, or other limits. “Hiring” a solution describes choosing a product or service to make progress, while “switching” refers to moving away from a current option to a different one. The language emphasizes progress over solution features, guiding teams to uncover authentic needs rather than assuming the best solution upfront.

Why JTBD matters for product, marketing, and education

For product teams, JTBD helps identify high-impact opportunities tied to real customer progress, aligning backlog with outcomes users value. Marketers can craft messages that resonate around jobs—clarifying why a product matters and how it delivers measurable progress. In education, JTBD supports designing learning experiences that directly connect to career and life goals, ensuring curricula and assessments measure what matters to learners and employers. Across domains, JTBD promotes a shared language for cross-functional collaboration focused on customer success.

Core Concepts: Jobs, Outcomes, and Hiring

Job-to-be-Done concept and motivation

A job represents the intended progress a person seeks in a specific situation. Motivation to hire a solution often stems from a gap between the current state and the desired state. This gap can be functional (completing a task faster), social (gaining status or acceptance), or emotional (reducing anxiety or increasing confidence). Understanding the full spectrum of motivation helps teams design or select offerings that truly enable progress.

Desired outcomes and constraints

Outcomes are the measurable changes users associate with getting the job done. They include metrics like time saved, accuracy improved, and ease of use. Constraints—such as budget, time, or learning curve—shape what outcomes are realistic. A complete JTBD view captures both the desired outcomes and the constraints that influence whether a solution is acceptable.

Hiring a solution vs. switching to alternatives

When a user faces a job, they consider multiple options, including competitors, workarounds, or doing nothing. “Hiring” a solution means selecting an option that best enables progress given trade-offs. “Switching” involves abandoning an existing approach in favor of something perceived as superior for the job. Framing decisions this way keeps teams focused on competing on outcomes, not just features.

JTBD Process: Discovery to Definition

Exploration and opportunity discovery

The process begins with exploring customers’ circumstances to surface underserved jobs. Methods include interviews, ethnographic observation, and rapid experimentation. The aim is to map not just what customers say they need, but the real progress they are trying to achieve in their daily routines, work, or learning paths.

Formulating a precise JTBD statement

A precise JTBD statement follows a simple structure: When [situation], I want to [job], so I can [outcome], but [constraint or barrier]. This clarity helps cross-functional teams align around a single, testable goal. Templates can be adapted to different domains, but the core intent remains: specify context, intention, and desired progress.

Validating with customer data

Validation combines qualitative insights with quantitative data. Interview findings, behavioral analytics, and small-scale experiments triangulate what the job is, how customers measure progress, and whether proposed solutions deliver the expected outcomes. Validation reduces guesswork and strengthens confidence before committing to a roadmap.

Research Methods: Customer Interviews and Observations

Interview techniques for uncovering jobs

Effective JTBD interviews use open-ended prompts, scenario-based questions, and storytelling. Researchers listen for explicit jobs as well as implicit pressures, such as failed attempts or workarounds. Probing questions help reveal the true progress customers seek in real contexts, not just what they say they want in the abstract.

Avoiding bias and leading questions

To reduce bias, researchers should avoid confirming preconceived notions and steer clear of binary yes/no questions. Neutral prompts and varied scenarios encourage genuine responses. Recording verbatim quotes and observing nonverbal cues can also help uncover subtleties that sales pitches often overlook.

Capturing true jobs, pains, and constraints

Capturing the full picture means documenting the core job, related jobs, the pains experienced, and the constraints that limit progress. A robust capture includes multiple customer segments, triangulated sources, and notes on contexts that influence decision-making. This holistic view informs accurate job statements and meaningful outcomes.

Crafting Job Statements and Outcome Statements

Structure of a JTBD statement

A typical JTBD statement follows: When [situation], I want to [job], so I can [outcome], with [constraint]. This structure centers the user’s context, objective, and success metric, providing a clear target for product and learning design alike. Variants can emphasize social or emotional dimensions if they drive progress in the given context.

Writing measurable outcome statements

Outcome statements should be specific and measurable. Each outcome is a metric the team can track, such as time to complete a task, cost reduction, error rate, or user satisfaction. Writing outcomes in a testable form enables dependable validation as features are developed or curricula are revised.

Practical examples and templates

• Job: When preparing for a job interview, I want to practice effectively, so I can present confidently, with a time-efficient plan.
• Outcome: Reduce interview preparation time by 40% while increasing perceived readiness by 25%.
• Constraint: Limited access to mentors and flexible study hours.

Templates can be adapted to different domains, such as education, product design, or service delivery, maintaining the core structure while tailoring specifics to context.

JTBD Mapping and Prioritization

Components of a JTBD map

A JTBD map connects core jobs to related jobs, desired outcomes, constraints, and current solutions. It visualizes progress pathways, highlights gaps between outcomes and existing capabilities, and reveals complementary jobs that amplification can unlock. The map serves as a living artifact guiding cross-functional planning.

Prioritization criteria and scoring

Prioritization weighs importance of outcomes, current satisfaction levels, feasibility, and market or learner impact. Scoring models often combine desirability, feasibility, and impact to surface top priorities. A transparent scoring process helps teams align on where to invest first.

Linking JTBD to product backlog

JTBD maps translate into backlog items by framing each feature or learning module as a response to a high-priority outcome. This linkage ensures that development work remains anchored in customer progress and that success criteria are observable and measurable.

Applying JTBD to Product Strategy and Roadmapping

Roadmapping by jobs and outcomes

Roadmaps organized around jobs guide teams to deliver outcomes rather than random features. Each roadmappath aligns with specific jobs, sets success criteria, and maps dependencies. This approach clarifies trade-offs and communicates intent to stakeholders beyond the product team.

Defining success metrics linked to jobs

Success metrics tie directly to the outcomes customers value. Examples include time-to-value, task completion rate, skill acquisition, or retention linked to learning milestones. Linking metrics to jobs makes progress tangible and testable across releases and curricula.

Roadmap examples and templates

• Quarterly roadmap by jobs: Q1 targets for job A outcomes, Q2 for job B, etc.
• Feature-portfolio map keyed to top outcomes, with milestones and metrics.
• Education-focused roadmap aligning modules to career outcomes and employer requirements.

Marketing, Messaging, and Product Positioning with JTBD

Messaging aligned with customer jobs

Messaging should articulate the job customers are trying to accomplish, the progress they seek, and how the offering uniquely helps them overcome constraints. This focus reduces generic claims and strengthens resonance with real-world use cases.

Positioning and value propositions by JTBD

Positioning varies by job segment. A single product may deliver multiple value propositions depending on the job context, outcomes prioritized, and constraints faced by different learner groups or user cohorts. Clear articulation of positioning helps campaigns target the right audiences with relevant benefits.

Campaign ideas and storytelling

Campaigns can center on stories of learners or users who achieved meaningful progress with the product or program. Narrative arcs around a job, the obstacles overcome, and measurable outcomes create compelling, credible messaging that aligns with real needs.

JTBD in Education and Career Development

Designing learning experiences around jobs

Education benefits from framing curricula around the jobs learners want to accomplish, not just discrete topics. By designing experiences that promote tangible progress, educators can improve engagement and outcomes. This shift often requires modular content, practical projects, and real-world assessments.

Aligning curriculum with career outcomes

Curricula should map to concrete career outcomes sought by learners and employers. Articulating these mappings helps students understand the relevance of their studies and supports alignment with industry needs, internships, and credentialing pathways.

Assessment and long-term impact

Assessment should measure forward-looking outcomes—such as job-ready skills, problem-solving ability, and lifelong learning habits—rather than only knowledge recall. Long-term impact tracking helps institutions demonstrate value to students, employers, and funders.

Implementation Playbook: Tools, Templates, and Teams

JTBD interview guides

Practical guides provide standard prompts, scenario cards, and note templates to consistently capture jobs, pains, and outcomes. They help teams scale qualitative research across segments while preserving depth of insight.

Job statement and outcome templates

Templates standardize how jobs and outcomes are captured and shared. They enable rapid synthesis across interviews and ensure that every insight can be translated into action, such as a backlog item or an evaluation metric.

Cross-functional roles and governance

JTBD initiatives require collaboration across product, design, engineering, marketing, and education teams. Clear governance—decision rights, review cadences, and documentation standards—ensures the approach remains disciplined and adaptable.

Metrics, Evaluation, and ROI

Key JTBD metrics to track

Track metrics that reflect progress on jobs and outcomes, such as time-to-complete, completion quality, user adoption of new learning paths, and satisfaction with achieved outcomes. These metrics should be easy to observe and tied to explicit statements of the job.

Measuring impact and ROI

Impact is measured by improvements in productivity, learning gains, employability, or other outcome-based indicators. ROI calculations can factor in reduced time to competency, increased retention, or higher job placement rates, depending on context.

Common missteps in evaluation

Common pitfalls include focusing on feature usage instead of outcomes, overfitting to a single customer segment, or neglecting long-term effects. A balanced evaluation plan uses mixed methods and revisits outcomes as contexts change.

Case Studies and Real-World Examples

Technology product JTBD example

In a software tool designed for knowledge workers, the core job may be “organize information to support quick, accurate decision-making.” Outcomes focus on speed of finding relevant data, accuracy of results, and ease of collaboration. A JTBD-led roadmap would prioritize search reliability, knowledge sharing workflows, and onboarding efficiency.

Service design and JTBD example

For a service design project—such as a customer support experience—the job might be “resolve issues with minimal effort and wait time.” Outcomes include reduced resolution time, higher first-contact success, and improved customer trust. Mapping jobs to service touchpoints guides process redesign and staff training.

Education-sector JTBD example

In an educational program, the job could be “prepare for a career with demonstrable skills.” Outcomes emphasize portfolio quality, interview readiness, and measurable competence in key domains. Curriculum updates, assessments, and industry partnerships are then aligned to these outcomes.

Trusted Source Insight

Key takeaway from our trusted source: World Bank education topic

Trusted Source Insight: World Bank education insights emphasize aligning learning outcomes with labor market needs and building human capital through relevant skills. They stress measuring learning gains, improving equity in access to education, and fostering lifelong learning to boost productivity and employment opportunities. https://www.worldbank.org/en/topic/education