4 ms·

Feature requests are really prone to this. Customers will only ask for features they can imagine, not the ones that really solve their problem. A significant ch

by Joeri 11y ago

Feature requests are really prone to this. Customers will only ask for features they can imagine, not the ones that really solve their problem. A significant chunk of the time the customer is better served by a different feature that takes less work. This is why i don't like tender-based software projects. The tender already describes the features needed, and they must be built even if they are suboptimal for the problem domain.

csours 11y ago
One of our Business Partners suggested a pop up box with Yes No Cancel, and then went on to describe the behaviors of each button. Absolutely no imagination. It's like people have been broken by years of limited choices.
- sopooneo 11y ago
  With some types of people, I've just stopped trying to get them to back up and describe the underlying pain point they are trying to relieve. Because as far as I can tell, some people just can not do that. Instead, I let them describe their implementation and listen/ask/listen/ask/listen to understand what they're actually trying to fix. And then once we have the problem figured out, we as a dev/design team go back and work forward again to design a proposed solution. And then we present that. Often enough, they're happy to accept it. The trick is that some egomaniacs just get fixated on their own proposed solution, and won't let go. And then you just give them their Homermobile: http://www.wired.com/wp-content/uploads/2014/06/the-homer-inline4.jpg http://www.wired.com/wp-content/uploads/2014/06/the-homer-in...
the4dpatrick 11y ago
Could you give an example of what you mean by "tender-based software projects"?
- tamana 11y ago
  The client writes spec and solicits a bid, instead of soliciting design partners.
hinkley 11y ago
If I had a dollar for every time a customer finally confessed that they actually wanted a different feature but thought it would be too expensive... Nothing like blowing $40,000 on a $1000 feature.

by Joeri 11y ago

csours 11y ago

One of our Business Partners suggested a pop up box with Yes No Cancel, and then went on to describe the behaviors of each button. Absolutely no imagination. It's like people have been broken by years of limited choices.

sopooneo 11y ago
With some types of people, I've just stopped trying to get them to back up and describe the underlying pain point they are trying to relieve. Because as far as I can tell, some people just can not do that. Instead, I let them describe their implementation and listen/ask/listen/ask/listen to understand what they're actually trying to fix. And then once we have the problem figured out, we as a dev/design team go back and work forward again to design a proposed solution. And then we present that. Often enough, they're happy to accept it. The trick is that some egomaniacs just get fixated on their own proposed solution, and won't let go. And then you just give them their Homermobile: http://www.wired.com/wp-content/uploads/2014/06/the-homer-inline4.jpg http://www.wired.com/wp-content/uploads/2014/06/the-homer-in...

the4dpatrick 11y ago

Could you give an example of what you mean by "tender-based software projects"?

tamana 11y ago
The client writes spec and solicits a bid, instead of soliciting design partners.

hinkley 11y ago

If I had a dollar for every time a customer finally confessed that they actually wanted a different feature but thought it would be too expensive... Nothing like blowing $40,000 on a $1000 feature.