Because of the Ukraine conflict, the phrase "mission command" came to my attention. It's about C2 rather than leadership but another one of those gems we might filter out in our "Bay Area" (you're all terminally online Europeans / teenagers jk) bubble.
The idea of mission command is pretty simple. If you see an incidental opportunity that will contribute to the big picture and pursuing it won't compromise the objective of your orders, take it. IIRC they call it something like "scoped initiative."
If you see an incidental opportunity that you can't take because it would compromise your local objective, you escalate. Up the chain, in the larger scope, that incidental opportunity that would compromise the objective of the smaller unit may be addressable using some available resources of the bigger unit.
It works by deduction and beautifully because you get the best of both individual initiative and large-scale coordination. It's an example where from-first-principle CS and pragmatic emergent systems resonate because it's near a morally true optimum.
In the context of OP, knowing the objective of your larger 1-2 organization levels is all the transparency that is every necessary. Neurons aren't smart. Information flows in a network are smart. Don't trust people who start performing and asking for transparency because ninety-nine times out of ten, they can't do better with what they ask for but will make everyone else do worse by breaking the cohesion.
And finally I read OP. It's a vapid feel-good long-form tweet that is nothing compared to the comment section.