10 ms·

Feature addiction is real. This post points to perverse economic incentives as being one possible cause, but I have also seen this happen in open-source projec

Feature addiction is real. This post points to perverse economic incentives as being one possible cause, but I have also seen this happen in open-source projects. It's a matter of listening to the wrong people, in my view. User feedback is incredibly valuable, but when user feedback comes in the form of GitHub issues rather than careful testing and conversation, the team will inevitably find themselves building more and more and more for no real benefit. I've quoted this before, but what Don Norman says in The Invisible Computer still applies: "Don’t ask people what they want. Watch them and figure out their needs. If you ask, people usually focus on what they have and ask for it to be better: cheaper, faster, smaller. A good observer might discover that the task is unnecessary, that it is possible to restructure things or provide a new technology that eliminates the painstaking parts of their procedures. If you just follow what people ask for, you could end up making their lives even more complicated."

Alex3917 7y ago
Most times when users say they won't use a product because it's missing a feature: - Those specific users won't use it anyway even if you add it - The problem they identified is a legitimate problem that was preventing other people from using it - Whether your metrics actually go up depends on where that feature was in the critical path of your funnel. All else being equal, fixing legitimate problems with your product is unlikely to move your metrics much, because most (randomly distributed) problems aren't at the frontier of the critical path. It's a mistake to think that adding features that customers ask for will immediately improve your core metrics, but it's also a mistake to think that features that don't visibly improve your core metrics were a mistake to add.
- cgriswald 7y ago
  > Those specific users won't use it anyway even if you add it I think people read this and think, "Why bother, then?" As someone who is often this user, I don't end up using your product because I've already moved onto a competing product or service; or because I never hear that you have added the feature. Whether your metrics move after adding the feature might be a matter of timing. There's also the chance I will come to your product in the future. Hypothetically, let's say you offer a password vault application, but I dislike it because it lacks a feature I want, so I end up going with your competitor who offers the feature. You add the feature, but I don't switch because I'm now content with your competitor. Later, your competitor starts pushing towards a subscription model while simultaneously showing a real lack of professionalism and social grace towards customers in public. Since you've added the feature that I thought was lacking, your product might now be an option for me. If you haven't added the feature, there's still no chance.
  - deleted 7y ago
    [deleted]
  - dennisgorelik 7y ago
    > competitor starts ... showing a real lack of professionalism Betting on eventual competitor's incompetence in the future - is not a reliable strategy. In such situation it may be better to implement that feature only when entrenched competitor with that feature will start pushing their customers away.
- kube-system 7y ago
  This situation is further complicated when you’re making enterprise software where the purchaser often isn’t a user and the majority of the users don’t have a say in the purchasing decision. A smart purchaser will define their purchasing criteria based on the needs of their users, but in practice, I’ve found that some haven’t done an accurate job of determining their users needs, and/or inject their own agendas into the requirements.
- hrktb 7y ago
  > Those specific users won't use it anyway even if you add it These users often understand what features are missing because they rely on them in other products. At that point your product is already dead to them.
- jyrkesh 7y ago
  Some of the best advice I've been given on this is to look at how the potential customer is already solving the problem today. If they're just ignoring the problem altogether, then they're not going to spend any money on you to solve it. If they're spending considerable time and/or money working around or manually solving the problem (maybe by working weekends, or buying a whole team of vendors, or outsourcing to Mechanical Turk type stuff), and you can solve the problem for them for less money and/or time, then it's a feature worth shipping. It can give false negatives, especially with future looking and platform-type work, but it's a great heuristic for weeding out useless feature work
