Jobs To Be Done

Jobs to Be Done Framework

Framework for discovering innovation based on a fundamental truth: customers don't buy products -- they "hire" them to do a specific job in their lives.

Core Principle

Job to Be Done = the progress a customer wants to make in specific circumstances.

Key elements of the definition:

• Progress (not goal, not solution) -- the customer wants to move from the current state to a better one
• Circumstances -- context determines the job, not customer attributes (demographics are useless)
• Hiring/Firing -- the customer actively chooses a product for the "job"

Scoring

Goal: 10/10. Rate product strategy or positioning 0-10 against the principles below. Always state the current score and the specific improvements needed to reach 10/10.

Three Dimensions of Every Job

Every job has three inseparable dimensions -- omitting any means failure:

Framework

1. The Job Statement

Core concept: A job statement captures the progress a customer seeks in a specific circumstance, in a structured format separating context, desired progress, and expected outcome.

Why it works: Forcing teams to articulate the job in the customer's language and circumstances prevents solution-first thinking and grounds innovation in real human progress.

Key insights:

• Format: "When [circumstances], I want to [progress], so I can [outcome]"
• Circumstances matter more than demographics -- the same person has different jobs in different situations
• A well-written job statement never mentions your product or any specific solution
• Jobs are stable over time; solutions change but the underlying job persists

Product applications:

Copy patterns:

• "When you're [circumstance], you need [progress] -- that's exactly what [product] does"
• Lead with the situation the customer recognizes, not the product category
• Mirror the emotional and social dimensions alongside the functional one

Ethical boundary: Never fabricate or exaggerate circumstances to manufacture urgency -- the job must reflect genuine progress, not artificial anxiety.

See: references/innovation-process.md for job hunting methodology, the job atlas, and statement templates.

2. Forces of Progress (Push, Pull, Anxiety, Habit)

Core concept: The decision to "hire" a new product results from four forces: Push (frustration with the current situation), Pull (attraction of the new solution), Anxiety (fear of the new), and Habit (comfort with the current behavior). Change happens only when Push + Pull > Habit + Anxiety.

Why it works: Most innovation efforts only increase Pull while ignoring the anti-change forces -- which is why great products still fail to gain adoption.

Key insights:

• Push: "this annoys me"; Pull: "I want this"; Habit: "I've always done it this way"; Anxiety: "what if it doesn't work?"
• Reducing anxiety and habit is often more effective than increasing push and pull
• Passive seekers (vaguely aware of a problem) are easier to influence than active seekers who already have criteria

Product applications:

Copy patterns:

• Address anxiety directly: "No lock-in, cancel anytime, your data is always yours"
• Name the push: "Tired of [frustration]? There's a better way"
• Reduce habit friction: "Switch in 5 minutes -- we import everything automatically"

Ethical boundary: Reducing real anxiety is ethical; manufacturing fear or exaggerated pain to drive sales is manipulation.

See: references/competitive-strategy.md for forces analysis, non-obvious competition, and jobs-based positioning.

3. The Big Hire & Little Hire

Core concept: Two distinct decision moments: the Big Hire (purchase/signup, happens once) and the Little Hire (decision to use in the moment, happens repeatedly). Winning the Big Hire does not guarantee the Little Hire.

Why it works: Many products win the sale but lose the customer because they optimize only the purchase decision -- understanding both moments reveals where retention problems truly originate.

Key insights:

• Big Hire is driven by marketing, onboarding, and first impressions; Little Hire by product quality, UX, and ongoing value
• Big Hire anxiety is purchase risk; Little Hire anxiety is effort and learning curves
• Retention problems are almost always Little Hire failures -- purchased but never used

Product applications:

Copy patterns:

• Big Hire copy sells the promise: "Transform how you [job]"
• Little Hire copy sells ease: "One click and you're done"
• Re-engagement copy addresses the failure: "We've made [specific friction] easier"

Ethical boundary: Never use dark patterns that win the Big Hire (hidden fees, misleading trials) while failing the Little Hire -- both decisions must deliver genuine progress.

See: references/case-studies.md for detailed analyses (SNHU, American Girl, Intuit).

4. Competitive Landscape (Non-Obvious Competition)

Core concept: True competition is everything a customer can "hire" for the same job, often from completely different categories. Competitors are defined by the job, not by industry classification.

Why it works: Category-based analysis creates blind spots: a milkshake competes with bananas, bagels, and podcasts; Netflix competes with TikTok, sleep, and family conversation. Mapping the full landscape around the job reveals threats and opportunities traditional analysis misses.

Key insights:

• Non-consumption (doing nothing) is often the biggest competitor
• Workarounds and compensating behaviors reveal unserved jobs -- people hack, combine, and improvise
• Integrate where performance is "not good enough" for the job; modularize where it's "good enough"
• The best positioning answers "what job are we the best hire for?", not "how do we compare to similar products?"

