Not recognizing that others may have vantage points that were unknown to me was a tough lesson to learn, but an important one. It's difficult to speculate on what someone else may know or not know.
You have to see the world like them, think like them and, especially, talk like them. You have to understand their incentives in the company. Etc. If you don't make clear for them why your proposal is beneficial (to them, not to the company), then you lose.
Fair point - basic human nature - but then people need to stop saying "you (developer) don't understand the business needs or the company's needs". I understand them quite well. If "the company" continues to employ people who need constant ego stroking every 5 minutes, then they'll continue to bounce along, and I'll go sell my skills to one of their competitors who is more open to input from all levels (to the extent any of those exist in that industry!) :)
Developer suggestions were generally based on a broader view of the business' overall needs (because of the breadth of discussions we were involved in) than other people at table had, which apparently can be threatening, regardless of how you present things politically.
I realize not everyone as a developer gets in those situations. Sometimes you're chained to one project and set of people for months on end. If you're not, you can have a much better view of the business needs, but that doesn't mean anyone will listen to you as a developer. You need to move out from being perceived as such - either by changing jobs to another company, or occasionally within a company. I've never had the latter option work out for me, but have seen a couple people do that successfully.