The Uncomfortable Truth: Your Best Engineer Is Often Your Worst Manager

Few opinions trigger stronger reactions in modern workplaces than this one:

Technical people often make worse leaders than non-technical people.

For engineers, developers, architects, data scientists, and technical founders, that statement can sound almost offensive. After all, if someone understands the work better than anyone else, shouldn't they naturally be the best person to lead the people doing it?

That's exactly what most companies assume. And that's why so many leadership promotions fail.

Every year, organizations take their highest-performing technical contributors and move them into management. The best programmer becomes the engineering manager. The best engineer becomes the director. The best architect becomes the VP.

The logic feels undeniable.

If someone is exceptional at the work, surely they'll be exceptional at leading the people doing it.

But leadership isn't the next level of technical expertise.

It's an entirely different game.

And that's where companies get into trouble.

Expertise in solving technical problems does not automatically translate into expertise in leading human beings.

The Leadership Promotion Trap

Most organizations treat leadership as a reward for technical excellence.

That's the mistake.

Leadership is not a promotion from technical work. It's a career change.

The skills that make someone an elite engineer are often very different from the skills required to lead teams, influence behavior, navigate conflict, and create alignment.

Yet companies continue to confuse technical competence with leadership potential.

As a result, they lose outstanding individual contributors and gain mediocre managers.

Why Technical Experts Often Struggle in Leadership

1. They're Trained to Solve Problems, Not Manage People

Technical professionals spend years learning how to diagnose problems and create solutions.

People don't work that way. Code can be debugged. Systems can be optimized. Processes can be redesigned.

Human beings cannot. People are messy. They have emotions, insecurities, ambitions, frustrations, personal struggles, and competing priorities.

Many technical leaders become frustrated because people refuse to behave like systems.

Instead of coaching employees, they try to fix and control them.

The result is often disengaged teams, low trust, and declining morale.

2. They Overvalue Logic and Undervalue Emotion

Technical environments reward rational thinking. Leadership rewards emotional intelligence.

Employees rarely follow leaders simply because they're right. They follow leaders they trust.

A technically brilliant manager may produce flawless analysis while completely missing what's happening inside the team.

They fail to notice:

• Burnout
• Anxiety
• Loss of motivation
• Growing resentment
• Cultural dysfunction

The irony is that employees rarely quit because their manager isn't smart enough. They quit because their manager doesn't understand people.

3. Expertise Creates Micromanagers

One of the most common complaints about technical leaders is micromanagement.

And the reason is surprisingly simple.

They know exactly how they would solve the problem. So they review every decision.

Challenge every implementation. Rewrite other people's work. Insert themselves into every discussion.

What starts as helpful guidance slowly turns into control. Instead of building an independent team, they create a team that waits for permission.

Eventually, every important decision flows through one person.

The leader becomes the bottleneck. Ironically, the expertise that got them promoted becomes the thing slowing everyone down.

4. They Struggle to Let Go

Delegation sounds easy until you're watching someone do a task worse than you would.

That's the reality many technical leaders face.

When you've spent years mastering a craft, accepting a different approach can feel painful.

So work gets centralized. Ownership disappears. Employees stop growing. And the leader becomes overwhelmed.

The company scales more slowly because one person refuses to stop being the expert.

5. They Mistake Knowledge for Influence

This may be the biggest mistake of all. Technical professionals often assume credibility comes from expertise. Leadership credibility comes from influence.

Those are not the same thing.

A leader can be the smartest person in the company and still fail to inspire action.

Meanwhile, another leader with average technical knowledge can build trust, align teams, resolve conflicts, and rally people around a vision.

In most organizations, influence beats expertise every time. Because companies don't succeed when one person is brilliant. They succeed when large groups of people move in the same direction.

Why Non-Technical Leaders Sometimes Outperform Technical Ones

This is the part that makes people uncomfortable.

Many exceptional leaders are not exceptional technical contributors.

In fact, some of the strongest leaders deliberately avoid becoming the smartest person in the room.

Why? Because leadership rewards different strengths.

They Focus on People Before Problems

Non-technical leaders understand they can't compete through expertise.

So they focus on relationships. They listen more. They communicate more. They coach more. They spend more time understanding people than proving they're right.

What looks like a limitation often becomes a leadership advantage.

They Think Beyond Execution

Technical professionals naturally focus on implementation.

Leaders must focus on outcomes.

Strategy is rarely about finding the technically perfect answer.

It's about balancing people, priorities, incentives, customers, markets, and resources.

The best leaders understand that organizations are human systems—not engineering systems.

And human systems require a different kind of thinking.

The Counterargument: Some Technical Leaders Are Extraordinary

Of course, there are exceptions. Some of the greatest leaders in business have deeply technical backgrounds.

