{"id":269023,"date":"2025-04-25T07:24:37","date_gmt":"2025-04-25T07:24:37","guid":{"rendered":"https:\/\/userpilot.com\/blog\/?post_type=pitt&p=269023"},"modified":"2025-06-11T12:04:31","modified_gmt":"2025-06-11T12:04:31","slug":"difficult-but-not-frustrating-the-art-of-cancelling-a-product","status":"publish","type":"pitt","link":"https:\/\/userpilot.com\/blog\/pitt\/difficult-but-not-frustrating-the-art-of-cancelling-a-product\/","title":{"rendered":"Difficult but Not Frustrating: The Art of Cancelling a Product"},"content":{"rendered":"

Let\u2019s get straight to the question that product managers ask themselves quietly but rarely admit out loud: Should I make it hard to cancel my product?<\/span><\/p>\n

On the surface, the answer seems obvious. No one wants to be ‘that’<\/span> company. Who would like to be famous for hiding the “cancel subscription” button, asking for a fax (yes, still happens), or looping you into a never-ending maze of confirmation screens?<\/span><\/p>\n

But once you start to think about it, the real question becomes more interesting: Is there a way to slow down <\/span>cancellation<\/span><\/a> ethically without damaging the relationship?<\/span><\/p>\n

And the answer to that is yes! As long as you\u2019re focused on clarity, not confusion, value, and not resistance, it is fair game to put a few stopgaps in place.<\/span><\/p>\n

Because sometimes, what looks like a user on their way out is a dissatisfied customer.<\/span><\/p>\n

As a <\/span>product manager<\/span><\/a>, it\u2019s also your job to make offboarding as thoughtful and intentional as the onboarding. Just because someone is leaving doesn\u2019t mean you have no product to offer them anymore. Let\u2019s look into some tactics you can use to <\/span>prevent churn<\/span><\/a>.<\/span><\/p>\n

1. Adding value to the exit path<\/strong><\/h2>\n

Instead of treating the cancel button like an opening to a bridge-burning scene, treat it as a final opportunity to engage the user in a helpful way. If done right, this doesn\u2019t delay their exit unnecessarily and instead adds context, alternatives, and sometimes a reason to stay.\u00a0<\/span><\/p>\n

A clear example of this is Basecamp, which offers a very clear two-step cancellation process that offers to export your data on your way out. This is the product being helpful and user-focused, even when the user is on their way out. This is an excellent example of showing empathy and providing value at the last second.<\/span><\/p>\n

<\/p>\n

 <\/p>\n

Another example is Adobe Creative Cloud. As a user begins the cancellation process, Adobe often presents a few tailored offers. It could be a 60-day discount, a temporary pause, or an alternative plan.<\/span><\/p>\n

<\/p>\n

 <\/p>\n

Though I present this as a positive example, I do need to stress that the only viable angle for this is when you look at this step out of context. Adobe actually has a <\/span>4-step cancellation process<\/span><\/a> that includes:<\/span><\/p>\n

    \n
  1. Review of the benefits being lost.<\/span><\/li>\n
  2. Providing a reason for cancellation.<\/span><\/li>\n
  3. Offering you a last-second offer.<\/span><\/li>\n
  4. Cancellation summary screen.<\/span><\/li>\n<\/ol>\n

    Oh boy, they do ask a lot for their products and really don\u2019t want to see you go, don\u2019t they? They are actually guilty of several \u201ccancellation product sins\u201d, so I will recall their process again later in the article.<\/span><\/p>\n

    \n

    Another way you can add value to the exit path in-app is by creating contextual cancellation experiences.<\/span><\/p>\n

    For example, if a user indicates they’re leaving because they found the product difficult to use, <\/span>Userpilot <\/span><\/a>can automatically trigger a specialized off-boarding flow that offers a quick tutorial video or connects them with customer success. If pricing is the concern, it can present a tailored discount or alternative plan.<\/span><\/p>\n<\/div>\n

    2. Asking for feedback but not demanding it<\/strong><\/h2>\n

    Exit surveys<\/span><\/a> can be immensely helpful, but only if they are truly optional and truly short. Netflix provides a nice example here:<\/span><\/p>\n

    <\/p>\n

    After confirming the cancellation, users are presented with a short list of common reasons for leaving.\u00a0<\/span><\/p>\n

    It\u2019s skippable. It\u2019s fast. And it\u2019s just enough for the team behind the scenes to gather some valuable insight.\u00a0<\/span><\/p>\n

    What is great, unlike Adobe\u2019s similar survey in the same flow, is that this doesn\u2019t pop up until you actually cancel. For Netflix, it\u2019s a one-step process, and the survey at the end of it is as invasive as possible.<\/span><\/p>\n

    The lesson here is simple. If your goal is to learn, don\u2019t make the users feel like they\u2019re taking a final exam. If they want to speak, they will. If not, let them go in peace. It\u2019s ok to ask for data; it\u2019s not OK to pretend to ask for it and try to do whatever is possible to keep the user subscribed.<\/span><\/p>\n

    With <\/span>Userpilot<\/span><\/a>, you can create and customize churn surveys completely code-free, allowing product teams to quickly implement sophisticated exit paths without engineering resources. This makes it easy to iterate and optimize your cancellation flow based on real user feedback.<\/span><\/div>\n
    <\/div>\n
    \n
    \n
    \n\"Stepstone<\/p>\n

    Learn More from the Interview with Bart<\/h3>\n

    Sign Up for the Interview<\/a>\n<\/div>\n

    \"Speaker<\/div>\n<\/div>\n<\/div>\n

    3. Offer support without gatekeeping<\/strong><\/h2>\n

    Sometimes, users cancel not because they\u2019re unhappy with your product but because something broke along the way, i.e., a billing issue, a misunderstood feature, or a simple annoyance. In such cases, a human conversation with a competent support agent can almost magically turn things around.<\/span><\/p>\n

    You can see this in Adobe\u2019s example above, though again, it\u2019s only good when you ignore the 4-step process that utilizes every \u201cethical\u201d play in the book, but makes it annoying due to the number of hoops to jump through.<\/span><\/p>\n

    Another poor implementation of this philosophy is demonstrated by a product called ConvertKit. There, you have no UI option to cancel the product, but it\u2019s super easy once you request it via chat.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\n

    \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/p>\n

    This sort of organically puts you on a path for the support agent to get to understand your motivation. If I were a PM there, I would keep it the same, but still leave an easy-to-find cancellation option. Clicking the button would simply summon the chat and automatically start the right conversation topic.\u00a0\u00a0<\/span><\/p>\n

    However, that is the furthest I believe one should go. Beware of going further than that. Forcing a phone call or hiding behind support tickets just to wear people down is not the same thing. The difference is whether the user still feels like they\u2019re in control of their decision.<\/span><\/p>\n

    4. Avoid patterns that breed resentment<\/strong><\/h2>\n

    Some patterns are universally hated, as they don\u2019t provide value or clarity, and simply provoke <\/span>frustration<\/span><\/a>. They are built to keep as many users paying as possible, no matter the ethics. Examples of such UI patterns include:<\/span><\/p>\n