DelightOne 7y ago
The problem is that there's only one list for everything. Allow owners to create differing lists and this would not be so.
ReptileMan 7y ago
I really liked Blizzard of Ghostcrawler era - he plainly stated that they listen to users carefully to identify problems, but do not listen to them carefully about the proposed solutions. And well - his design team got stuff mostly right.
gherkinnn 7y ago
Having watched recordings of people using our product and spent too much time reading their reviews and feature requests, I can safely say that neither does the average user know what he wants or needs, nor can he articulate what the current problems or improvements are. It gets worse when you have a specialist of a given field consulting you on how to build software with his field in mind. “A fish doesn’t think of water” is a fitting quote I once heard. All you can do is observe, tweak and test.
Reedx 7y ago
A useful metaphor we use in game dev: Players are the patient, you are the doctor. They're great at finding pain, but not at knowing how to heal it. It's on you to figure out what the underlying problem is and how to solve it. Also, some of my favorite quotes on this subject: You listen to all your fans and they always say "You should add this" or "You should add that." They never say "Take this out, take that out." They say "add more, add more!" There's an old saying that I love about design, it's about Japanese gardening actually, that "Your garden is not complete until there is nothing else that you can remove." I think a lot of designers think the opposite way - "What else can we add to the game to make it better?" -Will Wright "People don’t know what they want until you show it to them.” -Steve Jobs "Writers and people who had command of words were respected and feared as people who manipulated magic. In latter times I think that artists and writers have allowed themselves to be sold down the river. They have accepted the prevailing belief that art and writing are merely forms of entertainment. They’re not seen as transformative forces that can change a human being; that can change a society. They are seen as simple entertainment; things with which we can fill 20 minutes, half an hour, while we’re waiting to die. It’s not the job of the artist to give the audience what the audience wants. If the audience knew what they needed, then they wouldn’t be the audience. They would be the artists. It is the job of artists to give the audience what they need." -Alan Moore
- joshspankit 7y ago
  I’m not saying this to argue against your points: I’m a fan of Tangerine bank and have been continually and loudly telling them to remove the balances on the account overview screen as it now triggers “burning a hole in my pocket” psychology. I only mean to say at least a few fans are actively asking for things to be removed, simplified, and (thoughtfully) refined.
  - nicksergeant 7y ago
    You're asking a bank to remove visible account balances from a dashboard view?
    - sbr464 7y ago
capex 7y ago
Designing user research around watching people do something, and figuring out their needs is something I've covered in a recent post: https://adnankhan.space/user-research/2020/01/28/ask-users-for-their-problems-not-solutions-or-opinions.html https://adnankhan.space/user-research/2020/01/28/ask-users-f.... The idea is that your research objectives could be very different from what you're actually testing.
snthd 7y ago
Sounds like the XY problem https://en.wikipedia.org/wiki/XY_problem https://en.wikipedia.org/wiki/XY_problem
trickstra 7y ago
Henry Ford: "If I had asked people what they wanted, they would have said faster horses." (probably misattributed, but fitting nonetheless)
mikulabc 7y ago
I think if we look at Excel, we see that additional features were welcomed and it became very big, same with Word, but then we look at today's google docs and spreadsheet from google and wonder where all that stuff went, but we adapt and now i am fine with simplicity

Alex3917 7y ago

Most times when users say they won't use a product because it's missing a feature: - Those specific users won't use it anyway even if you add it - The problem they identified is a legitimate problem that was preventing other people from using it - Whether your metrics actually go up depends on where that feature was in the critical path of your funnel. All else being equal, fixing legitimate problems with your product is unlikely to move your metrics much, because most (randomly distributed) problems aren't at the frontier of the critical path. It's a mistake to think that adding features that customers ask for will immediately improve your core metrics, but it's also a mistake to think that features that don't visibly improve your core metrics were a mistake to add.

cgriswald 7y ago
> Those specific users won't use it anyway even if you add it I think people read this and think, "Why bother, then?" As someone who is often this user, I don't end up using your product because I've already moved onto a competing product or service; or because I never hear that you have added the feature. Whether your metrics move after adding the feature might be a matter of timing. There's also the chance I will come to your product in the future. Hypothetically, let's say you offer a password vault application, but I dislike it because it lacks a feature I want, so I end up going with your competitor who offers the feature. You add the feature, but I don't switch because I'm now content with your competitor. Later, your competitor starts pushing towards a subscription model while simultaneously showing a real lack of professionalism and social grace towards customers in public. Since you've added the feature that I thought was lacking, your product might now be an option for me. If you haven't added the feature, there's still no chance.
- deleted 7y ago
  [deleted]
- dennisgorelik 7y ago
  > competitor starts ... showing a real lack of professionalism Betting on eventual competitor's incompetence in the future - is not a reliable strategy. In such situation it may be better to implement that feature only when entrenched competitor with that feature will start pushing their customers away.