Product applications:

Copy patterns:

• "Stop using [workaround] for [job] -- there's a purpose-built solution"
• "You wouldn't hire a [bad fit] to [job] -- so why are you using [current hack]?"
• Position around the job outcome, not feature comparison charts

Ethical boundary: Honest competitive framing based on the job is powerful; misrepresenting alternatives is deceptive.

5. Customer Discovery Interviews

Core concept: Don't ask customers "what do you need" -- they don't know. Instead, reconstruct the purchase timeline (first thought, search, purchase, usage) to uncover the real job.

Why it works: Customers rationalize decisions after the fact and can't articulate latent needs; walking backward through concrete events reveals the true circumstances, forces, and tradeoffs that drove behavior.

Key insights:

• First thought: "When did you first look for a solution? What was happening in your life? What frustrated you?"
• Search: "What alternatives did you consider? What eliminated options? Who did you talk to?"
• Purchase: "Where were you? What ultimately convinced you? What were you afraid of?"
• Usage: "Is it doing what you expected? What surprised you? What's still missing?"
• Signals of undiscovered jobs: workarounds, non-consumption, compensating behaviors, negative emotions toward current solutions

Product applications:

Copy patterns:

• Use exact customer language from interviews in marketing copy
• "We heard you say [verbatim quote] -- so we built [feature]"
• Frame benefits in the circumstances and emotions customers actually described

Ethical boundary: Never lead interview subjects toward predetermined conclusions -- the goal is discovery, not confirmation.

6. Designing for the Job

Core concept: Build the entire experience -- features, metrics, organization -- around helping the customer accomplish their job, not around internal capabilities or feature parity.

Why it works: When every decision answers "will this help the customer better accomplish their job?", teams avoid feature bloat and build coherent products; if you can't answer it, you don't understand the job yet.

Key insights:

• Replace customer satisfaction metrics with "did the job get done?"
• Replace NPS with "reasons for hiring and firing"; replace feature usage with "progress on the job"
• Organize teams and processes around jobs, not internal capabilities or product components

Product applications:

Copy patterns:

• "Built for [the job], not for [the category]"
• "Everything you need to [job] -- nothing you don't"
• Emphasize outcome and progress, not features and specifications

Ethical boundary: Never design addictive patterns that serve engagement metrics over genuine progress -- the customer's progress is the true north, not your retention numbers.

See: references/organizational-change.md for the feature-factory trap, executive buy-in, and change management.

Common Mistakes

Quick Diagnostic

See: references/diagnostics.md for the full diagnostic checklist.

Reference Files

• innovation-process.md: Job hunting methodology, job atlas, prototype testing, job statements
• competitive-strategy.md: Non-obvious competition, jobs-based positioning, pricing strategy
• organizational-change.md: Overcoming objections, feature-factory trap, executive buy-in, change management
• diagnostics.md: Diagnostic checklist for evaluating products through the jobs lens
• case-studies.md: Detailed analyses of SNHU, American Girl, Intuit, and more

Further Reading

For the complete methodology, case studies, and deeper insights:

• *"Competing Against Luck: The Story of Innovation and Customer Choice"* by Clayton M. Christensen, Taddy Hall, Karen Dillon, and David S. Duncan

About the Author

Clayton M. Christensen (1952-2020) was the Kim B. Clark Professor of Business Administration at Harvard Business School, best known for the theory of disruptive innovation introduced in The Innovator's Dilemma (1997). He developed Jobs to Be Done as a practical innovation methodology in Competing Against Luck (2016) and was repeatedly ranked the world's #1 management thinker by Thinkers50.

JTBD Case Studies

1. McDonald's Milkshake

Situation

McDonald's wanted to increase milkshake sales. Traditional research (focus groups, surveys) gave conflicting results: "less sweet," "more chocolate," "more fruit chunks."

Job Discovery

Observation revealed that 40% of milkshakes were bought in the morning, by solo drivers, to-go.

Morning job: "When I'm driving alone to work and have a boring hour of commute, I want something to keep my hands busy, satisfy my hunger until lunch, and give me a small pleasure."

Afternoon job (different!): "When picking up my child from school, I want to be a good parent and give them a small reward, but without feeling guilty."

Competition Through Job Lens

• Morning job: banana, bagel, coffee, boredom, podcast
• Afternoon job: ice cream, candy, toy, parental attention

Solution

