Start with a question, not an explanation
When a customer stops using a product, it is tempting to label the departure as a response to price, a missing feature or a competitor. An interview can help you examine those possibilities, but it should not begin by treating any of them as fact. The useful question is often broader: what changed between the period when the product fit the customer’s life and the period when it no longer did?
Define the decision you hope to make before recruiting participants. You might need to understand where people got stuck during setup, whether the product remained relevant after an initial project, or what made an alternative easier to use. That focus helps you choose whom to interview and keeps the conversation from becoming a general request for complaints.
Recruit for different kinds of departure
“Stopped using” can describe several experiences. Someone may have canceled deliberately, let a subscription lapse, switched to another tool or kept an account while quietly abandoning the work it was meant to support. If these groups matter to your decision, distinguish them when recruiting rather than pooling everyone into a single category.
Include a range of prior engagement where practical. A person who left after one attempt may describe a different journey from someone who relied on the product for a year. Consider how recently people left, too: recent departures may be easier to reconstruct, while people who left longer ago may have a clearer view of what they do now. Neither perspective is a substitute for the other.
An invitation should make clear that the conversation is for learning, not a sales call. Give people room to decline, and avoid asking them to defend their decision. Those who agree to speak may have stronger feelings or more available time than those who do not, so treat their accounts as informative rather than representative of everyone who left.
Reconstruct the change over time
Begin with the customer’s original goal: what were they trying to accomplish when they first chose the product? Then move through a recent, specific period of use. Ask what work they were doing, when the product came up, what happened and what they did next. A sequence of concrete events is usually more useful for diagnosis than a request for an overall satisfaction rating.
Do not assume there was one decisive exit moment. You can ask, “When did you first notice you were using it less?” and “What were you doing instead at that point?” If the participant describes a failed task, explore the surrounding conditions: the deadline, other people involved, available options and any workaround they tried. If they cannot recall a detail, leave it uncertain rather than supplying a possible answer.
Listen for changes outside the product as well. A completed project, a new job, a reduced budget or a different household routine could make a once-useful product unnecessary. Understanding that context prevents a team from treating every departure as a defect it can fix.
Explore alternatives without turning the interview into a comparison quiz
Ask what, if anything, replaced the product. The answer may be a competitor, a spreadsheet, help from another person or no solution at all. Find out how the customer now handles the underlying task and which trade-offs they accept. If they mention another product, ask what they actually used it for rather than requesting a feature-by-feature verdict.
Keep the interviewer out of sales mode. Correcting a misunderstanding, explaining a feature the customer missed or offering a discount can interrupt the account you are trying to understand. Note the point for later follow-up through an appropriate channel instead. During the interview, a useful response is to ask what the customer expected to happen and how they decided what to do next.
Turn exit stories into questions you can test
After the interviews, separate observed events from your interpretations. “The participant tried to share a file twice and then used email” is a different kind of note from “sharing is too difficult.” Look for recurring sequences, but preserve departures that do not fit the emerging pattern. A small set of interviews can reveal plausible explanations without establishing how common each explanation is.
Use the findings to propose a bounded next step. If several people describe confusion at the same point in setup, you could test clearer instructions with new users. If departures appear tied to changing needs, you might examine whether different customer groups have different reasons to stay. The goal is not to win back every participant; it is to understand which problems are within your control and make a more informed decision about them.
