Years ago, I sat across from a mentor who had a way of cutting through the noise with a single sentence.
I was deep in my craft at the time — obsessed with the technical nuances of my field, convinced that being the most knowledgeable person in the room was the ultimate competitive advantage. He leaned back, looked me in the eye, and said something I filed away as obvious but not particularly urgent.
"Technical skills can open doors, but people skills keep them open."
I nodded politely. In the back of my mind, I thought: Sure, but the person who is most technical wins.
I was wrong. It took me years to understand how wrong.
What I Thought Leadership Was
The model I had for leadership, the one I'd built from watching people succeed around me, was essentially: be the best at the technical work, and the people stuff will follow. Get the right answers. Solve the hard problems. Be indispensable.
This is a seductive model because it works — for a while. And it works just long enough to get you promoted.
The problem is that the skills that make you an exceptional individual contributor are not only different from leadership skills — they can actively work against them. When your identity is built around being the person with the answers, you become a bottleneck by nature. You don't mean to be. You're trying to help. But every time you jump in and solve a problem that someone on your team could have worked through themselves, you are teaching them not to think.
I did this for longer than I'd like to admit.
The Invisible Language
What my mentor was pointing at — what I didn't fully grasp until much later — is that great leaders operate in a language most technical people haven't learned to read.
They pay attention to tone: how feedback is delivered matters more than the feedback itself. They read timing: knowing when to push and when to let a team breathe is often more valuable than knowing the right answer. They listen to silence: what isn't being said in a meeting is frequently the most important information in the room.
None of this is on any engineering curriculum. None of it shows up in a technical review. And yet it is the entire job once you're leading people.
The leaders I've watched build something lasting — the ones whose teams actually grow stronger over time — are not necessarily the most technically brilliant. They are the ones who understand that their job is no longer about their own performance. It's about the performance of the people around them.
They give credit freely and take responsibility quietly. Their teams don't follow them because of their title. They follow them because they feel seen.
The Shift That Changed Everything
The real change for me didn't happen in a workshop or a book. It happened in a conversation.
A mentor — a different one, later in my career — pulled me aside after watching how I operated with my team. He was direct in a way I've tried to be with people ever since.
"You're limiting everyone around you," he said. "They'll never grow as long as you're the one with all the answers."
I wanted to argue. Instead, I sat with it. And I realized he was right. I was so busy being indispensable that I'd made everyone else dispensable. I wasn't building a team. I was building a dependency.
So I started doing something uncomfortable: I stopped answering questions. When someone brought me a problem, I asked what they thought we should do. When someone made a mistake, I asked what they'd do differently next time. When I knew the faster path, I often let the team find the longer one — because the lesson was worth more than the time.
My team got stronger. Decisions got faster. Problems got solved without me. People started leading themselves.
It was not a comfortable process. But it was the right one.
What My Mentor Was Really Saying
Looking back, I understand now what he meant that day — the thing I nodded at and moved past.
Technical skills get you in the room. They're the cost of entry. But staying in the room, earning the trust of the people you lead, building something that lasts beyond your own involvement — that requires a completely different set of tools.
Developing emotional intelligence doesn't dilute your technical expertise. It gives it a platform. Without the ability to connect, to build trust, to create an environment where people want to do their best work, your best ideas will die quietly — killed by a lack of buy-in or a culture that never quite cohered.
Leadership begins at the moment your focus shifts from yourself to the people around you. That shift doesn't happen automatically when you get the title. It's a decision you have to make, often more than once.
I was lucky to have people who told me the truth before I ran out of time to act on it.
The transition from technical expert to leader is one of the most disorienting moves in a career — and one of the most important. If you're in the middle of it, or about to be, I'd be glad to talk. Schedule a conversation.