Skip to main content

The Power of Trust: A Lesson from Building a New Team

Intro:

In our previous post New Role, New Team, and New Challenge, I mentioned the challenges I faced while stepping into a leadership role for an existing team. If you haven't read it yet, please check it out. In this post, I'll share the challenges I faced while setting up a new team from scratch.


Pre-Context:

Immediately after taking on the leadership role, I was tasked with setting up a team with just a couple of people.

For the role, we screened over 100+ candidates and interviewed around 70 candidates. Only two of them made it to the final round, and eventually, just one candidate with 2 years of experience was selected.


Context:

The selected candidate joined a month later. For the first two weeks, he studied Java, its internals, and our company-specific frameworks. In the following two weeks, he underwent knowledge transfer. He completed everything with below average score, and we assumed he would perform strongly once onboarded to the project.

But that didn't happen.

Despite our expectations, his performance was consistently below average even when we provided him with clear use cases and documentation. At times, we had to explain basic use cases line by line. We suspected he might have faked his interview, but after reviewing the recordings, we found no such indication. Over the next few months, his performance barely improved, despite regular one-on-one meetings and guidance.

Then, one fine day, he came up with a brilliant feature idea which could have a significant impact on our project. At that point, I had two options:

  1. Assign the feature to another developer to ensure quick delivery.

  2. Let him implement it, knowing the release would be delayed.

I chose the second option, and here's why:

  1. The way he conceptualized the idea convinced me that he could execute it and perhaps faster than I anticipated.

  2. I didn't want to demotivate him by letting someone else implement his own idea.

And guess what? He delivered the feature exceptionally well and even released it sooner than I had expected. That moment became the turning point in his journey. From there, his learning curve accelerated, his confidence grew, and he went on to become one of the major contributors in our entire department.


Lesson to all leaders:

As leaders we often face a tough choice between short term results and long term growth. In this case I deliberately chose growth over speed and it paid off. Sometimes all a struggling team member needs is the right opportunity, ownership and trust to unlock their potential.

Not every risk will work out this well, but when we see even a small spark of capability or creativity in someone, it is worth nurturing. By giving them space to fail, learn and own their ideas, we can transform average performers into exceptional contributors.


Comments

  1. Well Said! and Noticed as well! Great Leaders will always choose the option 2 :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Respect Comes Naturally: A Lesson from My Gym Master

The gym I was going to had a master who stood 7 feet tall and weighed around 90 kilograms (198 pounds). He was the perfect role model for a gym master. One day, he got a better offer from another gym and decided to leave. Everyone at our gym felt a little sad about it, but we also knew this was not the end. A new master would eventually come. The very next day, a man around 5 feet tall with a bulky build joined our gym. At first, everyone thought he was going to be a trainee, but to our surprise, he was introduced as our new master. Many members felt disappointed. For newcomers like me, it did not matter much. To us, he was someone who knew more about the gym than we did. But the senior members did not see him as a true master. They believed they were stronger and knew more than him. The new master, however, did not let this bother him. He continued teaching, even though many ignored him. Within a week of joining, he surprised everyone. One day, he began practicing along with senior me...

New Role, New Team and New Challange

When I was promoted as a Team Lead, I had to take charge of one of the existing teams while also setting up two new smaller teams with a few members each. Building a new team comes with its own challenges, but leading an already established team is a completely different experience. The existing team had a few senior members who had been there from the beginning. One of them strongly believed that he knew the product and the codebase better than me. Whenever I delegated tasks to him, he would not prioritize them. If I tried explaining the use cases, he would not listen. Over time, his output dropped significantly. I knew that before my manager noticed this issue, I had to address it. I have always believed that most conflicts can be solved through open discussion, so I invited him for a one-on-one meeting. During that meeting, I understood his perspective and also gathered some feedback from him. I assured him that I would take his feedback seriously and that he would notice changes st...