Every company has two org charts.
The first one lives in the HR system. It’s clean. It shows who reports to whom, who has budget authority, who’s in charge of what. It’s useful for figuring out who to cc on an email and who approves your time off. Beyond that, it’s mostly decorative.
The second one doesn’t exist anywhere you can see it. No document, no diagram, no Confluence page. It’s the one that actually determines what happens—who gets consulted before a decision gets made, whose opinion the VP asks for before committing to a technical direction, who can block a project without ever appearing in the meeting where the project gets discussed. This org chart runs on trust, relationships, and accumulated credibility. It has nothing to do with the boxes on the official version.
I wasted years looking at the wrong one.
I’d look at the formal hierarchy and think I understood how things worked. Director above manager. VP above director. Straightforward. Except the senior IC whose opinion the VP always asked before making technical calls mattered more than whatever the formal chart said. The engineer who somehow controlled what got prioritized, regardless of the roadmap, had more pull than his title would suggest. And the person who’d been there a decade and knew where all the bodies were buried—more importantly, who buried them—had a kind of gravitational pull that no org chart could represent.
There’s an executive assistant somewhere at your company who filters what reaches the CEO’s calendar. That person has more practical power than half the directors on the org chart.
None of this is secret. It’s just invisible if you’re not looking for it. And I wasn’t looking for it, because I was busy doing what I thought the job was—writing good code, shipping features, being technically right about things. Nobody told me the job was also understanding which conversations mattered and who was in them.
The real structure—the power network—is built on things that don’t fit in boxes. Who’s been right enough times that people trust their judgment without checking. Who has the ear of someone who actually makes decisions. Who gets invited to the pre-meeting before the real meeting, where the actual discussion happens and the actual direction gets set. By the time something gets formally discussed—in a planning meeting, a review, an all-hands—the decision has usually already been made. The meeting is just theater. A ratification dressed up as a debate.
I figured this out the embarrassing way. I’d speak up in meetings with what I thought was a strong point—technically correct, well-reasoned. All I’d get is a polite nod back before changing the conversation without. Meanwhile, someone with a less developed point but more political credibility would say something, and suddenly we were changing direction. I wanted to believe it was because their idea was better. Sometimes it was. Often it wasn’t. Their idea just came from a node in the power network that mattered more than mine.
I’m not trying to complain—this is all human nature. It’s silly to expect that because there’s formality around an entity that it will suddenly be better. Because of the incentives, it’s usually worse. In organizations, information flows badly, incompletely, and with a heavy bias toward people who are already trusted. The engineer whose opinion gets sought isn’t always the best engineer. They’re the one who’s been right enough, visible enough, and present enough that their judgment became something people relied on without thinking about it. That’s not meritocracy failing. That’s just how humans build trust—slowly, through familiarity, in ways that consistently favor the people who’ve been around long enough to accumulate it.
The frustrating part—the part that kept me up at night during the years when I was too dumb to see it and too proud to ask—is that the shadow org chart explains most of the things that confuse people about their careers. Why your proposal died and someone else’s sailed through. Why your idea got ignored and the same idea, from a different mouth, became the plan. Why some people seem to get everything they want despite modest titles, and why you’re doing excellent work that somehow doesn’t translate into anything.
I’ve decided to call this the influence network. It’s my own way of defining organizational behavior. The proposals that got funded had been pre-sold to the right people before they ever hit a formal meeting. The engineer who kept getting the good projects wasn’t just lucky—they positioned themselves with precision.
I eventually started paying attention to who talked to whom before decisions happened. Not in a scheming way—I’m not built for scheming, and I’d be bad at it. More in a “oh, that’s why that happened” way that slowly, over years, changed how I understood the places I worked. I started noticing whose #watercool posts got fast responses from leadership and what emojis were used. I paid attention to who got invited to things that weren’t on any official agenda. I started realizing that the same people were whose former colleagues kept joining the company—because that signals influence, and people bring in people they trust.
The shadow org chart isn’t sinister. It’s just the natural result of humans working together over time, building relationships, developing trust, and gravitating toward the people they already know and already believe. It’s rational, even. You’d do the same thing—you already do, probably, without thinking about it. The problem isn’t that it exists. The problem is that most people don’t see it, and the ones who do see it have a massive advantage over the ones who don’t.
It took me a while to realize this. I was too busy reading the official version, the one with the clean lines and the clear hierarchy, and wondering why reality kept refusing to match the diagram.
It never does.