kube-system 7y ago
This situation is further complicated when you’re making enterprise software where the purchaser often isn’t a user and the majority of the users don’t have a say in the purchasing decision. A smart purchaser will define their purchasing criteria based on the needs of their users, but in practice, I’ve found that some haven’t done an accurate job of determining their users needs, and/or inject their own agendas into the requirements.
hrktb 7y ago
> Those specific users won't use it anyway even if you add it These users often understand what features are missing because they rely on them in other products. At that point your product is already dead to them.
jyrkesh 7y ago
Some of the best advice I've been given on this is to look at how the potential customer is already solving the problem today. If they're just ignoring the problem altogether, then they're not going to spend any money on you to solve it. If they're spending considerable time and/or money working around or manually solving the problem (maybe by working weekends, or buying a whole team of vendors, or outsourcing to Mechanical Turk type stuff), and you can solve the problem for them for less money and/or time, then it's a feature worth shipping. It can give false negatives, especially with future looking and platform-type work, but it's a great heuristic for weeding out useless feature work

DelightOne 7y ago

The problem is that there's only one list for everything. Allow owners to create differing lists and this would not be so.

ReptileMan 7y ago

I really liked Blizzard of Ghostcrawler era - he plainly stated that they listen to users carefully to identify problems, but do not listen to them carefully about the proposed solutions. And well - his design team got stuff mostly right.

gherkinnn 7y ago

Having watched recordings of people using our product and spent too much time reading their reviews and feature requests, I can safely say that neither does the average user know what he wants or needs, nor can he articulate what the current problems or improvements are. It gets worse when you have a specialist of a given field consulting you on how to build software with his field in mind. “A fish doesn’t think of water” is a fitting quote I once heard. All you can do is observe, tweak and test.

Reedx 7y ago

A useful metaphor we use in game dev: Players are the patient, you are the doctor. They're great at finding pain, but not at knowing how to heal it. It's on you to figure out what the underlying problem is and how to solve it. Also, some of my favorite quotes on this subject: You listen to all your fans and they always say "You should add this" or "You should add that." They never say "Take this out, take that out." They say "add more, add more!" There's an old saying that I love about design, it's about Japanese gardening actually, that "Your garden is not complete until there is nothing else that you can remove." I think a lot of designers think the opposite way - "What else can we add to the game to make it better?" -Will Wright "People don’t know what they want until you show it to them.” -Steve Jobs "Writers and people who had command of words were respected and feared as people who manipulated magic. In latter times I think that artists and writers have allowed themselves to be sold down the river. They have accepted the prevailing belief that art and writing are merely forms of entertainment. They’re not seen as transformative forces that can change a human being; that can change a society. They are seen as simple entertainment; things with which we can fill 20 minutes, half an hour, while we’re waiting to die. It’s not the job of the artist to give the audience what the audience wants. If the audience knew what they needed, then they wouldn’t be the audience. They would be the artists. It is the job of artists to give the audience what they need." -Alan Moore

joshspankit 7y ago
I’m not saying this to argue against your points: I’m a fan of Tangerine bank and have been continually and loudly telling them to remove the balances on the account overview screen as it now triggers “burning a hole in my pocket” psychology. I only mean to say at least a few fans are actively asking for things to be removed, simplified, and (thoughtfully) refined.
- nicksergeant 7y ago
  You're asking a bank to remove visible account balances from a dashboard view?
  - sbr464 7y ago

capex 7y ago

Designing user research around watching people do something, and figuring out their needs is something I've covered in a recent post: https://adnankhan.space/user-research/2020/01/28/ask-users-for-their-problems-not-solutions-or-opinions.html https://adnankhan.space/user-research/2020/01/28/ask-users-f.... The idea is that your research objectives could be very different from what you're actually testing.

snthd 7y ago

Sounds like the XY problem https://en.wikipedia.org/wiki/XY_problem https://en.wikipedia.org/wiki/XY_problem

trickstra 7y ago

Henry Ford: "If I had asked people what they wanted, they would have said faster horses." (probably misattributed, but fitting nonetheless)

mikulabc 7y ago

I think if we look at Excel, we see that additional features were welcomed and it became very big, same with Word, but then we look at today's google docs and spreadsheet from google and wonder where all that stuff went, but we adapt and now i am fine with simplicity