Useful to read this, not so much for the solution presented, but for the description of the challenges in software development:
http://www.wired.com/2014/09/most-code- ... al_twitter
Sometimes there may feel like resistance to new ideas. However, in the long term, while it is possible to "patch in" something to create a new feature, that's seldom sustainable over the long haul. This piece has a good perspective on good code development and how a considered process works best in the end.
A considered process is not devoid of input, it just means trying to frame new ideas in a larger picture. And, ultimately, that means more stable and long lived software.
When there's a request for a new feature, there's often a followup request for other users input. This is really important to make the software as good as possible.