• Morning milkshake: thicker (takes longer to drink), with chunks (more interesting), larger, easier to buy (drive-through kiosk)
• Afternoon milkshake: smaller (sense of moderation), faster to drink (child doesn't get bored)

Lesson

The same product can serve completely different jobs. Improving the "product" without understanding the job leads nowhere.

---

2. Southern New Hampshire University (SNHU)

Situation

SNHU was a small college with 2,500 students. They launched an online program that exploded to 100,000+ students.

Job Discovery

Typical online student: 30+ years old, working, often with family, interrupted education years ago.

Job: "When I realize I'm stuck in my career and need a degree to advance, but I have a job, family, and little time, I want to get a degree without turning my life upside down."

Job Dimensions

• Functional: Get a degree from an accredited institution
• Emotional: Feel that I'm growing, prove to myself that I can do it
• Social: Show my family I'm setting a good example; not look like a "student" at work

Competition

• Doing nothing (most common!)
• Other online universities
• Industry certifications
• Changing jobs without a degree

Breakthrough Changes

1. Onboarding: Calling applicants within minutes (not days) - reduces "can I do this" anxiety 2. Personal advisor: One point of contact throughout studies - like GPS, not bureaucracy 3. Credit transfer: Liberal policy for recognizing previous courses - faster to the goal 4. Communication: Simplicity, no academic jargon - "we work for you, not the other way around"

Lesson

SNHU doesn't compete with Harvard - it competes with "doing nothing." The job isn't "education" but "unfreezing a stuck life."

---

3. American Girl

Situation

Premium doll company ($100+) at a time when competitors offered dolls for $20.

Job

Mothers/grandmothers: "When I want to have a meaningful moment with my daughter/granddaughter and pass on values, I want an experience that connects us and teaches, not just a toy."

Girls (8-12): "When I'm at an age where I don't want to be a 'little girl' anymore but I'm not yet a teenager, I want something that takes me seriously and says my interests matter."

Dimensions

• Functional: Playing with doll, reading stories
• Emotional: Feeling "grown up," understood
• Social: Ritual with mother/grandmother, belonging to American Girl "club"

Experience Integration

• Doll + book with story (context, values)
• Stores with hair salons for dolls
• Restaurants where girls eat with their dolls
• Magazine, events, community

Competition

• Not other dolls (!)
• Other "moments with daughter": trips, movies, shopping
• Other ways to pass on values: conversations, books
• Non-consumption: "I'll just buy something at the store"

Lesson

American Girl sells an experience-ritual, not a doll. That's why $100+ price makes sense - it's not a "toy" but a "moment with daughter."

---

4. Intuit QuickBooks

Situation

QuickBooks dominated among small businesses. Attempts to enter the "even smaller" segment (freelancers, single-person) by simplifying the product didn't work.

Job Discovery

Freelancers have a different job than small businesses.

Small business job: "Manage company finances professionally and in compliance with regulations"

Freelancer job: "When I send an invoice to a client, I want to know I'll get paid, and I don't want to feel like an amateur"

Breakthrough: Mint.com → QuickBooks Self-Employed

Instead of "stripped-down QuickBooks" - a completely new product:

• Automatic expense tracking (not manual bookkeeping)
• Bank account integration
• Simple split: business vs personal
• Real-time tax estimation

Lesson

"Simpler version of the same thing" isn't innovation. Different job requires different product, not a simplified old one.

---

5. Airbnb vs Hotels

Business traveler job

"When I travel for work, I want efficiency, predictability, and ability to work" → Hotel wins (standardization, wifi, desk, room service)

Family traveler job

"When we go somewhere with kids for a week, we want to feel at home, have space, cook, be together" → Airbnb wins (kitchen, rooms, locality, group pricing)

"Experience" job

"When I want to really get to know a place and feel the locality, not be a tourist" → Airbnb wins (local hosts, authentic locations)

Lesson

Airbnb doesn't compete with "hotels" - it competes for specific jobs. For some jobs, a hotel is a better "employee."

---

Patterns from Case Studies

1. Same product, different jobs

Morning vs afternoon milkshake - require different solutions even though it's "the same product."

2. Competition from unexpected places

• SNHU: competitor is "doing nothing"
• American Girl: competitor is "other activities with daughter"
• Milkshake: competitor is banana and boredom

3. Integration for poorly understood jobs

American Girl and SNHU heavily integrated the experience because the job was poorly served by existing solutions.

4. Emotions and social aspects often more important than functionality

• SNHU: "prove to myself I can do it"
• American Girl: "moment with daughter"
• Milkshake: "small pleasure to start the day"

5. Anti-change forces are powerful

SNHU won mainly by reducing anxiety (quick callback, personal advisor) - not by "better education."

JTBD Competitive Strategy

Analyzing competition through the jobs lens and building differentiated positioning.

Rethinking Competition

The Traditional View (Wrong)

"Our competitors are companies that sell similar products in our category."

The JTBD View (Right)

"Our competitors are anything a customer might hire to get their job done."

This fundamental shift reveals:

• Non-obvious competitors you're losing to
• Opportunities in adjacent spaces
• Why customers choose seemingly inferior solutions

---

Non-Obvious Competition

Finding Hidden Competitors

Ask: "What else do customers hire for this job?"

The Milkshake Discovery

The famous milkshake study revealed:

• Assumed competitors: Other fast food beverages, breakfast items
• Actual competitors: Bananas, bagels, donuts, boredom itself

The job wasn't "consume breakfast"—it was "make my commute tolerable and keep me full until lunch."

Mapping Your Competition

Step 1: Define the job (not the product category)

Step 2: List everything customers currently hire:

• Direct competitors (same category)
• Indirect competitors (different category, same job)
• Non-consumption (doing nothing)
• DIY/workarounds (cobbling solutions together)

Step 3: Understand why each gets hired:

• What's the circumstance?
• What dimension does it serve best? (Functional/Emotional/Social)
• What trade-offs do customers accept?

Example: Project Management Software

Job: "Keep my team aligned and projects on track so nothing falls through cracks"

---

Jobs-Based Positioning

The Positioning Formula

For [customers in these circumstances]
who [have this job to do]
our [product/service]
is the [frame of reference]
that [does the job better because]
unlike [alternative]
we [key differentiator].

Example Positioning Statements

Traditional (weak): "Monday.com is a work operating system that helps teams manage projects and workflows."

Jobs-based (strong): "For growing teams who feel like projects keep slipping through cracks, Monday.com is the work management platform that gives everyone visibility into what's happening without adding overhead, unlike spreadsheets that get outdated or meetings that waste time."

More examples:

Slack: "For remote teams who feel disconnected and out of the loop, Slack is the communication hub that makes you feel like you're in the same room, unlike email that buries important messages or video calls that require scheduling."

Duolingo: "For busy people who want to learn a language but have always given up, Duolingo is the learning app that fits language practice into small daily moments, unlike courses that require big time commitments or tutors that require scheduling and money."

---

Competing Against Non-Consumption

Why Non-Consumption Matters

The biggest competitor is often "doing nothing." People who:

• Haven't realized they have the problem
• Don't think solutions exist
• Think solutions are too expensive/complicated
• Tried before and gave up

Non-Consumption Opportunities

Winning Non-Consumers

To convert non-consumers:

1. Lower the barrier to entry

• Reduce price
• Simplify the experience
• Remove expertise requirements

2. Reduce anxiety

• Eliminate commitment
• Provide strong guarantees
• Show "people like me" success stories

3. Reframe the job

• Make it about a job they already care about
• Connect to existing behaviors
• Show quick wins possible

SNHU Example:

• Traditional barrier: Campus attendance required
• SNHU reframe: "Get a degree without putting life on hold"
• Job focus: Career advancement, not "being a student"

---

Price Strategy Through JTBD

Price Based on Job Value, Not Cost

Traditional pricing: Cost + margin = price JTBD pricing: Job value to customer = pricing ceiling

Questions to determine job value:

• What does getting this job done save/earn the customer?
• What are they currently paying to get it done (including time)?
• How important is this job relative to other spending?
• What's the cost of the job NOT getting done?

Premium Pricing Justification

Charge more when:

• You serve job dimensions competitors ignore (especially emotional/social)
• You reduce anxiety in high-stakes situations
• You save significant time for time-strapped customers
• You eliminate effort for effort-averse customers

Price Relative to Alternatives

Frame your price against the cost of alternatives, including their hidden costs (time, frustration, opportunity cost).

---

Differentiation Strategy

Differentiate on the Underserved Dimension

Most competitors fight on functional dimensions. Differentiate on:

Emotional dimension:

• How customers feel while using the product
• Confidence, peace of mind, delight
• Reduced anxiety, eliminated frustration

Social dimension:

• How customers appear to others
• Status, belonging, identity
• What others think of their choice

Differentiation Examples

The Differentiation Test

Ask current customers:

• "Why did you choose us over [alternative]?"
• "What would you tell a friend about why they should use us?"
• "What would you miss most if you couldn't use us anymore?"

If answers are only functional, you have a differentiation problem.

---

Competitive Response Framework

When a Competitor Launches a Feature

Don't automatically copy. Instead ask: 1. What job does this feature serve? 2. Is that job a priority for OUR customers? 3. Do we serve that job differently/better already? 4. Should we compete or differentiate?

When Losing Deals to Competitors

Interview lost customers: 1. "What job were you trying to get done?" 2. "What did [competitor] do better for that job?" 3. "Was there anything we did better that wasn't enough?" 4. "What almost made you choose us?"

Pattern recognition: If you consistently lose on price, you're not communicating job value. If you consistently lose on features, you might be targeting the wrong customers.

When Entering an Established Market

Don't compete head-to-head. Instead: 1. Find underserved customer segments (different circumstances) 2. Find underserved job dimensions (emotional/social) 3. Find simpler jobs that incumbents over-serve 4. Find more demanding jobs that incumbents can't serve

---

Strategic Decision Framework

Should We Build This Feature?

Should We Enter This Market?

Should We Worry About This Competitor?

Product Diagnostics Through JTBD Lens

Checklist: Do You Know Your Product's Job?

Level 1: Basic Understanding

• [ ] You can describe the job in one sentence without using the product name
• [ ] You know the circumstances in which the job arises
• [ ] You know what customer did BEFORE using your product
• [ ] You understand the functional, emotional, AND social dimensions

Level 2: Deep Understanding

• [ ] You know what you really compete with (not just "direct competitors")
• [ ] You understand push/pull and habit/anxiety forces for your customer
• [ ] You can distinguish Big Hire from Little Hire
• [ ] You know why customers "fire" your product

Level 3: Organizational Implementation

• [ ] Product decisions are filtered through the job lens
• [ ] Metrics measure job completion, not just usage
• [ ] Roadmap is oriented toward better job execution
• [ ] Team can articulate the customer's job

Red Flags - Signs You Don't Know the Job

1. You describe product through features - "it's a tool for X with Y feature" 2. Competition is only "similar products" - you don't see non-obvious competitors 3. You segment by demographics - "target is men 25-35" 4. High acquisition, low retention - you win Big Hire, lose Little Hire 5. Customers use product "wrong" - they create workarounds

Diagnostic Framework

Why Aren't Customers Buying?

"Firing" Interview (Churn Interview)

Questions for customers who left:

1. "What did you do before us? Why did you come to us?" 2. "What changed that made you start looking for alternatives?" 3. "What ultimately convinced you to leave?" 4. "What do you do now instead of us? Does it do the job better?" 5. "If we could change one thing, what would it be?"

"Hiring" Interview (New Customer Interview)

Questions for new customers (within 2 weeks):

1. "When did you first think about looking for a solution?" 2. "What was the trigger - what was happening then?" 3. "What alternatives did you look for? What disqualified them?" 4. "What ultimately convinced you to choose us?" 5. "What were you afraid of before buying?" 6. "Is the product doing what you expected?"

JTBD Metrics

Instead of Traditional Metrics:

Job Completion Rate

Define what "job done" means and measure:

• % of sessions where job was completed
• Time to first success (Time to Value)
• Repeatability of "hiring" (hire frequency)

---

Post-Launch Iteration

Continuous Job Discovery

After launch, keep learning:

Usage data signals:

• Features used ≠ Features valued (may use out of necessity)
• Time spent ≠ Job done (frustration can increase time)
• Feature requests often describe solutions, not jobs

Ongoing research:

• Interview new customers within 2 weeks of purchase
• Interview churned customers within 1 week of leaving
• Observe actual usage (session recordings, support tickets)
• Track "aha moments" that predict retention

Iteration Framework

---

Churn Analysis Through JTBD Lens

Why "Firing" Happens

Customers fire products when: 1. Job changed - Circumstances evolved (company grew, life changed) 2. Better "employee" appeared - Competitor does job better 3. Job wasn't being done - Product never delivered on promise 4. Friction accumulated - Too hard to use, not worth the effort 5. Priorities shifted - Other jobs became more important

Churn Interview Framework

Timing: Within 1 week of cancellation (memory fresh)

Questions:

Churn Patterns to Watch

Acting on Churn Insights

If job changed: Consider segments, expansion products, or accepting churn as natural If competitor wins: Investigate which dimension they're serving better If job wasn't done: Product or onboarding needs improvement If friction accumulated: UX improvements, training, simplification If priorities shifted: May be targeting wrong customer profile

JTBD Innovation Process

Systematic methodology for discovering jobs and translating them into successful innovations.

Table of Contents

1. Job Hunting: Finding Undiscovered Jobs 2. Passive vs. Active Job Seeking 3. The Job Atlas 4. Prototype Testing Through the JTBD Lens 5. Job Statements: The Right Level of Abstraction 6. From Job to Innovation 7. Common Innovation Traps 8. Job Discovery Interview Guide

---

Job Hunting: Finding Undiscovered Jobs

Where Jobs Hide

Jobs worth pursuing are often invisible because:

• Customers don't articulate them (they've adapted)
• Existing categories obscure them (you see products, not jobs)
• Data shows behavior, not motivation

