5 ms·

It's remarkable that he was able to quantify the demand for his feature: "at the time of writing only 32 out of 26,000+ requests [was for turning off Read Recei

It's remarkable that he was able to quantify the demand for his feature: "at the time of writing only 32 out of 26,000+ requests [was for turning off Read Receipts]". There's a lot of Superhuman skepticism in the comments, but their CEO owned the decision and responded quickly. If you assume good intent, it's remarkable in its comprehensiveness, transparency, and speed. If you don't, well, you probably wouldn't be satisfied by anything other than ripping the feature out. Which wouldn't make sense for the business given the demand from its primary customer segment.

vageli 7y ago
> It's remarkable that he was able to quantify the demand for his feature: "at the time of writing only 32 out of 26,000+ requests [was for turning off Read Receipts]". A company managing customer feature requests is suddenly remarkable? For a tool aimed at professionals? I would take that as par for the course.
- kareemm 7y ago
  It's remarkable to track 26k requests. That's non-trivial. Especially with the ability to drill down to a single feature request. I know this is non-trivial because I run a business that helps product teams do this. I talk to PMs at companies you've heard of and probably use that struggle with this.
  - gnicholas 7y ago
    I don't know what tool they use to get user feedback, but it would be trivial for me to find out how many user requests we've gotten for a feature like read receipts: just do a search for "read receipts" in our contact email inbox. Might it miss some requests that didn't have the exact phrase? Yes, but it's in the CEO's interest to have a count that is very low, since he's trying to say that their users haven't asked about this much. So it might be hard to get an exact count of how many people asked for some feature (particularly if it doesn't have an agreed-upon name, like "read receipts", but if you're just looking for one phrase and don't mind erring on the low side, this should be a pretty easy exercise.
    - kareemm 7y ago
      Or on the high side: “read receipts are awesome!” I think my broader point stands: given their 26k requests (which you can’t figure out using your method) it’s impressive to know that N of them are for Y feature.

vageli 7y ago

> It's remarkable that he was able to quantify the demand for his feature: "at the time of writing only 32 out of 26,000+ requests [was for turning off Read Receipts]". A company managing customer feature requests is suddenly remarkable? For a tool aimed at professionals? I would take that as par for the course.

kareemm 7y ago
It's remarkable to track 26k requests. That's non-trivial. Especially with the ability to drill down to a single feature request. I know this is non-trivial because I run a business that helps product teams do this. I talk to PMs at companies you've heard of and probably use that struggle with this.
- gnicholas 7y ago
  I don't know what tool they use to get user feedback, but it would be trivial for me to find out how many user requests we've gotten for a feature like read receipts: just do a search for "read receipts" in our contact email inbox. Might it miss some requests that didn't have the exact phrase? Yes, but it's in the CEO's interest to have a count that is very low, since he's trying to say that their users haven't asked about this much. So it might be hard to get an exact count of how many people asked for some feature (particularly if it doesn't have an agreed-upon name, like "read receipts", but if you're just looking for one phrase and don't mind erring on the low side, this should be a pretty easy exercise.
  - kareemm 7y ago
    Or on the high side: “read receipts are awesome!” I think my broader point stands: given their 26k requests (which you can’t figure out using your method) it’s impressive to know that N of them are for Y feature.