What your "most senior" engineers work on, how well they communicate about it, and what visible expectations there are of them is such a crystal clear window in to your org's values
Values aren't made by mission statements - they're written in the sweat and mayhem of what _actually happens_. Trust is built based on proven track records, not leaps of faith.
I think this is one of the things that makes me so happy about the team I'm on - we _build_ trust, we iteratively focus our values, and it WORKS
My team's values aren't the same as other teams - by definition! We are different groups of people, who have been working on different things, and have built different relationships! This is OK, and good!
But it means that if you're someone in a position of power in an org, you need to be thinking of how what you say fits in to all those local value systems.
If the broader org has itself built a track record to be trusted in, and demonstrated its values over time, then the values of individual teams are likely to overlap a ton - that makes communication / kicking ass easier
But if you're _building_ that, you have a responsibility to be hyper-vigilant of implications, of different sets of values, of what is implied by what you say. You need to over-communicate how you see things evolving. You need to respect the value systems with more trust than you
Which is wicked hard! But it's the only way to establish that track record, make your mark in the org history, become a butt-kicking machine