Five Sources of Job Discovery

1. Workarounds and Compensating Behaviors

Signal: People combine products, modify them, or create DIY solutions.

What to look for:

• Products used in unintended ways
• Multiple products combined to complete one job
• Time-consuming manual processes
• Spreadsheets and duct-tape solutions

Interview questions:

• "Walk me through how you handle [situation] today"
• "What's frustrating about your current approach?"
• "What have you tried that didn't work?"
• "If you could wave a magic wand, what would change?"

Example: Milkshake study discovered people "hiring" milkshakes for morning commutes—a workaround for boredom and hunger that bananas and bagels couldn't solve.

2. Non-Consumption

Signal: People who should be using a solution but aren't.

Why people don't consume:

What to look for:

• Markets that seem "maxed out" but have huge populations not participating
• People who have "given up" on a category
• Simpler alternatives that attract non-users

Interview approach:

• "Have you ever considered [category]? Why or why not?"
• "What would make you try something in this area?"
• "What have you heard about [category] that put you off?"

Example: Southern New Hampshire University found millions of adults who wanted degrees but couldn't attend traditional college—a massive non-consumption opportunity.

3. Negative Emotions

Signal: Frustration, anxiety, fear, or embarrassment around a situation.

Emotions that signal jobs:

• Frustration → Job not being done well
• Anxiety → Risk of job failure
• Embarrassment → Social dimension unmet
• Overwhelm → Job too complex

