I empathise that it can be tough when Development is seen as the most important link in the chain. I used to think this way too (I started my career as a developer).
My own watershed moment came years ago when I asked a respected interaction designer to explain to me what his view of "best practice" involved. He pretty much spelled out the UX process that we champion to readers of UX Mastery. It stunned me that not only did "Development" not get a mention, but that it was just a small part of one of the "Production" stage. Who would have thought that there was so much effort being put into the earlier strategising, thinking, researching, validating, testing, idea generation, prototyping, designing, testing activities? It was a real eye-opener.
I mention this to back up Fox's comment that articulating the "big picture" process that other organisations are using, and are widely considered best-practice, can be a powerful catalyst for change. And I agree that having that message delivered by someone who possesses both authority and charisma certainly doesn't hurt!