How to sail the Open Source boat in Rough Seas of Corporate world

Even though Open Source is amazing for any organisation that consumes software, not everyone would agree. Legal may ring alarms for code that is licensed under a copyleft license, Corporate Relations may see Open Source engagement as ineffective and lastly project teams merely wants to consume or contribute code without worrying about anything else.

Navigating all of the above while adhering to planned timelines can be challenging, It is important to understand that not every function will share the same enthusiasm and may come with a different approach or perspective.

How can OSPO members sail through this, do they have to build a narrative based on respective functions or do they have to back the narrative with data or a top down push from executives is the only way to sail through?