Interview questions:

• "What's the hardest part about [situation]?"
• "When do you feel frustrated with [current solution]?"
• "Is there anything you avoid or dread?"
• "What keeps you up at night about [area]?"

Example: SNHU discovered adult students' real struggle wasn't academics—it was fear of failure and embarrassment about going back to school.

4. Unusual Uses and Surprising Customers

Signal: Customers using your product in unexpected ways, or unexpected customer segments.

What to investigate:

• Customer segments you didn't target who are buying
• Features used differently than intended
• Complaints that reveal hidden jobs
• Support tickets that reveal actual use cases

Questions to ask:

• "What made you choose us over [expected alternative]?"
• "What were you using before? What was wrong with it?"
• "What job are you really hiring us to do?"

Example: Arm & Hammer discovered baking soda was being "hired" for odor absorption, carpet cleaning, and toothpaste—jobs far beyond baking.

5. Moments of Struggle

Signal: Specific circumstances where existing solutions fail.

The Timeline Interview:

First thought → Passive looking → Active search → Decision → Purchase → Experience

Questions for each stage:

---

Passive vs. Active Job Seeking

Passive Seeking

Customer is vaguely aware of a problem but not actively looking for solutions.

Characteristics:

• Haven't allocated budget
• Haven't carved out time
• Open to being educated
• Easier to influence (no preconceptions)

