Requested features didn’t fix churn. First 10 minutes did.
by•
When paid users churned, our default reaction was: "They need feature X." So we rushed it onto the roadmap.
But looking at exit interviews, the problem wasn't what the product could do it was how hard it was to figure out where to start in an existing workday. They didn't leave because of missing functionality: they left because fitting us into their routine felt like a chore.
How do you structurally separate a "missing feature" complaint from a "workflow friction" complaint before bloating your product?
2 views
Replies
One check I use is whether the tools people already know do it. I'd planned the kanban and Gantt views in my board tool as separate screens, and when a user asked to switch between them, I found Notion and Asana both had that switch, so I added it the same day. If the familiar tools already work that way, it's usually how people expect to work, not just a missing feature.