My Team Feared Me. Here Is What Changed.

Six months into my first Technical Lead role, my Project Manager sat me down and told me something I was not ready to hear: my team feared me. Not respected me. Feared me. That distinction, delivered calmly across a desk in Pakistan, changed the trajectory of my career.

I am sharing this story because leadership failure is common and leadership honesty is rare. Most people who go through what I went through either don't talk about it, or they rewrite the story so that they were always on the right track. I was not on the right track. And the only reason I found one was because someone trusted me enough to tell me the truth.

The Technical Lead Who Commanded

Leadership roles are tricky and demanding in any environment. In Pakistan, at the grassroots level of a fast-growing software company in the early 2000s, the prevailing model was clear: you command, people deliver. Seniority meant authority. Authority meant control. That was the water I swam in, and I absorbed it without question.

When I was promoted to Technical Lead, I brought everything I had — and I had a lot technically. I could solve problems quickly. I could see architectural flaws before anyone else. I could get things done under pressure. The respect I earned for my technical skills was genuine. But the model I used to lead was not leadership at all. It was control dressed in the language of standards.

I demanded perfection. I left no room for mistakes. When someone on my team tried something and it didn't work, my reaction communicated very clearly that failure was not acceptable here. I thought I was maintaining standards. What I was actually doing was extinguishing the will to try. The atmosphere in our workspace was always tense — not because the work was hard, but because I made it that way.

My team was stifled. They were unappreciated. They were overworked and afraid to say so. I could not see any of this, because I was measuring the wrong things. Delivery. Output. Correctness. I was not measuring what was happening to the people delivering it.

The Feedback That Struck a Chord

Around six months into the role, my Project Manager called me in. He was direct. He was fair. He was exactly what a good manager should be.

He said it plainly: your team is not happy, and you are making my choice to keep you as lead questionable. You have to change — not your skills, not your standards, but your behaviour and the way you deal with people.

This struck a chord. I had always believed my methods were effective. I had the metrics to prove it. But metrics had been hiding something. The human cost of my approach was invisible to me — and it had been building for six months before someone finally said it out loud.

Before the meeting ended, he handed me a book. How to Win Friends and Influence People by Dale Carnegie. I went home that night and began reading.

A Book, a Mirror, and a Long Road

The Carnegie book did not teach me management technique. It held up a mirror. Page after page, I recognised my own flaws — the impatience, the assumption that being right was the same as being effective, the failure to understand that people's feelings about their work are not separate from the quality of their work. They are the same thing.

I realised I needed serious, sustained work on my own personality. Not just skill development. Personality. That is a harder thing to admit than a technical gap, because a technical gap feels external. This was internal.

I embarked on what I can only describe as a second education — this time in the human dimensions of professional life. I attended in-house workshops on emotional intelligence. I began learning about the three intelligences that I now believe determine professional growth more than any technical certification:

• IQ — Intelligence Quotient: The analytical capacity I had always prioritised and valued. Necessary, but never sufficient on its own.
• EQ — Emotional Quotient: The ability to recognise your own emotions, understand how they affect your behaviour, and manage them consciously. This was what I was missing.
• SQ — Social Quotient: The ability to read and navigate the emotional landscape of a group — to understand what a team feels collectively, not just what individuals say.

Through the workshops and through deliberate practice, I began to develop self-awareness that I had never had before. I learned to identify my triggers — the situations that made me reactive, controlling, and impatient. I practised responding rather than reacting. I practised staying calm when my instinct was to assert myself. I practised silence when I had previously filled every silence with a directive.

I learned that composure is not weakness. It is the most powerful signal a leader can send to a team under pressure.

From Command to Collective

The shift did not happen overnight. But it was real, and it was measurable — not in output metrics, but in the atmosphere. The tension that had defined our workspace began to lift. People started offering opinions they had previously kept to themselves. Junior engineers started asking questions instead of just executing instructions.

I realised the importance of empathy and began practising active listening. Not listening to respond — listening to understand. I encouraged open communication. I stopped treating my own conclusions as the only valid ones. I moved from the belief that I, as the lead, should have the answer, to the belief that the best answer should prevail — regardless of where it comes from.

I started mentoring — not just supervising. There is a fundamental difference. A supervisor ensures the work is done. A mentor ensures the person doing the work is growing. I began investing time in junior engineers, in new hires, in the people who were most likely to be afraid to ask for help. That investment paid returns I never saw from any amount of technical perfectionism.

My leadership philosophy shifted from a command-and-control model to something I can now articulate clearly: collective wisdom, collective decision-making, collective ownership. When a team owns a decision together, they defend it together, and they learn from it together. That is how engineering cultures grow.

What I Focused On From That Point Forward

After Dale Carnegie, I kept reading. Adam Grant. Simon Sinek. Robin Sharma. Each book opened a new angle on what leadership and human growth could look like. The reading has never stopped. Neither has the work.

Find a Mentor. It Will Change Your Course.

The growth — IQ, EQ, SQ — is still ongoing. It will continue for the rest of my life. I have come to see lifelong learning not as a discipline I impose on myself, but as the natural consequence of staying curious and staying honest about where I am falling short.

But the most important point in all of this is not a book, or a workshop, or a framework. It is this: you need someone trustworthy enough to point out your mistakes. And when they do, you need the courage to recognise them and the will to correct them.

That is rare. A manager who trusts you enough to be honest with you, rather than managing around your flaws, is a blessing. A mentor who believes in your potential more clearly than you do is a rarer one. I have been fortunate to have both, at different stages of my career.

If you have a mentor, treasure that relationship. If you do not have one — find one. Not because it is good career advice, but because it will change the course of your life in ways you cannot predict from where you are standing now. I owe my growth to every mentor who believed I was worth the honesty.