But that's not because they were technical. It's because they learned leadership.

They developed skills that had nothing to do with coding, architecture, or engineering.

They learned:

• Coaching
• Communication
• Delegation
• Influence

That's the shift that separates technical experts who become great leaders from those who don't.

What Companies Continue to Get Wrong

Organizations still assume leadership is the natural next step for successful technical employees.

That assumption creates two expensive problems.

Problem #1: Great Contributors Become Average Managers

The company loses an exceptional specialist and gains a mediocre leader. Nobody wins.

Problem #2: Leadership Becomes the Only Path to Success

Many technical professionals don't want to manage people.

They want to build. They want to solve hard problems. They want to create.

Yet organizations often force ambitious employees into leadership simply because it's the only way to advance.

The result is predictable. People end up in jobs they're neither passionate about nor naturally suited for.

The Real Question

The debate shouldn't be:"Are technical people worse leaders?"

The better question is:"Why do we keep assuming technical excellence predicts leadership excellence?"

Because it doesn't. Leadership is fundamentally about people. Technical expertise matters.

But communication, trust, influence, emotional intelligence, judgment, and vision matter far more.

A brilliant engineer can become a great leader. A non-technical professional can become a great leader.

Neither outcome is automatic. Leadership is not the reward for technical competence. It is its own discipline.

And until organizations stop confusing expertise with leadership, they'll continue promoting their best engineers into roles they were never trained to perform.

Conclusion

Technical expertise and leadership are different skills. The best leaders aren't always the smartest engineers—they're the people who can build trust, develop talent, and create alignment.

As a leadership coach, I help technical experts transition into confident, effective leaders. If you're navigating that journey, l

When I get sick, I take it seriously. I rest. I drink fluids. I pay attention.

When I tweak my back lifting something wrong, I see someone. I do the exercises. I let it heal.

When I eat something that doesn't agree with me, I notice. I probably won't eat it again for a while.

Physical discomfort, I honor. I treat it as information.

But psychological discomfort? For most of my life, I had a different relationship with that one. And I see it everywhere I look.

When something feels off in a conversation, we talk over it. When tension builds in a relationship, we get busy. When a feeling shows up that we don't want to feel, we distract, defend, or rationalize it away.

We've gotten very good at not feeling what we feel.

Fifty Years of Going Toward It

For nearly fifty years, I've been showing up to do this work in one form or another.

Men's rite of passage gatherings. Yoga intensives. Meditation retreats. Movement trainings. Shamanic practices. Process groups. Long conversations with individuals where the only real agenda was telling the truth and seeing what happened.

All of it, in different ways, designed to do the same thing: take me deeper into the patterns and beliefs that form who I am and how I behave. Expose the soft underbelly I'd otherwise spend a lot of energy keeping covered.

What I learned, over and over, was simple:

Unfamiliarity breeds fear.

The parts of myself I didn't know — the reactions, the defenses, the inherited beliefs running quietly underneath my decisions — those were the parts that had power over me. The more familiar I became with my own psychology, my own wiring, my own conditioned responses, the easier and more comfortably I could move through life.

And the more familiar I became with the same dynamics in other people, the more present I could be with them, even when what they were going through was hard.

The strange paradox of this work is that going toward discomfort, again and again, made me more comfortable in my own skin. Not less.

What I've Learned to Trust

Here's something I've come to believe deeply:

Discomfort is often at its greatest right before something breaks open.

Right before the answer comes. Right before a relationship turns a corner. Right before you finally see the thing that's been tripping you up for months, or years, or sometimes most of your adult life.

I've watched this in myself. I've watched it in person after person I've worked with. Peak intensity isn't a sign that things are getting worse. It's often the last resistance before something gives way.

The mind doesn't know that. The mind reads peak discomfort as proof that this approach isn't working, and pushes us to abandon the thing right at the moment it was about to teach us something.

Being With Someone in Theirs

I want to tell you about someone who worked for me once.

She came into my office on a difficult morning, carrying something heavy from her personal life. She didn't ask for advice. She didn't really ask for anything. She just needed somewhere to bring what she was feeling.

I didn't try to fix it. I didn't redirect the conversation. I didn't offer solutions or perspective. I just sat with her while she felt what she was feeling.

That was the whole thing.

She still mentions it to me, years later. Not because I said something wise. Because I didn't try to make her discomfort go away.

It took me a long time to understand that being with someone in their discomfort, really with them, is one of the most generous things a person can offer. And it's only possible if you've practiced being with your own.

You can't sit with what you haven't sat with.

What I Almost Missed

Years ago I was working with a leader who was stuck. Genuinely stuck. He had done everything he was supposed to do. Strategy. Communication. The right hires, the right structure, the right moves. And something was still missing in how his team showed up.

