Where then does the "learn to say 'no!'" attitude comes in if we are to say "yes, if..." to every idea coming our way? How to find the right balance between being a "can do" person, and NOT being the over-committer?
- Don't say no to clients "crazy" demands, just calculate what it would actually cost, or what you would need to do what they ask, and quote them that.
- A good price is when you are OK either way: You're OK if they say yes, and OK if they say no.
Edit: typos, missing word
these "no because," people are a common resistance to new ideas. In engineers, they're almost the default. It's much easier to say no; to say yes is to deal with an increasingly larger amount of resistance. However, that resistance is also what makes the idea go far.
Technically my answer was more "yes if we dump some other pieces of software, and we try to be the best player at this new idea".