A product use interview traces the distance between the purchase and the moment the product started working. It covers the functional jobs of usage and consumption — setting up, learning, fitting it alongside existing tools, bringing other people along, and getting support — rather than the job that drove the purchase. What surfaces is where onboarding stalls and what customers had to work out for themselves. This guide is a pool of 26 questions across four phases; 13 are marked core, which is about what fits in a 45-minute interview.
Last updated 2026-08-03John Gusiff, Customer Centric Solutions LLCFree to use and cite
- General
- Events & Timeline
- Pushes
- Pulls
- Desires
- Avoidances
- Habits
- Anxieties
- Solutions
- Constraints
- Experiences (gain / pain)
Phase 01
Open
Ask 2 of 3 · ~5 min
Get the adoption story from the moment of purchase to first real value. Let them narrate it before you probe any part of it.
-
01
Imagine that I am filming a documentary.
Documentary framing captures the real adoption journey, not an idealised version.
GeneralCore -
02
Tell me the story about buying this product. What, when, how?
Starts the story at the point of purchase — the beginning of the adoption journey.
GeneralCore -
03
Describe your first impressions with the product (unboxing)?
First impressions at unboxing/onboarding set the tone for the whole adoption arc.
ExperiencesGainPainOptional
Phase 02
Explore the Onboarding Experience
Ask 4 of 9 · ~16 min
Map the friction and delight moments through setup, learning, fitting it alongside existing tools, and bringing other people along.
-
04
How difficult was it to setup or install the product?
Setup difficulty is a top early-churn driver — isolate specific friction points.
ExperiencesGainPainCore -
05
How difficult was it to learn how to use the product or service?
Learning curve reveals whether time-to-value is longer than expected.
ExperiencesGainPainCore -
06
Describe anything that surprised you (good/bad) using the product.
Surprises (good and bad) reveal gaps between marketing promise and product reality.
ExperiencesGainPainOptional -
07
What stood in the way of achieving the desired outcome?
What stood in the way of getting value — is the barrier the product or the user's context?
ConstraintsCore -
08
What did you do or use to solve this need before?
What they were doing before, as the baseline they judge onboarding against. Friction only feels like friction relative to the old way.
HabitsOptional -
09
Any worries about the solution you chose?
Adoption anxiety — the worry that they had picked wrong, or could not make it work. Often what stalls a rollout before any feature does.
AnxietiesOptional -
10
How does it fit alongside the other tools you already use?
Whether it slotted into the existing stack or fought it. Integration friction rarely shows up in support tickets but reliably kills adoption.
Customer JTBDFunctional (usage/consumption)Core -
11
Who else had to be brought along before it stuck?
Who else had to be convinced. Single-user activation and team adoption fail for entirely different reasons.
Customer JTBDFunctional (usage/consumption)Optional -
12
What else did you buy to enhance the product/service experience?
What they bought or added alongside it. Reveals gaps they filled themselves — the clearest roadmap signal in this interview.
SolutionsOptional
Phase 03
Probe Value Realisation
Ask 5 of 9 · ~15 min
Understand when and how they first felt the product was working for them — and what they had to work out for themselves to get there.
-
13
Walk me through the first time you used it for real work.
The first real use, narrated. Look for what they had to work out for themselves between buying and getting value.
Customer JTBDFunctional (usage/consumption)Core -
14
When did you first feel it was actually working for you?
The moment it started working. If they cannot name one, you have found an activation problem rather than a value problem.
Customer JTBDFunctional (usage/consumption)Core -
15
What does this product enable you to do?
The enabling outcome — what could they now do that they couldn't before? This is the "aha."
Customer JTBDNot about ProductCore -
16
What will this product enable you to do?
Did the product deliver on the enabling vision they had when they bought?
DesiresNot about ProductOptional -
17
How has this product improved your life or business?
The improvement in their own terms. Compare against what they said they were hoping for — the gap is your positioning problem.
Customer JTBDImprovementCore -
18
Were you solving a problem or improving your life?
Whether this was pain relief or an upgrade. Changes what "working" even means to them.
Customer JTBDPleasure vs. PainOptional -
19
How often do you use this product or service?
Usage frequency signals whether value has been realised and habituated.
Continuous UseCore -
20
Have you recently tried alternative products?
Whether they are already sampling alternatives. Early in the lifecycle this reads as curiosity; later it reads as risk.
Continuous UseOptional -
21
How do you feel about the purchase now?
Post-adoption reflection — do they feel the purchase was worth it?
ExperiencesGainPainOptional
Phase 04
Close
Ask 2 of 5 · ~9 min
Capture support needs and continuation intent, then confirm your understanding by playing the story back.
-
22
Did you ever need service or support? How was this experience?
Support touchpoints often reveal systematic onboarding gaps.
ExperiencesGainPainCore -
23
Are you confident the product will continue to satisfy your needs over time?
Forward-looking confidence check — are they staying or at risk?
ExperiencesGainPainOptional -
24
After the trial do you plan on subscribing?
Intent to continue, asked plainly. The answer matters less than the hesitation before it.
Continuous UseOptional -
25
Anything else you would like to share about your product or service experience?
Open question to surface anything the structured questions missed.
ExperiencesGainPainOptional -
26
Let me playback your story. Correct me if I get it wrong.
Play back the adoption arc to confirm your understanding.
GeneralCore