Conducting JTBD Customer Interviews: Product Manager Interview Questions That Reveal Real Jobs
This skill teaches you how to run switch interviews and timeline interviews that uncover the real jobs, hiring criteria, and switching triggers behind customer decisions, giving you the raw material for every other activity in the JTBD framework.
Start by recruiting people who recently switched to or from your product. Use a timeline interview format that walks backward from the moment of purchase through first thought, passive looking, active looking, and the deciding event. Ask about the push of the old situation, the pull of the new solution, the anxiety of change, and the habit of the present. Document forces, hiring criteria, and the functional job in the customer's own language.
Outcome: You produce a set of documented customer timelines, each containing the specific push/pull forces, anxieties, habits, hiring criteria, and switching triggers in the customer's own words, ready to feed into job mapping, outcome statement writing, and opportunity scoring.
Prerequisites
- Basic understanding of the JTBD framework and the concept of 'hiring' a product
- Familiarity with the Four Forces of Progress (push, pull, anxiety, habit)
- Access to customers or recent switchers willing to be interviewed
- A defined core functional job or hypothesis about the job (see defining-core-functional-jobs)
Overview
JTBD customer interviews are the primary research method inside the Jobs-to-be-Done (JTBD) Framework. They are not satisfaction surveys, usability tests, or feature request sessions. Their purpose is narrow and specific: reconstruct the timeline of a real decision so you can identify the functional job the customer was trying to get done, the forces that pushed and pulled them toward a new solution, and the criteria they used to evaluate their options. The output is a set of documented timelines and force diagrams that become the raw input for writing desired outcome statements, creating job maps, and identifying underserved outcome opportunities.
The two dominant interview formats are the switch interview and the timeline interview, and they overlap heavily. A switch interview focuses on someone who recently switched from one solution to another (including switching from "doing nothing" to adopting a product for the first time). A timeline interview zooms in on the chronological sequence of events: the first thought that something needed to change, passive looking for alternatives, an event that triggered active searching, the decision itself, and the experience of consuming the new solution. In practice, most JTBD interviews blend both: you find someone who switched, then walk them through their timeline. The distinction matters mainly when you are recruiting. You need people who made a real decision, not people who are hypothetically considering one.
What makes these interviews difficult is not the question list. It is the interviewing posture. Product manager interview questions in a JTBD context are designed to slow the conversation down and reconstruct emotional and contextual detail that the customer has already forgotten or rationalized. You are not asking "What features do you want?" You are asking "Take me back to the moment you first realized the old way wasn't working. Where were you? What happened?" The skill is in the follow-up, not the script. A novice interviewer asks the script questions and gets surface-level answers. An experienced interviewer notices when a customer skips a step in the timeline or rationalizes a decision after the fact, and gently pulls them back to the concrete moment. Mastering this skill produces insights that no survey, analytics dashboard, or competitive teardown can replicate.
The concrete artifact you produce is an interview document for each conversation, containing: the customer's timeline with dates and events, the four forces mapped (push of the current situation, pull of the new solution, anxiety about switching, habit of the current situation), the hiring criteria the customer used, the functional job in their language, and any emotional or social jobs that surfaced. After 8-12 interviews, you should see patterns converging. If you do not see patterns after 12 interviews, your recruiting criteria are too broad or you are interviewing the wrong population.
How It Works
JTBD interviews work because they exploit a psychological principle: people cannot accurately predict or abstractly describe their decision-making process, but they can reconstruct specific moments when prompted with enough contextual detail. When you ask someone "Why did you buy this product?" they give you a post-hoc rationalization. When you ask "Walk me through the moment you first realized the old approach was failing. What happened that day?" they access episodic memory, which is richer, more honest, and full of the emotional and situational context that actually drove the decision.
The timeline structure works as a scaffolding for episodic recall. By anchoring to real dates and events ("When was that? Was it before or after the holidays?"), you help the customer reconstruct a sequence they otherwise compress into a vague "I just decided to switch." Each phase of the timeline corresponds to a different insight:
- First thought: Reveals the push force. Something happened that made the status quo insufficient. This is often not a product failure. It is a life or business context change (a new hire, a lost deal, a policy change) that raised the stakes of an existing struggle.
- Passive looking: Reveals awareness channels and early filtering criteria. The customer starts noticing alternatives without actively seeking them. Understanding this phase tells you where and how to show up in the consideration set.
- Event triggers: Reveals the catalyst that converted passive discontent into active search. This is the most valuable signal for marketing and positioning because it tells you when customers become ready to buy, not just why.
- Active looking: Reveals the hiring criteria and the competitive set. What did the customer actually compare? What dimensions mattered? This phase is where the real product manager interview questions live, because the criteria the customer used to evaluate options are the desired outcomes your product must deliver.
- Decision and consuming: Reveals anxiety and habit forces. What almost stopped them from switching? What did they miss about the old solution? These forces explain churn risk and onboarding friction.
The Four Forces model (push, pull, anxiety, habit) is not just a framework for organizing notes after the interview. It is a real-time diagnostic tool during the conversation. If you notice a customer describing strong push and strong pull but they still took six months to switch, you know there is an unspoken anxiety or habit force you have not uncovered yet. That gap becomes your next question. This is why the Jobs-to-be-Done (JTBD) Framework emphasizes the forces model so heavily. The job alone does not predict behavior. The balance of forces does.
The model breaks down in a few predictable ways. Customers who switched a long time ago have degraded episodic memory, so you get thin timelines and rationalized answers. Customers who are heavy domain experts (e.g., a VP of Engineering choosing a database) over-index on technical criteria and under-report the emotional and political forces that actually drove the decision. And customers in high-consideration B2B purchases often conflate the "buyer" role with the "user" role, so you need to be clear about whose job you are mapping. Being aware of these failure modes lets you adjust your recruiting and question strategy before you waste interview slots.
Step-by-Step
Step 1: Define the switching event you want to study
Before you recruit anyone, get precise about which decision you are investigating. A switching event is a moment when someone hired a new solution (your product, a competitor, a workaround, or nothing) and fired an old one. " The timeframe matters because memory degrades. For consumer products, 90 days is ideal, 6 months is the upper bound.
For B2B enterprise software, 6-12 months works because the purchase cycle is longer and the decision is more memorable. " Avoid studying decisions older than 12 months unless you have no alternative. The more recent the switch, the richer the detail you will get.
Tip: If you are unsure which switching event to study, start with recent signups to your own product. They have the freshest memory and you already have their contact information. After 6-8 interviews you will know whether the pattern is strong enough or whether you need to broaden to competitor customers.
Step 2: Recruit 8-12 interview participants who match the switching event
The quality of your interviews depends almost entirely on recruiting the right people. You need people who made a real, completed decision, not people who are currently evaluating or people who are hypothetically interested. " Filter out anyone who answers no or gives vague answers. Aim for 8-12 participants.
If patterns have not converged by interview 8, continue to 15. If patterns are clear by interview 6, you can stop at 8. Offer a reasonable incentive ($50-100 for consumers, a donation to charity or a gift card for B2B professionals). Schedule 60-minute sessions.
Do not try to do this in 30 minutes.
Tip: The best recruiting channel depends on your context. For your own customers, use email outreach filtered by signup date. For competitor customers, use LinkedIn outreach, panel services (UserInterviews, Respondent), or ask in relevant communities. Avoid recruiting from your power-user base. They are outliers. You want the median customer who made a deliberate choice, not your biggest fan.
Step 3: Prepare your interview guide with timeline anchors and force prompts
Write a one-page interview guide, not a rigid script. The guide should contain three sections. First, a warm-up (2-3 minutes): explain that you are interested in the story of their decision, not evaluating them, and that there are no right or wrong answers. Second, the timeline reconstruction (35-45 minutes): start with the purchase or switch moment ("Tell me about the day you [signed up / bought / cancelled].
Where were you? "), then walk forward through passive looking, the trigger event, active evaluation, and the final decision. "). Print or display the guide, but do not read from it.
The guide is a safety net, not a teleprompter.
Tip: Prepare 5-7 specific follow-up probes for each timeline phase. Examples: "What happened right before that?" "Who else was involved in that moment?" "You said 'it was frustrating.' Can you tell me about a specific time it was frustrating?" These probes are what separate a productive interview from a surface-level one.
Step 4: Conduct the interview using the timeline reconstruction technique
Start the interview by asking about the moment of purchase or switch. This is counterintuitive because it is the end of the story, but it works because the purchase moment is vivid and concrete. " and keep asking it until you reach the first thought. Then walk forward through the timeline chronologically, filling in details at each phase.
Your job is to slow the customer down every time they summarize or skip ahead. When a customer says "I just decided it was time to switch," respond with "Take me back to that moment. " When they say "I compared a few options," ask "Which ones? How did you find them?
" Record the interview (with permission) so you can focus on listening and follow-up rather than note-taking. Stay in documentary filmmaker mode: curious, non-judgmental, interested in the details, never suggesting answers.
Tip: Silence is your most powerful tool. When a customer finishes a sentence and you say nothing for 3-5 seconds, they will often fill the silence with the real answer, the one they were not sure you wanted to hear. Resist the urge to ask the next question immediately.
Step 5: Probe the Four Forces in depth
After the timeline is reconstructed, spend 10-15 minutes explicitly mapping the four forces. For push, ask: "If nothing had changed about the old solution, would you still have switched? " For pull, ask: "What did you imagine your life or work would look like after switching? " For anxiety, ask: "What worried you about switching?
What could have gone wrong? " For habit, ask: "What did you have to give up or relearn? " Listen for imbalances. If push is very strong but the customer still took months to switch, there is a hidden anxiety or habit you have not uncovered.
If pull is weak but they switched anyway, there is a hidden push. The forces should explain the timeline. If they do not, probe further.
Tip: Anxiety and habit are the forces customers are least likely to volunteer. Ask about them directly. Many customers feel embarrassed admitting they almost did not switch because of inertia, so normalize it: "A lot of people tell me they almost stuck with the old way even though it was not working. Did that happen for you?"
Step 6: Identify the functional job and hiring criteria in the customer's language
" Write down the answer verbatim. This is the customer's articulation of the functional job. It will rarely be in clean outcome-statement format, and that is fine. " These are the hiring criteria, the dimensions the customer used to evaluate solutions.
They are the raw inputs for writing desired outcome statements. Capture the exact words. Do not translate into your product's feature language during the interview. The translation happens later, during synthesis.
Tip: If the customer gives you a feature-level answer ("I needed something with a Gantt chart"), ask "What would the Gantt chart help you do?" Keep asking "what would that help you do?" until you reach a functional outcome. Usually it takes 2-3 layers.
Step 7: Document the interview within 24 hours
Within 24 hours of the interview (while your memory of tone, hesitations, and emphasis is fresh), create a structured interview document. Use a consistent template with these sections: participant profile (role, company size, solution switched from/to, date of switch), timeline (first thought, passive looking, trigger event, active looking, decision, consuming, each with dates and quotes), four forces (push, pull, anxiety, habit, each with 2-3 supporting quotes), functional job (in customer's words), hiring criteria (2-5 dimensions), and surprising insights (anything that did not fit the framework but seemed important). Store all interview documents in a shared folder so the team can access them directly. This document is the primary artifact.
Everything downstream depends on its quality.
Tip: Use timestamps from the recording to link key quotes back to the source. When a stakeholder later questions an insight, you can play the exact moment. This eliminates the "but that is just your interpretation" objection.
Step 8: Synthesize across interviews to find patterns
After 6-8 interviews, start a synthesis pass. Create a summary table with one row per interview and columns for: trigger event, push forces, pull forces, anxieties, habits, functional job, and hiring criteria. Look for clusters. Are multiple customers describing the same trigger event?
Are the same hiring criteria appearing across interviews? Do the functional job descriptions converge on a common theme? Highlight the patterns that appear in 3 or more interviews. These are your high-confidence insights.
Single-interview insights are hypotheses to explore in future interviews, not conclusions. If you do not see patterns by interview 12, revisit your recruiting criteria. You may be interviewing people who made different types of decisions and should segment your research.
Tip: Color-code your synthesis table. Green for patterns appearing in 5+ interviews, yellow for 3-4, red for 1-2. Present stakeholders with the green patterns first. They are the foundation for product and positioning decisions.
Step 9: Translate insights into JTBD artifacts for downstream work
The final step is converting your synthesized patterns into the specific artifacts that other JTBD activities require. Write a draft core functional job statement using the converging language from your interviews. Extract hiring criteria and rephrase them as candidate desired outcome statements (direction + metric + object of control). Map the timeline phases across interviews into an initial job map showing the steps customers go through to get the job done.
Note which outcomes and steps showed the most frustration, the highest emotional energy, or the longest delays. These are your initial candidates for underserved outcome opportunities. Package the full research into a brief (2-3 pages) that includes the functional job, top 5 hiring criteria, the dominant trigger event, and the force diagram. This brief becomes the input for product strategy and roadmap conversations.
Tip: Share the brief with 2-3 people who were not involved in the research and ask them to summarize the key insight. If their summary does not match yours, your brief is not clear enough. Rewrite before circulating widely.
Examples
Example: B2B SaaS project management tool (Series A, 15-person team)
A project management startup wants to understand why customers switch from spreadsheets and email to their tool. The team has 200 signups in the last 60 days. The PM and one designer will run the research. Budget is $500 for incentives.
' She screens signups with a 3-question email survey: (1) What were you using before? (2) When did you sign up? (3) Are you the person who decided to try our tool? Of 200 signups, 45 respond, and 18 match the criteria.
She schedules 10 interviews at $50 Amazon gift cards each, spacing 2-3 per week. ' By interview 7, 5 of 7 participants describe the same pattern: a visible project failure (missed deadline, dropped deliverable, confused handoff) witnessed by someone important, which created urgency to switch from informal tracking. ' Hiring criteria cluster around: (1) can my team see status without asking me, (2) takes less than 10 minutes to set up for a new project, (3) does not require everyone to learn a complex system. ' The PM packages these findings into a 2-page brief and shares it with the team.
The product roadmap shifts from building advanced Gantt chart features (which zero interviewees mentioned as a hiring criterion) toward a simplified status dashboard and a guided onboarding flow that gets a team of 5 set up in under 10 minutes.
Example: Consumer fitness app (early stage, 3-person founding team)
A fitness app founder wants to understand why people switch from free YouTube workout videos to a paid app. The team has no existing customer base beyond 50 beta users. Budget is minimal. The founder will conduct all interviews personally.
com panel, offering $30 gift cards. She recruits 8 participants across 3 different apps (not just hers) to understand the job broadly. ' and corrects course, instead asking 'Tell me about the last time you did a YouTube workout. ' A consistent timeline emerges: customers spent 3-6 months doing free workouts, plateaued (stopped seeing results or got bored), tried to create their own programming by combining YouTube videos, found it overwhelming, and then searched for a structured program.
The trigger event was typically a visible plateau: stepping on the scale, trying a harder workout and failing, or a friend commenting on lack of visible progress. ' Pull forces included accountability features (streaks, reminders) and progressive difficulty. '). The founder realized her app's positioning ('AI-powered personalization') was not matching the job.
Customers wanted structure and progression, not algorithmic novelty. She rewrote her landing page to lead with 'Stop cobbling together random workouts. 8% in the next 30 days.
Example: Enterprise HR platform (growth stage, 80-person company)
An HR tech company wants to understand why mid-market companies (200-2000 employees) switch from one HRIS to another. Sales cycles are 3-6 months. The research team includes a product manager, a UX researcher, and a product marketing manager. Budget is $2,000 for incentives and panel access.
' The 12-month window is necessary because enterprise migrations take 2-4 months themselves. The UX researcher recruits through LinkedIn outreach to HR directors and VP-level contacts, supplemented by a B2B panel service. She offers $150 Amazon gift cards and schedules 75-minute sessions (longer than consumer interviews because the decision involved more stakeholders and steps). Ten interviews are scheduled across three weeks, with the product marketing manager observing every other interview.
A critical finding emerges in interview 2 and repeats in 7 of 10 interviews: the decision-maker (usually VP of HR or CHRO) and the primary user (usually HR operations manager) had different jobs. ' Both jobs were real, but the hiring criteria differed. The decision-maker cared about executive dashboards, workforce analytics, and presentation-ready reports. The user cared about integration depth, data accuracy, and workflow automation.
Anxiety forces were enormous: the migration itself (3 months of parallel systems, data migration risk, and employee retraining) was the dominant anxiety for both roles. Habit forces centered on institutional knowledge embedded in the old system's custom fields and workarounds. The team realized their sales process was pitching strategic analytics (decision-maker job) but their trial experience optimized for data entry speed (user job). They restructured the demo to show both perspectives in sequence: first the executive dashboard to sell the decision-maker, then the integration workflow to reassure the user.
They also created a detailed migration playbook to directly address the anxiety force. Win rate on competitive deals increased from 28% to 41% over two quarters.
Example: DTC e-commerce brand (small team, product expansion research)
A direct-to-consumer ergonomic desk accessories brand wants to understand why home office workers buy their first standing desk converter. The brand sells accessories (monitor arms, keyboard trays) and is considering adding a desk converter to the product line. The founder and one marketing hire will conduct interviews.
' She cannot interview her own customers (they bought accessories, not converters), so she recruits through a home office subreddit and a panel service. She recruits 9 participants at $40 each. The timeline interviews reveal a consistent 3-phase journey. Phase 1 (passive, 2-12 months): the customer experiences back pain or fatigue, reads articles about standing desks, but does nothing because the investment feels unjustified for a home office.
Phase 2 (trigger, days to weeks): the customer gets a medical signal (doctor's recommendation, increasing pain, a friend having back surgery) or a permanence signal (company announces permanent remote work, customer signs a longer apartment lease with a home office). Phase 3 (active search, 1-4 weeks): customer compares options on Reddit, YouTube reviews, and Amazon, filters by price (under $400), desk compatibility, and adjustability range. ' The founder decides to launch a converter, but the interview insights change the product strategy. Instead of competing on adjustability range (the typical differentiator), she focuses on stability with monitors (the dominant anxiety), compatibility with existing desks (the functional job constraint), and a 30-day return guarantee (directly addressing 'what if I stop using it').
She also changes the marketing angle from health benefits to home office permanence: 'You are working from home for good.
Best Practices
Interview the decision-maker, not the user, when they are different people. In B2B, the person who signed the contract and the person who uses the product daily often have different jobs and different hiring criteria. If you interview only users, you will optimize for consumption satisfaction and miss the forces that drive purchase decisions. Clarify in recruiting which role you need.
Always ask 'When was that?' to anchor events in time. Customers will compress a six-month decision into 'I just decided to try it,' and without temporal anchors you cannot reconstruct the actual timeline. Dates do not need to be exact. 'Before Thanksgiving' or 'right after our Q2 planning' is sufficient. The point is to separate events that felt simultaneous but actually happened weeks apart.
Record every interview with explicit permission and transcribe it before synthesis. Notes taken during the conversation are filtered through your existing assumptions. Transcripts give you the customer's actual language, which is the raw material for outcome statements and positioning copy. If a customer declines recording, take near-verbatim notes and flag any paraphrasing.
Never interview more than two people in a single day. Interview fatigue causes you to stop following up on interesting threads, ask leading questions, and hear what you expect instead of what the customer says. Schedule interviews with at least a 90-minute gap for note-taking and mental reset. Three interviews in a week is a sustainable pace.
Separate the interviewing phase from the interpretation phase. During the interview, your only job is to reconstruct what happened and capture the customer's language. Resist the temptation to map answers to product features, validate your hypothesis, or celebrate confirming evidence during the conversation. Interpretation happens during synthesis. Mixing the two phases biases both.
Treat each interview as a documentary, not a deposition. Your tone should be genuinely curious, warm, and unhurried. Customers reveal more when they feel like they are telling a story to a fascinated listener than when they feel like they are answering a questionnaire. Smile, nod, express genuine interest. 'That is interesting, tell me more about that moment' is your most-used sentence.
Validate emerging patterns by deliberately seeking disconfirming evidence. After 4-5 interviews, you will start forming a hypothesis about the dominant job and forces. In interviews 6-8, actively probe for exceptions: 'Some people I have talked to mentioned [opposite pattern]. ' If your hypothesis survives this stress test, it is robust.
If it collapses, you have saved yourself from building on a false pattern.
Keep a running 'surprising quotes' document alongside your structured interview notes. The insights that change product strategy are often not the answers to your planned questions. They are the off-hand comments, the emotional outbursts, and the casual asides that do not fit any framework. Capturing them separately ensures they do not get lost during structured synthesis.
Common Mistakes
Asking hypothetical questions instead of reconstructing real events
Correction
The most common novice error is asking 'What would you look for in a solution?' or 'Would you use a feature that does X?' These questions produce unreliable answers because people are bad at predicting their own behavior. The signal that you are doing this is when your notes contain words like 'would,' 'might,' 'ideally,' or 'probably.' Catch yourself and redirect: 'Let us go back to what actually happened. When you were evaluating options, what did you actually look at first?' Every answer should reference a real event, not a hypothetical scenario.
Accepting the customer's first explanation without probing deeper
Correction
' This is almost always a post-hoc rationalization. The signal is that the story sounds too simple, too rational, and too short. Real decisions are messy, emotional, and drawn out. When you hear a tidy narrative, probe the gaps: 'You said you needed better reporting.
Was there a specific report you tried to run that did not work? ' Pull them into the concrete moment and the real story will emerge, usually involving politics, frustration, or an embarrassing failure that they did not want to lead with.
Leading the witness with product-centric questions
Correction
Product managers instinctively ask about their own product: 'Did you try our integration feature?' 'Was our pricing competitive?' These questions anchor the customer to your frame and prevent them from telling you what actually mattered. The signal is when every interview confirms your existing beliefs and nothing surprises you. Use open-ended questions that start with 'Tell me about...' or 'Walk me through...' and let the customer bring up the dimensions that mattered to them. If your product's integration feature never comes up organically in 8 interviews, that is data: it was not a hiring criterion.
Interviewing current happy customers instead of recent switchers
Correction
Interviewing your biggest fans feels productive because they say nice things, but it produces almost no JTBD insight. Happy customers have already rationalized their decision and forgotten the messy journey. The signal is that your interview notes are full of praise and light on timeline detail. Recruit people who switched within the last 90 days (or 6 months for B2B).
Recent churned customers are equally valuable, sometimes more so, because they can describe both the forces that pulled them in and the forces that pushed them out.
Stopping at the functional job and ignoring emotional and social forces
Correction
Some product teams treat JTBD interviews as purely functional: what task, what outcome, what metric. This misses half the picture. ) played a significant role. The signal is that your force diagram has detailed push and pull entries but empty anxiety and habit sections.
Ask explicitly: 'How did you feel about making this change? What would your team think if it did not work out? ' These questions feel personal, which is why interviewers skip them. But the answers often explain the timing and urgency of the switch better than any functional analysis.
Conducting interviews solo without ever involving stakeholders
Correction
If you are the only person who heard the interviews, you become a bottleneck and a single point of interpretation. Engineers, designers, and marketers will question your summary because they did not experience the conversation. Invite one stakeholder to observe (camera off, muted) for every 3-4 interviews. Rotate who observes.
After the interview, spend 10 minutes debriefing with the observer about what they heard.
Other Skills in This Method
Identifying Underserved Outcome Opportunities
How to use opportunity scoring (importance vs. satisfaction) to quantify which desired outcomes are most underserved and represent the best innovation targets.
Applying JTBD Insights to Product Strategy and Roadmaps
How to translate job maps, outcome scores, and opportunity landscapes into actionable product roadmaps, feature priorities, and go-to-market positioning.
Defining the Customer's Core Functional Job
How to identify and articulate the fundamental job a customer is trying to accomplish, using proper job statement syntax and structure.
Writing Desired Outcome Statements
How to craft properly structured outcome statements (direction + metric + object of control + context) that capture measurable customer success criteria at each job step.
Creating Job Maps to Visualize Customer Processes
How to break down a core functional job into its universal process steps (define, locate, prepare, confirm, execute, monitor, modify, conclude) to map the full customer journey.
Segmenting Customers by Unmet Needs
How to create outcome-based customer segments that group people by shared underserved outcomes rather than demographics, enabling more targeted product strategies.
Frequently Asked Questions
How many JTBD interviews do I need before I can act on the findings?
Plan for 8-12 interviews. Most teams see clear patterns emerge between interviews 6 and 8, with interviews 9-12 serving as confirmation. If you reach interview 12 and patterns have not converged, your recruiting criteria are too broad. You may be interviewing people who made fundamentally different types of decisions. , same company size, same solution switched from) and run another round of 6-8. Acting on fewer than 6 interviews is risky because you may be building on a pattern from 2-3 unrepresentative cases.
Should I conduct JTBD interviews before or after defining the core functional job?
Start with a hypothesis about the core functional job, then use interviews to validate, refine, or completely rewrite it. You need a hypothesis to recruit the right people. If your hypothesis is 'the job is managing projects efficiently,' you will recruit people who recently adopted project management tools. If the interviews reveal the actual job is 'make project status visible to stakeholders,' you update your job definition. See [defining the core functional job](/skills/defining-core-functional-jobs) for how to form the initial hypothesis. The interviews are the validation mechanism, not the starting point.
How do I handle JTBD interviews when the customer is not the decision-maker?
Interview both the decision-maker and the user separately when possible. In B2B contexts, the person who signed the contract and the person who uses the product daily often have different jobs, different hiring criteria, and different force balances. The decision-maker's interview reveals the buying job. The user's interview reveals the consumption job. If you can only interview one, prioritize the person who initiated the search for a new solution, because they experienced the push force directly. Document which role each interviewee played so you do not accidentally mix buying criteria with usage criteria during synthesis.
What product manager interview questions work best for uncovering the trigger event?
The most effective product manager interview questions for trigger events are: 'Was there a specific moment when you decided you needed to actually do something about this?' and 'What happened right before you started actively looking for a solution?' Follow up with 'Were you alone when this happened or was someone else involved?' and 'Had you felt this way before? What was different this time?' The trigger event is typically not a product failure. It is a context change (new role, new client, new deadline, new team member) that raised the stakes of an existing frustration above the customer's tolerance threshold.
How do I run JTBD interviews when I have no existing customers?
Interview people who recently adopted a competitor product, a workaround, or any solution in your category. The job exists independent of your product. If you are building a new project management tool, interview people who recently started using Asana, Monday, Notion, or even a new spreadsheet-based system. The switching event is the same: they fired one approach and hired another. io, or by posting in relevant Slack or Discord communities. Focus on learning the job and forces, not on validating your specific product idea.
Why does my JTBD interview data keep producing conflicting insights?
Conflicting insights usually mean you are interviewing people with different jobs. A common cause is recruiting too broadly. If your screening criterion is 'anyone who bought our product,' you will get people who hired it for completely different reasons. One customer hired a CRM to manage sales pipeline, another hired the same CRM to manage investor relationships. These are different jobs with different hiring criteria, and their interview data will conflict. The fix is to segment your interviewees by the job they were trying to get done, then analyze each segment separately. See [segmenting customers by unmet needs](/skills/segmenting-customers-by-unmet-needs) for how to identify and validate these segments.
Can I combine JTBD interviews with usability testing or feature feedback sessions?
Do not combine them in a single session. JTBD interviews require a documentary mindset: you are reconstructing a past decision with no agenda other than understanding what happened. Usability testing requires an evaluative mindset: you are observing someone interact with your product and identifying friction. Feature feedback requires a speculative mindset: you are asking people to react to something that does not exist yet. Mixing these modes confuses both you and the participant. ' Run JTBD interviews as a standalone research activity. Use the findings to inform what you test in separate usability and concept testing sessions.