When you say no to some things, you obviously have to think about what to say no to. It helps you prioritize and focus on the most important stuff first. Only when you've stripped down an idea to it's bare minimum can you really say that you understand it.
"Yes, there's a way to do that. No one has ever done that before, so now is the time for someone to be first..."
This sounds dangerous. What one really wants is to add stuff that will be useful to the user and will help him get things done easier. If the client proposes a feature and you say yes because "it's the time for someone to be first", then you are wasting time and effort on something that maybe isn't really necessary.
"Yes, there's a way to do that. No one has ever done that before, so now is the time for someone to be first..."
This sounds dangerous. What one really wants is to add stuff that will be useful to the user and will help him get things done easier. If the client proposes a feature and you say yes because "it's the time for someone to be first", then you are wasting time and effort on something that maybe isn't really necessary.