Reese H. is adjusting the D65 daylight simulator for the 29th time this morning, his eyes narrowing as he compares a swatch of “Industrial Cobalt” to the master standard.
He’s an industrial color matcher, a man whose entire career is built on the smallest detectable differences in light and pigment. If a batch of plastic for a medical device is off by a fraction of a percent, Reese is the one who smells the error before the machines even register it.
He’s been the top individual performer at the plant for . He owns the outcomes. He is the single point of failure for the entire supply chain, a title he wears like a badge of invisible gold.
Last week, I watched Reese pretend to be asleep in the breakroom while his manager discussed the upcoming Director of Quality role. He wasn’t actually tired; he just didn’t want to explain, yet again, why the 99-page report he submitted on “Process Optimization” was ignored in favor of a candidate who hasn’t touched a spectrophotometer in .
Reese is the quintessential L5. He is the person who gets things done, the person who “owns” the problem until it bleeds. And that, fundamentally, is why he is stuck.
The Mathematical Irony of Progression
There is a cruel, almost mathematical irony in high-level career progression. The behaviors that earn you the keys to the L5 kingdom-ruthless execution, deep-domain expertise, and the ability to personally pull a failing project across the finish line-are the exact same behaviors that will get you rejected at the L6 calibration table.
You are running uphill, but you’ve reached a point where the stairs have turned into a ladder, and you’re still trying to run.
We think of career levels as a linear progression of the same skills. We assume L6 is just L5 but with a 29 percent larger budget or a team of 19 instead of 9. It’s a comforting lie. In reality, the axis shifts.
The fundamental shift from individual delivery to organizational enabling.
I remember a specific calibration meeting for a senior engineer-let’s call him Marcus-who had delivered 39 successful feature launches in a single year. He was a machine.
“Marcus saved the day,” “Marcus stayed up until to fix the bug,” “Marcus is the only one who understands the legacy code.”
– Peer Review Calibration Panel
To Marcus, this was a slam dunk for L6. To the promotion panel, it was a red flag. They saw a man who hadn’t built a system that could survive without him. They saw an L5 who was over-performing at the wrong level.
The “smallest” margin of error for an L5 is often technical. For an L6, the smallest margin of error is cultural. It’s the difference between telling a team what to do and building the infrastructure so they already know what to do.
Confessions of an Expensive Cog
I once spent arguing with a mentor about this. I told him that if I stopped doing the work, the quality would drop. He looked at me with a tired sort of pity and said:
It hurt. I went home and sat in the dark for , realizing that my pride in being “indispensable” was actually a confession of my inability to lead at scale.
This is the psychological wall. To move from L5 to L6, you have to kill the version of yourself that loves being the hero. You have to be okay with things being done 79 percent as well as you would do them, provided they are being done by 19 people instead of one.
Industrial color matching, strangely enough, is a perfect metaphor for this. In the old days, a master matcher like Reese H. would mix the dyes by hand, relying on “the eye.” It was artisanal. It was elite. But it didn’t scale.
To grow the business, the company had to move to automated dispensing and algorithmic color correction. The master matcher’s role shifted from “doing the mixing” to “calibrating the system.” If the master matcher kept grabbing the stir stick, he was actually preventing the system from learning.
Data Viz: The shift from “Contribution via Volume” to “Contribution via Multiplier”.
Most senior candidates fail their promotion not by underperforming, but by overperforming the wrong things. They double down on ownership. They think, “If I just work 59 hours a week instead of 49, they’ll see how much I contribute.”
But the panel isn’t looking for contribution; they are looking for influence. They want to see that you have moved from “I delivered X” to “I enabled the delivery of X, Y, and Z by identifying the 19 blockers that were slowing down the entire organization.”
Rewriting Your Professional Narrative
This shift requires a total rewrite of your professional narrative. When you sit down for a calibration or a high-stakes interview, the stories that got you to L5-the “I saved the project” stories-will actually hurt you.
You need to talk about the times you stepped back. You need to talk about the systems you built, the people you mentored into L5s themselves, and the strategic pivots you navigated that saved of wasted effort across three departments.
This is where professional guidance becomes vital. Navigating these shifts is complex, and many find that
provides the necessary mirror to see where their “hero” tendencies are masking their leadership potential.
The transition is often lonely. When you are an L5, you get the dopamine hit of finishing a task. You see the color match; you see the code ship. When you are an L6, your “work” is often invisible.
It’s the absence of a crisis. It’s a meeting that ended early because you’d already aligned the stakeholders. It’s the quiet growth of a junior dev who just handled their first major outage without pestering you.
I’ve made the mistake of trying to bridge this gap through sheer volume. I thought if I attended 99 meetings a week, I was being “strategic.” I wasn’t. I was just a busy L5. True L6 behavior is often about subtraction.
What can I stop doing? What can I delegate? What process can I simplify so that the “smallest” member of the team can execute it with 99 percent accuracy?
Reese H. still hasn’t figured this out. He’s currently obsessed with a new pigment from a supplier in Germany. He’s spent researching its molecular stability. He’s going to write a brilliant memo about it.
And he will be passed over for promotion again, because the company doesn’t need a man who knows everything about one pigment; they need a man who can design a procurement strategy for 199 pigments that reduces lead times by 29 percent.
There is a certain grief in this. You have to let go of the thing you are best at. You have to become a novice again at the art of delegation and organizational design. It’s uncomfortable. It’s why people stay stuck. It’s easier to be the best L5 in the building than it is to be a mediocre L6 learning how to wield influence.
The Logic of Sitting on Your Hands
I remember a project where we had to scale a data pipeline for 149 clients. My instinct was to jump in and write the core logic. I knew I could do it faster and better than the rest of the team.
But I forced myself to sit on my hands. I spent my time instead writing the documentation and the testing suite. I let the team struggle. It took 39 percent longer than if I had done it myself.
But at the end, I had five engineers who understood the pipeline as well as I did. That was the first time I felt like I was actually doing L6 work. The “cost” was my own ego and a few extra days of development time. The “value” was a team that no longer needed me to stay up until .
If you look at the most successful leaders in any organization, they are rarely the most technically gifted people in the room. They are, however, the most effective at managing the energy and the focus of those who are.
They understand that their primary product is no longer “the work,” but “the environment in which the work happens.”
If you find yourself frustrated, feeling like you’re doing the work of two people but receiving the recognition of half a person, stop. Look at what you’re doing. Are you “owning” the outcome, or are you “stewarding” the process? Are you the hero of your stories, or is the team the hero?
If you multiply yourself by zero because you won’t let go of the work, your total value to the organization-at scale-is zero.
We often talk about “leveling up” as if we’re adding more tools to a belt. It’s more like changing the belt entirely. You’re trading in your hammer for a compass.
The hammer is great; it’s served you for . You’ve hit 999 nails perfectly. But a compass is the only thing that’s going to get you out of the woods.
I’ve seen too many talented people burn out at L5 because they keep trying to be the hero in a story that has outgrown them. They think the system is rigged against them. It’s not. The system is just looking for something they aren’t showing it.
It’s looking for the person who can step away from the light simulator, leave the lab, and go into the 19th-floor boardroom to explain why the color of the plastic doesn’t matter as much as the reliability of the mold.
Reese H. just finished his match. He looks proud. He should be; it’s perfect. But as he walks back to his desk, I see him ignore 9 emails from junior technicians asking for guidance. He doesn’t have time for them.
He’s too busy being the best color matcher in the world. He’ll be back here tomorrow, adjusting the lights for the 29th time, wondering why no one has noticed how hard he’s working.
The irony is that they have noticed. And that’s exactly why he’s staying right where he is.
Are you working harder to prove you belong at your current level, or are you working differently to prove you’ve already outgrown it?