> Difficulty of implementation should never be a deciding factor in whether or not to address the needs of the users.

Really?

Never ?

I've got to disagree with this.

All possible changes that one might make to a codebase should be evaluated in terms or ROI (return on investment).

If a 1 day project creates X value, and a 3 day project creates 5 X value, then the latter project delivers more bang for the buck, and that's where resources should be allocated.

To ignore the amount of work that a task takes is to blind oneself and discard rationality.