Marketing implications:

• Content marketing to raise awareness
• Focus on problem articulation
• Lower competition for attention

Active Seeking

Customer is actively shopping for a solution.

Characteristics:

• Researching options
• Set budget (often)
• Clear criteria
• Comparing alternatives

Marketing implications:

• More competitive
• Focus on differentiation
• Demonstrate superior job completion

Key insight: The best customers are often passive seekers whose jobs you've awakened. They're not shopping—they're discovering they have a need.

---

The Job Atlas

A comprehensive map of a customer's job ecosystem.

Elements of the Atlas

1. Main Job The primary progress the customer wants to make.

2. Related Jobs Adjacent jobs that cluster with the main job.

Example (financial planning):

• Main job: Retire comfortably
• Related: Protect family if I die, fund kids' education, manage taxes

3. Emotional Jobs How they want to feel during and after.

4. Social Jobs How they want to be perceived by others.

5. Consumption Chain Jobs Jobs at each stage of using your product:

Building Your Atlas

1. Interview 10-20 customers using timeline methodology 2. Map all jobs mentioned across interviews 3. Cluster related jobs 4. Identify which jobs are served/underserved 5. Prioritize based on importance and satisfaction gap

---

Prototype Testing Through the JTBD Lens

Testing for Job Completion, Not Features

Wrong question: "Do you like this feature?" Right question: "Does this help you accomplish [job]?"

Prototype Testing Framework

1. Simulate the circumstances

Don't test in a vacuum. Recreate the context where the job arises.

• Wrong: "Here's a new budgeting app. What do you think?"
• Right: "Imagine it's the end of the month and you're worried about overspending. Here's what you'd see..."

2. Measure job completion

3. Test the full experience

Not just the core product—test the entire "hiring" and "using" experience:

• Finding and understanding the product
• Purchasing/signing up
• First use
• Ongoing use
• Moments of difficulty

4. Compare to current "hires"

"Would you fire your current solution for this?"

---

Job Statements: The Right Level of Abstraction

Too Narrow

"I want to create a to-do list"

Problem: Focuses on solution, not job. Misses why they want a list.

Too Broad

"I want to feel productive"

Problem: Too vague to build for. Hundreds of solutions could apply.

Just Right

"When I'm overwhelmed with tasks and don't know where to start, I want to see my priorities clearly so I can focus on what matters and feel in control of my day."

The Litmus Test

A good job statement should: 1. Be solution-agnostic (no product names) 2. Include circumstances 3. Include functional, emotional, and social dimensions 4. Be specific enough to build for 5. Be abstract enough to allow innovation

---

From Job to Innovation

Step 1: Define the Job Clearly

Use the job statement format:

