Member-only story
Users Ask for Features. They’re Really Describing Problems They Can’t Name.
Every feature request is a workaround in disguise. The real work is reading backward to the pain underneath.
The request came in on a Tuesday, logged by a customer success manager who had just gotten off a call with one of our largest accounts. It read, simply, “Add a button to export the full report to Excel.”
It was the kind of request that feels easy. Concrete. Bounded. A button. An export. A spreadsheet. You can almost see the ticket writing itself. The account was worth a lot of money, the request had a name attached to it, and the person who sent it was polite about it. So we built it. Two sprints, a small team, a new export option in the report menu. We shipped it on a Friday and felt good about being responsive.
Then the customer success manager followed up three weeks later. The account had barely used the export. The person who asked for it had used it twice, looked at the spreadsheet, and gone back to the old workflow. The churn risk had not changed. The relationship had not improved. We had delivered exactly what was asked for, and it had done almost nothing.
I sat with that failure for a while, and eventually I went back and actually talked to the person who had made the request. Not through a survey. A real conversation. And what came out was not “I needed an Excel file.” It was “I do not trust the numbers in your dashboard, so I pull them into a spreadsheet and recheck them by hand before I…
