Should you promise to deliver a feature that you aren't sure if its implementable?

Posted by user476 on Programmers See other posts from Programmers or by user476
Published on 2012-10-08T19:16:47Z Indexed on 2012/10/08 21:49 UTC
Read the original article Hit count: 141

Filed under:

In an article from HN, I came across the following advice:

Always tell your customer/user "yes", even if you're not sure. 90% of the time, you'll find a way to do it. 10% of the time, you'll go back and apologize. Small price to pay for major personal growth

But I've always thought that one should do a feasibility analysis before making any kind of promises to a customer/user, so that they aren't misled at any point. At what circumstances, then, should the above advice applicable?

© Programmers or respective owner

Related posts about programming-practices