Jobs to Be Done Template: Two Schools, One Spreadsheet

A jobs to be done template is a structured document that captures why customers hire your product, what progress they expect to make, and what stops them from switching. Clayton Christensen's research at Harvard Business School established the framework; Strategyn's Outcome-Driven Innovation quantified it with an 86% success rate. Zoom's 354% customer growth post-COVID and Kroll Ontrack's revenue growth to $200M+ both trace back to identifying the correct job before building.

Two distinct JTBD schools exist, and they produce structurally different templates. This article explains both, tells you which to use at each stage, and gives you a free Google Sheet that covers the full workflow.

Key Takeaways

• The Christensen/Moesta school produces narrative job statements from switch interviews; the Ulwick/ODI school produces measurable outcome scores from surveys.
• The core template covers six components: job statement, job types, four forces, Universal Job Map, switch interview guide, and opportunity scoring.
• A job statement pattern requires 8–12 switch interviews before it converges.
• Get the ready-to-use template in Google Sheets.

Why You Need a JTBD Template

75–85% of new products launched fail financially, and the core diagnosis is building features customers didn't ask for in the form they wanted. A JTBD template forces you to define the customer's goal before writing a single requirement.

Without a structured template, teams run into what Strategyn describes as the cascading definition problem. 80% of product teams can't agree on how to define their own market, which means they can't agree on the customer, their needs, or what to build. That ambiguity compounds into roadmap fragmentation and wasted sprints.

The template also solves an internal communication problem. As u/ToStringMethod in r/ProductManagement (October 2025) explains: "By defining the product through the lens of the job the customer is hiring it to do, you establish outcome-focused language right from inception. That language carries through requirements, design discussions, and ultimately into go-to-market messaging."

The Two JTBD Schools

Before filling in any template, choose which school you're working from.

School 1: Christensen/Moesta (qualitative, narrative) anchors on the customer's struggling moment (the trigger that made them act) and the purchase story. The switch interview is the primary tool: 10–12 one-hour conversations in which recent buyers narrate the chronological story of their decision, not product feedback. The output is a narrative job statement and a Four Forces map.

School 2: Ulwick/ODI (quantitative, measurable) anchors on desired outcomes: what the customer is trying to optimize that no current solution satisfies. The primary tool is a needs-based survey followed by cluster analysis. The output is a quantified opportunity score for each unmet need, ranking which outcomes to target next.

Both schools use the "When , I want to , so I can ___" sentence format, but for different purposes. Christensen practitioners write it as a discovery output from interviews. Ulwick practitioners write it as the anchor before running a full measurement study.

Which to use:

The Jobs to Be Done Template

Each section below maps to a tab in the free Google Sheet. Want to skip the copy-paste? Google Sheets version is ready to fill in.

Section 1: Job Statement

A job statement is ready to use when it passes all three of thrv's validation criteria:

• [ ] Solution-agnostic (describes a goal, not a product feature: "understand status" not "see a dashboard")
• [ ] Measurable in speed or accuracy ("get status without a meeting" can be timed; "feel more confident" cannot)
• [ ] Stable over time (the job persists across technology generations; the product hired to do it changes)

Four common job-statement mistakes: writing the solution as the job, making the job too broad, skipping desired outcomes entirely, and segmenting by demographics instead of struggling moment.

Section 2: Job Types

Customers hire products primarily for functional jobs. Emotional and social jobs shape which product they hire and build the switching inertia that keeps them from leaving. Mapping all three explains why technically superior products lose to incumbents.

Section 3: Four Forces Map

The Four Forces determine whether customers switch, not just why they want to. A product can win on pull and still lose to habit.

