On the other hand, I'd never want a "what should I do?" person as an early startup hire.
I have never seen transparency hurt the productivity of these employees. They know they can look and see the big picture any time, they just don’t bother to look:
But for some people "transparency" also means a more active communication of this information, and this definitely confuses some (other) people because they will consistently interpret "we want to do X" or "we are going to do X" as "I should, right now, do (sub-part of) X".
This doesn't apply to tanks or healers, only dps. Playing tank as an infra person I would do my team a disservice if I didn't make myself available on a dime to unblock my team. Big picture is fine for the planning meetings but on small teams I'm usually the only one, I have a bunch of cooldowns to keep track of, and don't always have the context because I have a separate workstream that has to telegraph out ahead of the dev work.
I am always asking what I should do that has the most impact for my devs.
* Looking for people who caught aggro and getting out ahead of it is the bulk of my work. It's how I prioritize my workstream. The problem, and where the metaphor breaks down, is that I'm not omnipotent or have Grid2. If my devs don't tell me their pain points or I don't pull it out of them by asking what deliverables they would like to see out of me I would miss out lots of higher priority items than what I can see.
* The whole reason I'm on a team is because I have a specialized skillset and am but one stakeholder among many who want things from me. I will never run out of stuff to bring to planning but ultimately it's a group discussion about what I should do next. For larger companies s/me/the infra team.