jtbd-fundamentals-and-interviewing

name: jtbd-fundamentals-and-interviewing description: > Apply Jobs-to-be-Done (JTBD) theory and the canonical interview techniques: Jobs Interviews, Switch Interviews (Bob Moesta), Inverted Switch (cancellation), Customer Case Research (CCR), the Four Forces of Progress (Push, Pull, Anxiety, Habit), the Switch Timeline (six phases), the Milkshake Marketing reframe. Use when scoping customer research, designing interview protocols, understanding why customers switch (or don't), uncovering unarticulated needs, separating jobs from solutions. Triggers: "JTBD interviews", "Switch technique", "Bob Moesta", "why did they switch", "cancellation interview", "Four Forces of Progress", "milkshake reframe", "jobs vs solutions", "uncover unarticulated needs". Produces an interview protocol + analysis approach.

JTBD Fundamentals and Interviewing

You apply Jim Kalbach's Jobs to be Done Playbook methodology: customers hire products to make progress toward an objective. You uncover those objectives via specific interview techniques (Jobs, Switch, CCR), separating the job from any specific solution.

When to Use This Skill

Scoping customer research that isn't preference / demographic
Designing interview protocols (jobs / switch / cancellation)
Understanding why customers switched to or away from a product
Uncovering unarticulated needs (what customers can't tell you directly)
Repositioning a product against unexpected competition
Diagnosing churn root causes

The JTBD Lens

People hire products to make progress toward an objective.

Three implications:

Job ≠ solution. "Get breakfast on the go" is the job; milkshake is one solution.
Job is stable; solutions change. The job persists across decades; the products that fulfill it cycle.
Competition is solution-agnostic. Tax software competes with pencils, accountants, and skipping filing entirely.

The Milkshake Marketing Reframe

Clayton Christensen's canonical example: McDonald's tried to improve milkshake sales by tweaking flavor / texture / pricing. Sales flat. Researchers observed customers and discovered the morning milkshake was hired for "make my long boring commute more interesting and keep me full until lunch." Different job → different innovations win (thicker, more chunks, longer-lasting).

The reframe: Stop asking "how do customers feel about our product?" Start asking "what job were they hiring it to do, and how well did it do that?"

Three Job Layers

Layer	What it is	Example (gym membership)
Functional	The actual progress (objective, measurable)	"Improve cardiovascular fitness"
Emotional	How the customer feels during/after	"Feel disciplined and capable"
Social	How others perceive the customer	"Be seen as someone who takes care of themselves"

Hierarchy rule: Functional first. Emotional and social can't be solved if the functional job fails.

Job Performer vs Buyer vs Other Roles

Role	Definition
Job Performer	The end user executing the job
Buyer	Who pays / chooses
Approver	Who can veto
Manager	Who sets context for the performer
Reviewer	Who provides feedback after
Audience	Who observes
Assistant	Who helps the performer

The Job Performer is the primary unit of analysis. Confusing buyer with performer (especially in B2B) leads to product-market mismatch.

Jobs Interviews

A surgical, open-ended interview about objectives, process, and needs — without referencing specific products or solutions.

Why solution-free?

If you ask "what would you change about Product X?" you get features. If you ask "tell me about the last time you tried to [achieve objective]" you get the job.

Core questions

"Walk me through the last time you tried to <objective>."
"What were you trying to accomplish?"
"What got in the way?"
"What did you do when you encountered <obstacle>?"
"What would have made this easier?"
"What would 'success' look like to you?"

Discipline

No leading questions
No mentioning your product (until much later, if at all)
No "would you use a feature that...?"
Long silences — let the participant fill them
Probe specifics ("can you show me the email/calendar/spreadsheet?")
Watch for what they didn't say (workarounds, frustrations they normalized)

The Switch Technique (Bob Moesta)

Reverse-engineers the decision to switch. Pioneered by Bob Moesta and Chris Spiek at Re-Wired Group.

Switch Timeline (Six Phases)

1. First Thought          — when did the seed of switching first appear?
2. Passively Looking      — when did you start noticing alternatives?
3. Actively Looking       — when did you decide you needed to actually switch?
4. Deciding               — what were the final factors?
5. Consuming              — what did you experience post-switch?
6. Satisfaction           — looking back, was it the right move?

What this reveals

Forces driving switch (push from old, pull to new)
Anxieties (uncertainty, fear of change)
Habits (inertia keeping them with old)
Triggering events (specific moments that tipped them)

The switch interview is dense — typically 60-90 minutes per person, transcribed and analyzed.

Four Forces of Progress

                  Push of the situation
                         │
                         ▼
     Habit ◄───── [DECISION POINT] ─────► Pull of new solution
     of present                          
                         ▲
                         │
                  Anxiety of new solution

Every behavior change is the result of these four forces:

Force	Drives change?
Push of the situation	Yes — pain with current state
Pull of the new solution	Yes — promise of progress
Anxiety of new solution	NO — uncertainty, friction
Habit of the present	NO — comfort, familiarity

For change to happen: Push + Pull > Anxiety + Habit.

For your product to win:

Amplify push (help them see pain of status quo)
Amplify pull (vivid demos of progress)
Reduce anxiety (case studies, free trials, refunds)
Reduce habit (low switching cost, easy migration)

Inverted Switch Interview (for Cancellations)

Same Switch structure, applied to why customers leave you. Six phases reframed:

Phase	Question
First Thought	When did you first consider canceling?
Passively Looking	What started bothering you about the product?
Actively Looking	When did you start evaluating alternatives?
Deciding	What was the final straw?
Consuming	What's life like without our product?
Satisfaction	Are you glad you canceled?

Yields: Specific patterns in cancellation. Often reveals that customers churn for jobs you didn't realize you were hired to do.

Customer Case Research (CCR)

Origin: Denise Nitterhouse and Gerald Berstell.

A more open-ended ethnographic-style technique. Documents:

Unexpected openings (situations that triggered need)
Embedded segments (sub-populations within "your customer")
Hidden decision-makers (unrecognized stakeholders)
Unintended product uses (features used unexpectedly)
Unforeseen obstacles (friction you don't see)
Unarticulated needs (what customers don't say in interviews)

When: Beyond Jobs/Switch interviews. When you suspect "we're missing something fundamental."

Format: Long-form (1-2 hour) interviews + observations + artifact review (emails, screens, notes).

Hierarchy of Abstraction

A job can be stated at multiple levels of specificity:

HIGHER (more abstract)
   ▲
   │   Get fed for the day
   │       │
   │       ▼
   │   Get breakfast on the way to work
   │       │
   │       ▼
   │   Have something quick that lasts until lunch
   │       │
   │       ▼
   │   Eat in the car without making a mess
   ▼
LOWER (more specific)

Choose the level that matches your decision.

Strategic positioning → higher abstraction (broader market view)
Feature design → lower abstraction (specific actions)
Innovation roadmap → middle (specific enough to guide; abstract enough to allow alternatives)

Principles

Job ≠ solution. Solutions change; jobs are stable.
Job Performer is the primary unit. Not buyer, not approver.
Functional first; emotional and social on top.
Causality over correlation. Why people act, not what demographics they are.
Discover, don't invent jobs. Interview real people.
Solution-free interviews. Don't reference your product.
Probe specifics. "Show me the spreadsheet" beats "describe in general."
Silence is signal. What they didn't say matters.
Switch interviews are 60-90 minutes. Don't truncate.
Four forces are predictive. Use them to design adoption strategy.

Anti-Patterns

Asking About the Product

Looks like: "What do you like about Product X? What would you change?"

Why it fails: Gets opinions and feature requests, not jobs. People rationalize their feature wishes.

The fix: Ask about the last time they tried to accomplish something. Don't mention your product.

Demographic-First Segmentation

Looks like: "Our user is 35-44, female, urban, college-educated, $100K+ income."

Why it fails: Demographics correlate with jobs imperfectly. Two people in the same demographic can have different jobs.

The fix: Job-based segmentation. "Customers hiring our product to do X" cuts across demographics.

Skipping Functional Job

Looks like: Marketing focused on emotional appeal ("feel like a winner!") while functional job is unfulfilled.

Why it fails: Customers can't feel like winners if the product doesn't actually work.

The fix: Solve functional first. Layer emotional and social on a working foundation.

Confusing Buyer with Performer (B2B)

Looks like: B2B product designed for the procurement officer; ignored by the actual users.

Why it fails: Buyer and Performer have different jobs.

The fix: Identify each role explicitly. Design for Performer; persuade Buyer.

Switch Interview as 30-Minute Survey

Looks like: Quick phone call. Skip phases. Ask about high-level feelings.

Why it fails: Switch decisions live in specifics. Compressing the timeline loses critical detail.

The fix: 60-90 minute interview. Six phases. Specifics throughout.

Never Doing Cancellation Interviews

Looks like: Surveying churned users with "why did you leave?" multiple-choice.

Why it fails: Reasons people leave are messy and surprising. Multiple-choice doesn't capture the actual job-mismatch story.

The fix: Inverted Switch interviews on a sample of churners. Patterns emerge from 5-10 interviews.

Generic Personas Built From Demographics

Looks like: "Marketing Mary" personas with photo, age, income, hobbies.

Why it fails: Doesn't predict behavior. Doesn't guide design.

The fix: Goal-driven (Cooper) or job-based personas. "Customer hiring product to achieve X."

One Job, Forever

Looks like: "We've defined our customer's job. We're done with research."

Why it fails: Jobs evolve. New use cases emerge. Competitive landscape shifts.

The fix: Continuous customer research. Re-interview annually at minimum. Track new patterns.

Decision Rules

Situation	Action
About to do customer research	Start with Jobs interviews; don't reference products
Want to understand acquisition	Switch interviews on recent customers
Want to understand churn	Inverted Switch interviews on cancellers
Repositioning a product	Re-do Jobs interviews; check if jobs have shifted
Suspected blind spot	CCR (longer ethnographic) interviews
Persona feels off	Replace demographic with goal/job-based
B2B product	Map all roles; design for Performer; persuade Buyer
Innovation strategy	Higher abstraction job statement
Feature design	Lower abstraction job statement
Adoption challenge	Apply Four Forces analysis; amplify push + pull; reduce anxiety + habit
Competitor analysis	Solution-agnostic — list everything that gets the job done, not just same-category players
Marketing struggling	Verify functional job is solved; don't lead with emotional
Customer says "I want feature X"	Probe — what job is feature X serving?
Switch timeline missing phases	Interview was too short; redo
Churn surveys aren't surfacing patterns	Switch to Inverted Switch interviews; multiple-choice can't capture this

Worked Example: Why Are Customers Canceling Our SaaS?

Context: B2B SaaS. Cancellation rate climbing. Surveys saying "didn't use enough" and "too expensive." Unhelpful.

Approach: Inverted Switch interviews on 8 recent cancellers.

Findings (synthesized):

Phase	Pattern
First Thought	Triggered by team reorganization in 5/8 cases — internal advocate left
Passively Looking	Started noticing competitor ads; comparing in head
Actively Looking	Asked colleagues; trial of competitor
Deciding	Final straw was UI change in our product Q2 release
Consuming	Most miss our integrations; not the core feature
Satisfaction	4/8 are unhappy with the switch but committed

Insights (vs the survey):

"Didn't use enough" → really, internal champion left. Job-performer changed; new performer didn't have the relationship.
"Too expensive" → really, price wasn't justified after UI change. The change reduced perceived value.

Action plan:

Customer Success: identify accounts with single champion; over-invest in second-champion relationships
Product: re-evaluate the UI change with switching-cost lens
Marketing: lead with integrations (the moat the competitor doesn't match)

Result: 6 months later, churn down 40% in mid-market segment.

Lesson: Surface-level survey reasons hide the real job stories. Inverted Switch interviews surface them.

Gotchas

Switch interviews require trust. Customers may not be candid. Use a third-party researcher when possible.
Recall bias. Memory of switch decisions degrades. Interview within 90 days of switch.
Self-report ≠ behavior. What people say they did and what they actually did differ. Combine interviews with observation/data.
CCR is expensive. 1-2 hours per interview + observation. Reserve for high-stakes investigations.
Job-based personas can become abstract. Ground them in real customer quotes and behaviors.
Jobs are stable, but contexts shift. Same job, new context (remote work) = new opportunities.
Demographics still useful for marketing reach. Job-based for design; demographic-based for media targeting. Both, not either.
B2B Performer ≠ Decision-Maker. Map both; design for Performer; persuade Decision-Maker.