There is a particular kind of hire that happens regularly in tech companies, usually when something has gone sideways. A team is failing to execute. A product is stalling. A function needs to be stood up from scratch, or a relationship has been mishandled, or the company has grown faster than its systems and now things are quietly on fire. Leadership looks around, identifies the problem, and then does something that is, at least on its face, the right thing: they bring in someone exceptional to fix it.
She is, usually, exceptional. She has the resume. She has the judgment. She has done this specific thing, or something close to it, more than once, and she has the scar tissue to show for it. Leadership is, in that initial period, genuinely enthusiastic. They tell other people about her. They use words like “strategic” and “exactly what we need.” She gets the title and sometimes the budget and always the large, complicated problem.
And then they do not give her what she needs to do the job.
Not dramatically. Not through malice. It is quieter than that, and in some ways more corrosive because of the quietness. They share the information they think she needs, when they think she needs it. They loop her in after decisions are made rather than before. They hand her the brief but not the backstory. They introduce her to the stakeholders but not to the history of the relationship, or the failed attempt eighteen months ago that the stakeholder is still quietly angry about, or the internal political current she is now swimming against without knowing it. She finds the missing context the way you find missing steps in a staircase: at speed, in the dark, when it is too late to catch yourself.
When she asks, they answer. This is the part that makes it so hard to name. They are not withholding. They are responsive. They are even, they will tell you, transparent. But there is a profound difference between a system that shares information proactively and a system that shares information reactively, and that difference falls on her as a tax levied against her effectiveness in small, invisible increments.
In security architecture, there is a principle called need-to-know. The idea is that access to sensitive information should be granted only to those who require it for their function. It is a legitimate and important principle when applied to classified intelligence or medical records or financial data. It is a catastrophic principle when applied, consciously or not, to the professional context a person requires to do their job.
The tech workplace runs a degraded version of this. Not the formal, documented version. The informal one, the one that nobody wrote down and nobody decided, the one that accumulated over years of a company’s history like sediment. The old-timers know. The people who were in the room when the decision got made know. The person who was at the offsite where the strategy shifted knows. The information is not secret, exactly. It is just assumed. It exists in the oral tradition of the organization, passed around at the Thursday lunch or the post-meeting debrief in the hallway that the person who joined last month was not part of. Every organization has this. The question is who gets inducted into it, and on what timeline, and whether the induction is active or passive.
When the answer is passive, which is to say when the culture assumes that people will absorb organizational context by osmosis and will ask if they need something, the people who pay the highest price are the ones who joined with a clear mandate, a high-stakes problem, and no runway for looking uncertain. A new person who is positioned as junior is expected not to know things. A new person who is positioned as senior, as the person who was brought in specifically because of their expertise and judgment, is not supposed to need orientation. The expectation is that she arrived already knowing. The gap between that expectation and reality is hers to manage, invisibly, while also doing the actual job she was hired to do.
There is a cost to asking, and it is not evenly distributed.
When a man in a senior role asks for context, it reads, fairly consistently, as diligence. He is being thorough. He is making sure he has the full picture before he acts, which is the kind of strategic thinking you want in a senior hire. When a woman in a senior role asks for context, the same question can read differently. Not always. Not everywhere. But often enough to be a documented pattern rather than an anecdote: she is missing something she should already know. She is not as prepared as expected. She needed help.
This is not speculation. The research on gender and the perception of competence is extensive and grim and mostly ignored in practice. The same behavior reads differently depending on who performs it. A woman who advocates for resources is demanding. A man who advocates for resources is strategic. A woman who says she needs more information to make a good decision is underprepared. A man who says the same thing is deliberate. The double standard does not require anyone in the room to be consciously sexist. It operates in the gap between stated values and the reflexive judgments that happen faster than reflection.
So she asks less than she should. She fills the gaps herself, spending time and energy on reconnaissance that her male counterpart spent on the actual work. She builds the map of the organization from scratch, interview by interview, meeting by meeting, and she does it largely invisibly, because visibility in this domain looks like weakness. She absorbs the cost and she smiles in the status meeting because the status meeting is not the place to say that she has spent the last three weeks finding out what she should have been told in week one.
I want to be specific about what leaders are actually doing when they hire a capable woman for something important and then manage the information asymmetry poorly, because I do not think it is usually conscious, and I think the unconscious version is worth examining more carefully than the conscious version precisely because it is harder to see and easier to excuse.
Some of it is paternalism dressed as protection. She is new. She does not need to know about the failed initiative that the executive sponsor is still embarrassed about, not yet, it will color her perception before she has a chance to form her own. The intention is good. The effect is that she walks into a room missing the context that would explain why the executive sponsor goes quiet when a particular topic comes up, and she has to figure it out through a read of social cues that she could have spent on the actual work.
Some of it is the way information is attached to relationships, and relationships take time, and organizations that run on relationships are often not aware of how much invisible onboarding those relationships represent. The person who knows why the last vendor relationship failed is the same person who was there for the vendor relationship. Getting that person to transfer that knowledge requires them to understand that the knowledge is worth transferring, which requires them to understand what she needs, which requires them to think about her perspective rather than their own, which is precisely the cognitive work that busy, well-meaning people tend not to do systematically.
And some of it (this is the part that is hardest to say plainly) is that keeping her on a need-to-know basis keeps her dependent. Not as a deliberate strategy. Not, usually, with any awareness that it is happening. But a person who must ask for context to operate is, functionally, a person who must maintain a relationship with the person who holds the context. She comes back, regularly. The relationship is maintained. She remains, in a subtle and deniable way, managed.
The version of this that most damages organizations is when it intersects with credit. She does the work. She navigates the missing context, she figures out the political geography through trial and some painful errors, she builds the relationships from scratch and delivers the result. And then the person who gave her the context she needed (when she needed it, when she asked, in dribs and drabs over months) gets attributed as having been essential to her success. He was so helpful. He really brought her up to speed. She could not have done it without him.
She did it despite him. The distinction is important and almost never made.
The fix is not complicated. It is just work, and it requires the specific kind of intentionality that organizations tend to apply to things they have decided are important and almost nowhere else.
Proactive context transfer when someone senior joins. Not the org chart and the P&L and the slide deck that was presented at the last all-hands. The actual history: what was tried before this, what failed, who has a position on this that is not yet visible to someone new, where the real decisions get made and who has to be in the room for them to stick. This information exists in the heads of the people who were there. Someone has to go get it and give it to her, before she asks, before she needs it, before she walks into the room without it.
Explicit relationship introductions with actual context. Not just “this is the head of engineering, you should connect” but “this is the head of engineering, he had a proposal for this space that did not move forward eighteen months ago, he is not a blocker but that history is in the room with you.” That sentence takes fifteen seconds to say. It saves weeks.
A reckoning with the asymmetry of asking. If her asking for information is a tax on her perceived competence, then the organization has an obligation to make asking structurally unnecessary, not by telling her less, but by giving her more without requiring her to surface the need. The burden of proactive information sharing should sit with the people who have been there longest. They hold the context. Moving it is their job.
There is a version of this that gets framed as a communication style difference, or as organizational onboarding challenges that affect everyone, or as the natural friction of joining a complex system. Those framings are not wrong, exactly. The friction is real and it does affect everyone.
But “affects everyone” and “affects everyone equally” are not the same sentence, and collapsing them is how organizations avoid the specific work of looking at who bears the cost disproportionately, and why, and whether the structure that produces that outcome is acceptable once it has been named.
She was brought in because she was exceptional. The least the organization can do is let her be exceptional with full access to the information she needs to operate. Not on a need-to-know basis. Not when she asks. From the beginning, on the assumption that she is there to succeed, and that success requires context, and that providing context to the people who need it to do important work is not a favor.
It is the job.