As Bob Moesta explains in "ultimate guide to JTBD" (Lenny's Podcast): "The biggest misconception around jobs to be done is this notion that it's pain and gain as opposed to context and outcome. When you hear somebody's story and it seems irrational… the context makes the irrational rational."

Section 4: Universal Job Map (ODI School)

Ulwick's Job Map breaks any functional job into eight universal steps. Map each step, then survey customers on desired outcomes for each to quantify which step is most underserved.

For each step, list every desired outcome a customer might want to optimize. These become your survey items in an ODI study. Strategyn's original research estimates that 95% of product teams don't agree on what a customer need is; the Job Map forces that disagreement into the open before sprints start.

Section 5: Switch Interview Guide

Pre-interview setup:

• Recruit 10–12 recent buyers (purchased within the last 90 days)
• Prioritize people who switched from a prior solution
• Record with permission; transcribe verbatim

Six-phase interview flow (60 minutes):

Bob Moesta's protocol from Lenny's Podcast: "Go find 10 people who recently bought your product… go talk to them not about the product but about why they bought the product. What was going on, what were they hoping for, what were they worried about, what did they have to give up, how did they convince somebody else. Just listen to the story."

Synthesis matrix: Log each interview below. A pattern converges at 8 interviews; if new themes still emerge at interview 15, the customer segment is too broad.

AI-assisted synthesis: After running interviews, paste a transcript into Claude or ChatGPT with this prompt to categorize quotes into the Four Forces automatically:

Act as an expert PM specializing in JTBD research. Analyze this transcript. Identify and categorize quotes into the Four Forces: Pushes, Pulls, Anxieties, Habits. Present as a four-quadrant markdown table with verbatim quotes.

This prompt (from Aakash G.'s PM guide) cuts manual synthesis from hours to minutes. No published SERP competitor includes this step; it's the most practical way to use AI on a JTBD project without compromising the qualitative data.

Section 6: Opportunity Scoring

Ulwick's Opportunity Score formula quantifies which outcomes to target first:

Opportunity Score = Importance + max(Importance − Satisfaction, 0)

Survey each desired outcome on two 10-point scales. Scores above 10 are underserved (high importance, low satisfaction); scores below 5 are over-served. Target the 10+ cluster first.

The Opportunity Score gives product and engineering a shared prioritization language: Strategyn's work with Microsoft used exactly this method to produce a 100% year-over-year revenue increase for the Software Assurance product line.

Example: JTBD Template in Action

Scenario: A B2B SaaS team building async project management software for engineering teams at 50–200 person companies.

Job Statement (Christensen school):

When preparing for a weekly sprint kickoff, I want to understand which tasks are blocked and by whom, so I can resolve dependencies before the sprint starts. Confirmed at 11 switch interviews; pattern stable from interview 8.

Four Forces:

Top Opportunity Scores (SaaS sprint tool):

Recommended build sequence: The blocker-identification feature scores 14, so build that first. Status-without-meetings (13) is the pull customers already articulate during interviews. Dependency updates (9) reduce execution friction without a separate product investment.

Skip "team pulse" features: those target the social job, not the functional one that drives switching.

Industry note for SaaS: The job statement format stays identical across sectors. In e-commerce, the core job is minimizing time to identify inventory discrepancies before a fulfillment window. In B2B services, it's minimizing effort to produce a client-ready deliverable under a deadline.

How to Use This Template

1. Start with 3–5 switch interviews before filling in anything else. Even an informal run through the six-phase protocol unlocks more honest roadmap conversations than a brainstorm session.
2. Map the Four Forces for each interview. Log findings in the synthesis matrix. Patterns across 8+ responses reveal actual push/pull dynamics, not team assumptions.
3. Write the job statement once the pattern converges. Run it through the three-criteria checklist: solution-agnostic, measurable, stable.
4. Run the Job Map to find which of the eight steps your product competes in, and where competitors leave gaps unaddressed.
5. Score outcomes before any major investment. A 50-person survey takes 2 hours to run and prevents building against over-served outcomes.

Which school to lead with:

Use Christensen/Moesta at the discovery stage when you don't know what job you're solving. Use Ulwick/ODI at the innovation stage when you know the job and want to rank which outcomes to target next. Starting with switch interviews is the right default; move to opportunity scoring once you have a job statement confirmed by 8+ interviews.

Recommended Tools