How is your documentation and writing? Rarely have I seen corporate software teams get this even remotely competent. Its generally so bad, in fact, that in my prior organizations they deferred almost all technical writing to QA personnel and product owners, because they couldn't trust the developers or the technical leadership to produce anything intelligible.
Here is a brief checklist of things to focus on communicating value:
* Purpose - What would ya say you do here?
* Measures - How do you measure success in numbers?
* Product Goals - What are the very specific and quantifiable goals of the current project/product?
* Product/Development Alignment - What is your approach to align the work to the business? Be short and specific. Don't say Agile or any jargon bullshit.
* Personnel Alignment - How many people do you need doing which jobs and how do you justify that in hours and dollars? This should be driven by the business requirements and not some developer's bullshit technical requirements.
The reason these things are important is that the higher your rise the further you move away from the granularity of the actual work. You need to clearly understand business organization and how to organize teams opposed to individual developers. Developers are just resources (numbers) and a collection of those resources are a team, but those resources are interchangeable because what is most important is shipping a product and penetrating a market.