For weeks, our conversations got harder, not easier. He kept asking what to do. I kept asking him what he was feeling. He resisted that. He wanted a solution. He didn't want to feel what was underneath.

And then one afternoon, in the middle of yet another loop, something shifted. He got quiet. He sat back. And he said something he hadn't said in any of our previous sessions, about a fear he'd been carrying since childhood about not being enough.

That was the block. Right there. The whole thing.

He didn't need a new strategy. He needed to feel the thing he'd been spending his whole career trying to outrun.

The discomfort was at its greatest right before it gave way.

The Body Already Knows

What I find interesting, and what the neuroscience increasingly supports, is that the body usually knows before the mind does.

The tightness in the chest. The held breath. The restlessness that shows up when you're avoiding something. The way your sleep changes when there's a conversation you keep meaning to have.

Those signals aren't random. The nervous system is telling you something needs attention. The same way your back tells you you lifted wrong, or your stomach tells you that food was off.

Physical discomfort, we honor. We rest, we recover, we adjust.

Psychological discomfort, we override.

The body doesn't know the difference. The signals come from the same place. The rest, the recovery, the adjustment work the same way. The only difference is that the practice happens in stillness rather than stretching.

What Keeps Me Going Back

I'm not going to tell you discomfort is fun. It isn't. After almost fifty years of this work, I still resist on some days. The pull to look away is strong and it never fully goes away.

But I keep showing up. To the groups, to the practices, to the smaller moments inside the rest of my week where something difficult wants my attention and I have to choose whether to feel it or escape it.

What I can tell you is that almost everything that's mattered in my life and my work has come through the doorway of discomfort. The relationships that lasted. The clarity that finally arrived. The blind spots that finally became visible. The conversations that took years to have, and changed everything once I had them.

The discomfort wasn't the obstacle.

It was the path.

What's an uncomfortable thing in your life right now that might be closer to resolution than it feels?

The Category You Don't Notice Is the One That Runs You

Why This Matters More for Leaders

What Happens When You Use It as a Tool

If you gather a group of school-age children and leave them alone with something as simple as a ball, a game will almost always emerge.

One child will step forward, decide what game to play, and begin organising others into teams. Another may take on a similar role for the opposite side. Occasionally, someone else keeps score, calling out who is winning.

From the outside, it appears to be leadership in action.

It’s easy to see why.

The child who takes charge looks confident. Decisive. In control.

They organise, direct, and influence what everyone else is doing.

Parents and teachers often recognise this as early leadership potential.

But in reality, what we are often witnessing is something else —a natural tendency toward control.

At a young age, control and leadership can look almost identical. The person who steps forward stands out. They create structure where none exists. Others follow because it’s easier than resisting.

And in that environment, it works.

There are no real consequences. No long-term accountability. No need to build trust over time.

But as people grow older, the environment changes.

When Control Stops Working

As individuals move into their teenage years and early adulthood, the same behaviours begin to create friction.

The need to direct others, to stay in control, to have the final say ,these traits become harder for others to accept.

• Collaboration becomes difficult.
• Relationships feel strained.
• People begin to disengage.
  

In some cases, strong performance or talent can temporarily mask this behaviour. But over time, the pattern becomes clear.

What once looked like leadership starts to limit influence.

The Workplace Reality

By the time these individuals enter the workplace, expectations are very different.

Leadership is no longer about taking charge in every situation.

It requires a balance — confidence with humility, direction with listening, and authority with trust.

This is where many capable professionals struggle. They are used to being the one who steps in, solves problems, and drives action.

But in a team environment, this approach often leads to:

• Over-involvement in every decision

• Difficulty delegating

• Reduced ownership within the team

• Slower overall execution

• Growing dependence on the leader

I see this regularly in corporate settings and founder-led businesses.

The individual is not lacking skill or intent. They are simply operating from a version of leadership that was never challenged or refined.

The Organisational Blind Spot

Organisations, unintentionally, reinforce this pattern. We tend to promote individuals who:

• speak with confidence

• act quickly

• take visible control of situations

These qualities are valuable, but they represent only a small part of effective leadership. Over time, this creates a predictable outcome. Leaders who rely too heavily on control:

• become bottlenecks

• limit team capability

• struggle to scale themselves or the business

And the cost is often hidden until it shows up in performance, culture, or retention.

What Leadership Actually Requires

The ability to take initiative and organise people is important. But when it is driven by the need to control, it becomes a limitation. Sustainable leadership in the workplace looks different. It requires:

• creating clarity without micromanaging

• setting direction without dictating every step

• building trust instead of dependency

• knowing when to step in — and when to step back

