3 ms·
If you were to hypothetically say "We're killing X" and that didn't cause a nightmare for support, I'd take that as an extremely strong bit of signal regarding
by patio11 15y ago
If you were to hypothetically say "We're killing X" and that didn't cause a nightmare for support, I'd take that as an extremely strong bit of signal regarding how important X and X-like things were. By the same token, words like "This feature seems to me so important that I don't think we can live without it" (direct quote from customer!) are solid gold for directing future priorities. Dave McClure suggested pre-emptively killing a feature every week just to elicit responses like that. That seems both a) valuable and b) cheap to do, since saying that X is on the chopping block is essentially free. Heck, you could wire up an A/B test with a "Got a problem?" button right next to it, and it wouldn't take you more than ~5 minutes.
If you're building a time tracking software and your customers are using it to do project management... you might be in the wrong business. Something to think about.
It is, of course, possible that folks paying you $12 a month get very attached to one particular thing. $12 a month does not buy you a whole lot of development priority, to put it mildly. It is occasionally necessary to tell them "Nope, sorry, it appears that we're not the best fit for your needs."
- PotatoEngineer 15y agoSo if I'm using that app, I'd have to check the developer blog, or some "news" section, every week just to see if one of my favorite features might get axed? It sounds like a really annoying thing for a user.
- jellicle 15y agoI think the parent comment is suggesting something like, in a new version of the software, doing this: -- remove the button for the feature, replace it with a "Give me back my feature!" button -- when the "give me back my feature!" button is clicked, send a GET request to mydomain.com/theywantedthefeatureback.php , and give them back the feature button -- look at your server logs to determine whether anyone actually uses the feature This is no big hassle for the developer or the user and it will tell you rather quickly whether anyone actually uses feature X.