Madison Marley

We spent almost three months building and maintaining a feature that 40% of our free users asked for. But when we looked at the data, that exact feature was causing 60% of our support tickets and confusing high-paying customers.

Last month, we ripped it out completely. We lost a few vocal free users, but our main product speed improved, support volume plummeted, and paid upgrades went up.

Have you ever sunsetted a popular feature to save your main core value proposition?

When we first launched, we built a comprehensive onboarding flow to capture every detail. But our trial drop-off rate was brutal.

Watching user session recordings made us realize that people weren't leaving because they lacked interest they were giving up because we asked for 10 minutes of configuration before showing a single outcome. They wanted immediate relief, not an admin task.

For founders managing products with heavy initial setup: how do you deliver that first aha moment before requiring full integration?

I want to share something counterintuitive that took me two years to figure out.

Like most founders, I was obsessed with user happiness. Did they like the product? Were they satisfied? Did they leave a good review? I'd send NPS surveys, add "how are you feeling?" prompts, respond to every bit of feedback with gratitude.

But churn stayed stubbornly high. People weren't unhappy they just weren't using the product. They'd sign up, poke around, and drift away.

Then I accidentally noticed something. The users who stuck around weren't the ones who said they loved the product. They were the ones who had figured out the one specific thing the product was actually good at. They weren't confused anymore. They had clicked with the core value.