As a developer, I have built many features. I wouldn’t say all, but many of them were a waste of everyones time. These features were usually built because the product group told us to build them. I found product teams make these decisions based upon some customer interviews, email feedbacks, phone complains and mostly their “gut”. And its hurts the most when we would bust our asses building and releasing it, to only realize that our customers are not using it. Reasons vary from customers wanting X and we building Y to the user flow not being right. Its further disappointing to learn after a release that customers didn’t even care enough to click on the feature i built, forget about using it.<p>Prioritizing what to build, which features to double down on and which ones to ignore, what to prototype and what to scrap etc. are all important questions which the product team needs to decide. In their defense I feel like these are difficult questions. To me its just that I don't think they can afford to get this wrong. Building the wrong features, maintaining them and then eventually killing them is very expensive and just a moral killer.<p>The question in my mind is can product teams make better product decisions? Why do we have to ask developers to build things, release it and then learn whether customers really wanted it. To address this issue and empower product teams I have built www.featureKicker.com. It enables teams to deploy features before building them, collect feedback, analyze data and make better, more informed, data backed decisions. It enables a product manager to look a developer in his or her eye and say “I need you to build X and I need it done by Y. I have Z number of customers waiting for it. Here you can read what they have to say”.<p>I would love to hear from the community of what they think of this solution. I want to help companies make better product decisions and am looking at the community for guidance.<p>Sandeep
CTO
FeatureKicker.com