When you’re building an app to scratch an itch, it’s easy to design and launch new features and tools that you need. But once you starting gaining customers, they’re going to have their own set of needs that hopefully your app can fulfill. Most will be along the lines of the same itch that you’re scratching but sometimes they’re unique.
Enter the feature request.
I’ve talked about how to handle those emails to a customer here. This time, let’s talk about what to do with them.
Keep a list of the most common ones someplace your team can see it. For us at 37signals, we pick three of the most common requests / pain points from our customers and put them in a project. We include links to cases from customers, examples of what they’re saying, and even screenshots. Anything to give the rest of the team a clear picture.
From there, we do a quick demo of each of those at the company meetup. Everyone is in the same room so it’s a prime opportunity to talk about how to fix them.
We also include info on those top three in our weekly heartbeats to the rest of the team. That way, it stays on everyone’s radar the entire time.
You’ve got to keep them in sight.
That’s the biggest thing. You can use boards, lists, or even a dancing cat that announces the top ones. You’ve just got to keep them in sight for the rest of the team to see.
What ways do you make sure the top customer feature requests stay in sight?