When I joined Netflix there were four of us doing security. By the time I left, that function had grown past a hundred. Somewhere in the middle of that climb I helped hire an engineer who, about three months in, understood our environment better than I did.
Not better in some narrow corner. Better, full stop. He could hold the live system in his head, trace a request through services I’d only ever seen on a diagram, and tell you where it would fail before it failed.
I remember the meeting where it landed. He was walking us through an attack path and I was two beats behind, nodding while I did math under the table. The feeling I had wasn’t threat. It was relief. The hire was working exactly as designed. The intention wasn’t to bring him in to be slightly useful one rung below me. I wanted him brought in to know more than me.
That’s the part most leaders never make peace with.
The Authority Inversion
There’s an old model where the person in charge is the person who knows the most. The best engineer becomes the lead. The CISO is the one who can out-argue the room on firewalls. Knowledge runs down the org chart, authority runs right alongside it, and the two feel like the same thing.
That model had a good run. It’s over.
The CISO who knew more about firewalls than anyone on the team was a fine CISO for 2010. The surface is too big now. Nobody holds all of it. The cloud architecture, the detection pipeline, the model you shipped to production last week, the regulatory exposure across three jurisdictions: no single human is the smartest person in the room across all of that. If your authority depends on being that person, your authority is already gone. You just haven’t felt it leave.
The inversion isn’t the problem though. The inversion is the design. You’re supposed to hire people who exceed you. What goes wrong is the panic about it, the small hot feeling that if they know more, you’re exposed. That feeling is the actual failure mode, and it manufactures two bad leaders. The one who bluffs. The one who clamps down so nothing happens without them.
Both are trying to protect a kind of authority that stopped existing.
What Credibility Actually Is
So if it isn’t knowledge, what are people following?
Judgment. Specifically, judgment about what matters.
I couldn’t trace every request the way that engineer could. But I could tell you which of the six things he was worried about was the one that would end up in front of a regulator, which one was interesting but survivable and which one we were going to consciously not fix this quarter. And why each call was the call. That’s a different skill than his. Not lower, not higher. It’s the one the seat actually requires.
But here’s where I lose the people who want a clean answer: judgment without literacy is just confident guessing. You can’t evaluate what you don’t understand at all. The leader who says “I don’t need to know the tech, I just hire smart people” is one fluent liar away from a disaster, because they have no way to tell a real answer from a good-sounding one.
You don’t need to be the best cryptographer to run the program. You need to know which crypto question is load-bearing, and enough to know whether the answer you just got was real. Enough to ask the second question. Enough to smell it when someone’s managing you with vocabulary. That’s the line. Not omniscience. Not ignorance dressed up as delegation. Enough to judge.
The Moment of Exposure
Every leader managing experts gets the same recurring moment. Someone is explaining something and you’ve lost the thread.
The old reflex is to nod and bluff. Protect the picture. The team always clocks it: they see the nod that doesn’t connect to anything, and the real cost isn’t that you looked slow. It’s that they just learned information can move past you without resistance. Which is the precise thing you were hired to prevent.
The move is plain. “I don’t follow that yet. Walk me through it.”
I’ve said that sentence in front of people who report to me, more than once, over twenty-five years into this. It doesn’t lose the room. It does the opposite. It tells the expert their explanation has to actually land instead of just sounding right, and it tells everyone watching that the standard in here is understanding, not performance. The strongest people I’ve managed were never confused about whether I was the deepest expert in the building. They were clear that I was the one deciding what we’d stake the quarter on. Different jobs. They knew which one was mine.
What the AI Era Does to This
Until recently, the expert inversion was occasional. You felt it with a few specific hires, in a few specific meetings.
That’s done. Now there’s a system in the room that has read more than your whole team combined, and it’ll explain a vulnerability class or a market or a legal argument in clean, confident prose at three in the morning. The inversion isn’t occasional anymore. It’s constant, it’s synthetic, and it never gets tired or political.
This breaks the bluffers completely. You cannot out-knowledge a model trained on most of what’s been written down.
And yes, you can teach it your “here.” I’ve built the systems that do exactly that: feed a model the postmortems, the org chart and the risk register, and it reads your environment faster than most new hires. The context objection is real. I won’t wave it away.
But two things don’t transfer. First, the part of “here” nobody wrote down: who’s about to quit, what was actually decided in the hallway, the thing that moved this week and hasn’t reached a document. Second, and this is the one that holds: the model can absorb all of it and still not be the one accountable for the call. It’ll hand you ten options and sound equally certain about all ten, because it has nothing at stake in being wrong. You do. Judgment isn’t just knowing the context. It’s deciding under consequences you carry.
That’s the whole job now. Not knowing the most. Reading what you’re being told, by humans and machines both, and deciding what’s worth the weight of the organization. The expert inversion went from a feeling you had about a couple of people to the daily condition of the work. The practice is the same one I learned in that meeting at Netflix. The scale is not.
Your authority was never your knowledge. It’s your judgment about what matters. Confuse the two, and you become the bottleneck the smartest people in your building learn to route around.
ZenOne also produces electronic music. The mixing arc behind the work is at zenonemusic.substack.com.