Leadership is less about being in control, and more about creating an environment where others can think, act, and contribute effectively.

The Hard Shift

For many leaders, the real challenge is not learning new skills. It is unlearning the instinct to control.

The shift is subtle but powerful:

From “How do I stay on top of everything?” To “How do I build something that doesn’t depend on me?”

This requires restraint. It requires trusting others before they’ve fully proven themselves. It requires allowing space for mistakes, learning, and growth.

And it requires recognising that constant involvement is not the same as leadership.

Final Thought

What looks like leadership early in life often earns attention. But in the workplace, leadership is not measured by how much control you have.

It is measured by how well people perform, think, and grow without you. Because in the long run, people don’t follow control. They follow leaders who make them better.

My father could have been an entrepreneur, but he never became one.

He had the drive, the talent, and the skills. He was a tool-and-die maker — a craftsman who understood how to turn ideas into something real. He tried many business ideas over the years: custom water glasses, back massagers on his lathe. His eyes glowed with passion with each new concept. But none of his ventures succeeded.

The reason wasn’t lack of ability. It was simpler than that. My father was a craftsman who never learned business. And he never found the right partner — someone who could bridge the gap between concept and opportunity.

I became an entrepreneur. And it was thanks to partnership.

My first business launched out of my garage in the Santa Cruz mountains in the mid-1980s. Victor Technologies, where I’d been managing the field service department, was shedding their older product lines. I had the skills to repair their computers, a cache of spare parts was going up for sale, and Victor was willing to send me their customers. I quit my job and found a partner. 

We made money in the first month.

That was just the first of dozens of partnerships across thirty-five years. Working partnerships, financial partnerships, strategic partnerships. With these partners, we made powerful breakthroughs. But we also fought. Occasionally we didn’t speak for weeks. I had to end employment for a friend who was also a limited partner. One partnership lasted fifteen years past the point where it should have ended, and it cost me the business I’d spent years building.

And from all of it, I learned something that I couldn’t find written down anywhere: partnerships aren’t a business model. They’re ecosystems.

When Teams Move Like Starlings

The Sweet Spot That Keeps Moving

Living at the Edge of Chaos

Making the Edge Safe Enough

The Rhythm of Growth and Integration

Reaching and Releasing

• Where is my team on the spectrum between rigidity and chaos right now? What would move us closer to that generative edge?
  
• What would it look like to build in intentional consolidation after our next push?
  
• When did I last see my team surprise itself? What conditions were present?
  

You built it. You funded it. You live and breathe it. You are theOwner, the visionary, the person who makes the final call.

In that position, there's a powerful, subtle truth that eventually becomes a trap:When you are the Owner, no one tells you “No.”

This isn't a power trip; it's a structural reality. It’s born from a complex web of loyalty, ambition, and the very nature of hierarchy. While it feels like "smooth sailing" in the moment, it is quietly the biggest bottleneck to your growth.

The Echo Chamber Effect

Think about the three circles of your professional life:

• Your team wants to please you.They are driven by loyalty and career progression. Challenging the founder carries a perceived risk. They’ll tell you what they think you want to hear, or simply fall in line and execute a flawed plan.
• Your board wants results.Their focus is on financial milestones. While they might challenge the "how," they often defer to your conviction on the "what." If the numbers look okay today, they won't push back on your operational blind spots tomorrow.
• Your family doesn't want to hear about work.They offer emotional support, but they aren't strategic partners. They hear the stress, but they aren't positioned to give you an objective critique of your leadership.

The result? You create anecho chamber. Your ideas don't get stress-tested. Your bad habits go unchecked. You stop being a student of your own leadership and start becoming a bottleneck.

The High Cost of Unchecked Authority

When "No" disappears from your vocabulary, three things happen:

1. Leadership Debt:Your habits become the ceiling for the entire company. If you micromanage, your managers stop thinking. If you delay decisions, the whole organization slows down.
2. Stifled Innovation:If challenging the boss isn't rewarded, new ideas stop surfacing. Why bother innovating if the path is always dictated from the top?
3. Isolation:Paradoxically, being constantly affirmed is incredibly lonely. The weight of every decision rests solely on your shoulders because no one feels empowered to share the load.

Breaking the Cycle

True power doesn't lie in being unchallengeable. It lies in building a system where the best ideas win, regardless of who they came from.

To scale, you have to move from being thesingular answerto being thearchitect of answers.You need someone in your corner who has zero agenda other than your performance—someone who isn't afraid to tell you when you're wrong.

Ready to get out of your own way?

If your business is growing but you feel like you’re the one holding it back, let’s talk. I help Owners and Leaders identify their blind spots and build teams that take real ownership.

Click [here] to book a 15-minute Strategy Alignment call.

Let’s turn the noise into signal.