The Deer in Headlights
The silence was heavier than the humid air conditioning unit that always seemed to leak on floor 4. You could almost hear the molecules of tension vibrating between Elena and Mark. Two senior developers, usually capable of debating the merits of Haskell versus Rust with surgical precision, were locked in a staring contest over a trivial API dispute.
And there was Alex, their brand new manager, who had been promoted just three weeks prior because he wrote the fastest asynchronous processing loop the company had ever seen. Alex was a genius. Truly. He could debug a six-month-old system architected by someone who had clearly lost their mind, and fix it in 44 minutes. But put him in front of two humans having a conflict that required listening, empathy, and perhaps, the mild manipulation of emotional expectation?
🦌 😵💫
Alex: The startled deer.
“So,” Alex finally managed, rubbing the back of his neck, leaving a faint oil smudge on the crisp new collar of his shirt. “I think… the core problem here is data flow inconsistency in communication patterns, not the code itself.”
Elena leaned forward, skeptical. Mark just sighed, looking at the ceiling, mentally calculating the complexity required to implement a new CI/CD pipeline.
“What if,” Alex continued, voice regaining some of the technical authority he lost talking about feelings, “we treat this interaction model as a system failure? Elena, you communicate style A. Mark, you communicate style B. We A/B test your communication styles over the next 4 days. Then we use quantitative metrics-response time, sentiment analysis-to determine the optimal path.”
He offered a triumphant, albeit slightly sweaty, smile. Then he stood up, declared, “Problem solved. Let me know the results by end of day Friday,” and walked straight out the door to go back to coding, which was the only thing that felt real to him.
Revelation Point I
Organizational Self-Sabotage
This is the failure. This is the moment I recognized the Peter Principle wasn’t some theoretical, occasional administrative mistake-it is the default, industrialized career ladder in organizations that prioritize doing over enabling. We force our best technicians into roles where they become the worst possible leaders.
The Miscalculation of Value
We didn’t promote Alex because he showed great managerial potential. We promoted Alex because he was too valuable to stay where he was, yet we had no other way to reward him without giving him a bigger title and a commensurate salary increase-specifically, $474 more per pay period.
The entire system relies on components-be they human talent or physical hardware-being managed and operated by those who understand the system of logistics, not just the components themselves. Look at how a service like smartphones chisinau manages their network; it’s designed around logistical expertise, not around rewarding the most skilled forklift operator with the title of CEO.
Skill Transferability Fallacy
Technical Output (Competence)
Leadership Amplification (Management)
We mistake technical competence-the ability to 10x output-for leadership potential. Leadership, however, is an input amplifier. It’s messy. It’s invisible for months.
Respect for what you can build is not the same as trust in how you guide people. The first is transactional; the second is existential.
The Oracle Moved to Purchasing
I know this because I made the same catastrophic error. But consider Nova Z., a woman I hired at a previous firm. Her title was “Quality Control Taster” for a specialty food processing plant. Her palate was legendary. She could detect a 0.004% fluctuation in the coriander concentration simply by running her tongue across the back of her teeth. She didn’t use jargon; she just said, “It feels lonely,” or “It’s arguing with itself.” She was an oracle.
Management moved her into the Purchasing Department to manage raw ingredients. Her gift was not managing inputs; her gift was tasting outputs. Suddenly, Nova Z., who could sense the subtle emotional distress of a cumin seed, was failing to meet with aggressive spice merchants who demanded price flexibility.
The Cost of Misplacement
Batch Quality Precision
Cost Negotiation Rate
We cannibalize our own expertise. A programmer deals with a compiler that is brutally logical. A manager deals with a team member who is late because their cat is sick, or because they feel unheard. You can’t A/B test that kind of chaos.
Decoupling Reward from Role
The problem is that organizations treat management skill development as optional, or worse, as intuitive. You wouldn’t hire an architect and expect them to immediately understand structural engineering without training. Yet, we throw our best developers into the deep end of conflict resolution, budgeting, and performance management.
Specialist Track (PE)
Reward for Deep Output.
Enabler Track (Manager)
Reward for Human Optimization.
A Principal Engineer should be able to earn $300,000, manage zero people, and still be seen as the ultimate success story. Management is a discipline, demanding its own expertise, its own certification, and its own deep respect.
Revelation Point II: The Compromise
I criticize the organizational design, yet I leverage their technical fame as a temporary shield, repeating the cycle for speed and cheapness.
It is the cheapest and fastest solution, and that, perhaps, is the darkest truth of the whole mess.
Look at Alex, A/B testing human sadness. He tried to solve an emotional problem with a logical framework because that is the only language he speaks. We built a system that punishes diversity of skill.
The Silent Sacrifice
So ask yourself: If your most brilliant individual contributor quit tomorrow, would you mourn the loss of their output, or would you quietly celebrate that you didn’t have to risk turning them into another terrible manager?
And what does it say about your company that the only way to recognize true genius is by forcing it into silence?