We shipped 12 feature requests from our loud power users. Churn went up anyway.
by•
Last quarter, we spent six weeks building custom shortcuts and advanced export filters because our most vocal users kept asking for them in Slack. When the release went live, adoption barely moved and two mid-tier accounts canceled the following month. Looking back at session replays, new signups were getting overwhelmed by the cluttered navigation before ever reaching the core workflow.
For builders balancing power-user demands against simplicity: how do you say no to vocal customers without making them feel ignored? And where did listening too closely to feedback actually hurt your product?
5 views
p/seshka
p/kodlo
p/talanoa-2
p/ai-context-flow
p/duckfightclub
p/runevr
p/producthunt
p/google-cloud-platform
p/nudgeforme
p/nexupira
p/many-displays
p/operum
p/murror
p/dino-kids
p/tabstack
p/rithub
p/any-video-to-text
p/seldon
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.