When _____________ [circumstances]
I want to _____________ [progress]
So I can _____________ [outcome]

Step 2: Map Current "Employees"

What do people currently hire to do this job?

• Direct competitors (same category)
• Indirect competitors (different category, same job)
• Non-consumption (doing nothing)
• DIY/workarounds

Step 3: Identify Performance Gaps

Where do current solutions fall short?

Step 4: Design for the Gap

Build experiences that address unmet dimensions.

Questions:

• How can we do the functional job faster/better/cheaper?
• How can we make the emotional experience better?
• How can we help with the social dimension?

Step 5: Test Against the Job

Return to customers:

• "Does this help you make the progress you wanted?"
• "Would you fire your current solution for this?"
• "What's still missing?"

---

Common Innovation Traps

The Feature Factory Trap

Symptom: Shipping features without connecting them to jobs.

Fix: Every feature must answer: "What job does this help complete?"

The Correlation Trap

Symptom: "Our best customers are women 25-34, so let's target them."

Problem: Demographics correlate with jobs but don't explain them.

Fix: Find the job that women 25-34 happen to have, then target anyone with that job.

The Technology-First Trap

Symptom: "We built this cool AI—let's find a use case."

Fix: Start with jobs, then ask if your technology serves them better.

The Competitor-Copying Trap

Symptom: "Competitor added X, so we should too."

Fix: Ask what job X serves. If that's not your customers' priority job, don't copy.

---

Job Discovery Interview Guide

Preparation

• Recruit recent purchasers (within 1-2 weeks)
• 45-60 minutes per interview
• Record with permission
• Prepare timeline visualization

Opening (5 min)

"I'd love to understand how you came to use [product]. Not to sell you anything—just to learn about your experience."

First Thought (10 min)

• "When did you first realize you might need something like this?"
• "What was going on in your life at that time?"
• "What triggered that thought?"

Passive Looking (10 min)

• "What did you do after that first thought?"
• "What alternatives did you consider?"
• "Why didn't you act on it right away?"

Active Search (10 min)

• "What made you start seriously looking?"
• "What changed?"
• "What were you comparing?"
• "What criteria mattered most?"

Purchase Moment (10 min)

• "Walk me through the moment you decided to buy."
• "Where were you? Who were you with?"
• "What finally convinced you?"
• "What almost stopped you?"

Experience (10 min)

• "Is it doing what you expected?"
• "What surprised you?"
• "What's still frustrating?"
• "Would you hire it again?"

Closing

• "If you could change one thing, what would it be?"
• "What would make this perfect for your situation?"

Organizational Change for JTBD

Overcoming resistance, building jobs-oriented organizations, and avoiding the feature-factory trap.

Table of Contents

1. Common Objections to JTBD 2. The Feature-Factory Trap 3. Getting Executive Buy-In 4. Building a Jobs-Oriented Organization 5. Change Management Playbook 6. Handling Resistance 7. Measuring Adoption

---

Common Objections to JTBD

"We already know our customers"

The objection: "We've been in this business for years. We know what customers want."

The reality: You know what customers say they want and what they do. You may not know why they do it.

Counter:

• "Great—let's validate that knowledge. If we're right, research will confirm it quickly."
• "When was the last time we talked to customers about their struggles, not our product?"
• "Do we know why customers choose competitors, or why non-customers don't buy?"

"Jobs theory is too abstract"

The objection: "This sounds like academic theory. We need practical action."

The reality: JTBD is extremely practical—it tells you what to build and how to market.

Counter:

• "Let me show you a job statement for our product. Does this match how we talk about it?"
• "Here's how [successful company] used JTBD to [specific outcome]."
• "What if we ran one customer interview using this method and compared insights?"

"We don't have time for research"

The objection: "We need to ship features, not conduct research."

The reality: Shipping the wrong features wastes far more time than research.

Counter:

• "How much time did we spend building [feature that didn't work]?"
• "Five customer interviews take ~10 hours. What's the cost of a failed launch?"
• "We can learn the job from 10 interviews. We can't learn it from guessing."

"Our data tells us what to build"

The objection: "We have analytics. We know what users do."

The reality: Data shows what users do, not why. Jobs research explains the why.

Counter:

• "Data shows users drop off at step 3. Do we know why?"
• "Our most-used feature might not be our most-valued feature. Data can't tell us."
• "Correlation ≠ causation. We see patterns but don't understand motivations."

"Our roadmap is set"

The objection: "Leadership has already decided what we're building."

The reality: JTBD doesn't change what you build—it changes how you build and position it.

Counter:

• "Let's use jobs thinking to make sure we build [planned feature] the right way."
• "Understanding the job might reveal quick wins within current plans."
• "We can influence future roadmaps even if this quarter is set."

---

The Feature-Factory Trap

What It Looks Like

A feature factory is an organization that:

• Measures success by features shipped, not outcomes achieved
• Builds what stakeholders request without validating need
• Competes by feature matching competitors
• Has roadmaps full of features without hypotheses
• Celebrates launches, not impacts

Why It Happens

The Costs

• Wasted development: Features nobody uses
• Product bloat: Complexity without value
• Technical debt: Maintaining unused code
• Team demoralization: Shipping without impact
• Customer confusion: Product does everything, nothing well

Breaking Free

Step 1: Change the conversation

Step 2: Change the metrics

Step 3: Change the process

Before greenlighting any feature: 1. What job does this serve? 2. Who has this job? How many? 3. How well is the job being served today? 4. How will we measure if this helps?

---

Getting Executive Buy-In

Speaking Their Language

Executives care about:

• Revenue growth
• Market share
• Competitive advantage
• Customer acquisition/retention
• Resource efficiency

Frame JTBD in these terms:

Making the Business Case

Case 1: Failed features "Last year we shipped 12 major features. 3 moved metrics. JTBD research could have identified which 3 before we built all 12."

Case 2: Churn analysis "Customers leave because we're not doing their job. Exit interviews reveal jobs we didn't know about. What if we knew before they left?"

Case 3: Competitive loss "We lose deals to [competitor]. Is it features or job understanding? Interviews with lost customers could tell us."

Case 4: Market expansion "Our market seems saturated. JTBD reveals non-consumers with the same jobs. That's greenfield opportunity."

The Pilot Proposal

Start small to prove value: 1. One focused research project (10 interviews, 2 weeks) 2. One product decision influenced by findings 3. Measure the outcome 4. Report back with concrete results

---

Building a Jobs-Oriented Organization

Team Structure

Option 1: Embedded researchers

• Researchers on each product team
• Continuous discovery, integrated with development
• Best for: Large organizations, complex products

Option 2: Central research team

• Shared research capability serving all products
• Standardized methodology, cross-product insights
• Best for: Multiple products, resource constraints

Option 3: Everyone does research

• Product managers, designers, engineers all interview
• Research is a skill, not a role
• Best for: Small teams, startups

Cultural Practices

Regular customer exposure:

• Monthly customer interviews for every PM
• Recordings shared team-wide
• "Customer of the week" highlights

Decision-making rituals:

• "What job does this serve?" in every roadmap discussion
• Job canvas for every major initiative
• Retrospectives include job validation

Metrics and reviews:

• Quarterly job completion metrics
• OKRs connected to customer progress
• Celebrate outcomes, not outputs

Knowledge Management

Job documentation:

• Job atlas maintained and updated
• Interview insights aggregated
• Competitive job mapping shared

Searchable repository:

• All interview notes and recordings
• Tagged by job, circumstance, dimension
• Accessible to entire organization

---

Change Management Playbook

Phase 1: Awareness (Weeks 1-4)

Activities:

• Present JTBD concepts to leadership
• Share case studies relevant to your business
• Identify internal champions
• Conduct one pilot research project

Milestone: Leadership agrees to pilot, one team engaged

Phase 2: Pilot (Weeks 5-12)

Activities:

• Train pilot team on JTBD methodology
• Conduct 10-15 customer interviews
• Document job findings
• Apply findings to one product decision
• Measure results

Milestone: Pilot produces actionable insights, one decision improved

Phase 3: Expansion (Months 4-6)

Activities:

• Share pilot results broadly
• Train additional teams
• Establish research operations
• Build job documentation
• Connect to roadmap process

Milestone: Multiple teams practicing, methodology documented

Phase 4: Integration (Months 7-12)

Activities:

• Jobs language in all product discussions
• Metrics shifted to job completion
• Hiring includes research skills
• Continuous discovery established

Milestone: JTBD is "how we work," not "that initiative"

---

Handling Resistance

From Engineers

Concern: "This is just going to change requirements mid-sprint."

Response:

• JTBD happens before sprint planning, not during
• Better job understanding = fewer requirement changes later
• You'll build things people actually use

From Sales

Concern: "Customers tell me what they want. I don't need research."

Response:

• Customer requests are input, not output
• Understanding why they want it helps you sell better
• Competitor feature requests aren't always right

From Marketers

Concern: "We already have personas and segments."

Response:

• Jobs complement personas with motivation
• Circumstance-based targeting often outperforms demographic
• Job statements make better copy than feature lists

From Product Managers

Concern: "I don't have time for research—I need to ship."

Response:

• Five interviews take less time than one failed feature
• Research prevents building the wrong thing
• Good PMs always talk to customers; this just structures it

---

Measuring Adoption

Leading Indicators

Lagging Indicators

Anti-Patterns to Watch

• "Job-washing": Using jobs language without doing research
• "One and done": Research project that doesn't continue
• "Cherry-picking": Only sharing findings that support existing plans
• "Performative interviews": Going through motions without learning