"Why Did He Get Promoted Faster Than Me?" The Workplace Truth I Understood Only After Five Years

You may have had this same confusion:

That colleague doesn't work overtime, doesn't fight for tasks, and is only slightly above average technically, yet the leader values him especially. The interns he mentors can work independently within six months, project handovers never break down, and after switching teams he runs even more smoothly.

Meanwhile, you stay late fixing bugs, independently carry the project rhythm, and still your name is missing from the promotion list.

Why is that?

📊 A set of data may explain part of it:

85% of professionals believe the key to promotion is "strong ability," but surveys show that among the top 20% fastest-promoted people, only 23% are the strongest technically in their team.

The people who truly rise fast are often not the most capable ones, but the ones who make others more capable.

These people have a name: Force Multiplier.

▌The quiet team lead: Why do his team members always stand out?

I once led a team where there was a team lead who, to be honest, didn't talk much and didn't like to show off.

But strangely, almost every newcomer under him grew extremely fast. His team went through two waves of people, yet core metrics kept climbing.

What impressed me most was a project retrospective. Everyone was saying this feature was "their own idea," but after asking around, it turned out the ideas were all quietly guided step by step by that team lead.

He doesn't stand in the C position, but he always makes others shine.

When the leader evaluated him, he said only one sentence:

"After he leaves, the team can still keep running."

He is not the most capable one, but he is the one who makes the whole team able to run.

▌An experiment with two newcomers: The difference between leading "hands" and leading "brains"

I once mentored two newcomers with similar backgrounds and abilities.

The first one I mentored in a traditional way: I sent him standard templates, broke down requirements while explaining, and marked all review points. He worked very fast and almost never made mistakes.

For the second one, I did only one thing: I talked through his thinking with him. Before every requirement review, I would ask:

• What angle are you planning to approach this from?
• What do you think is the point most likely to be challenged in this plan?

At first he stumbled through his answers, but after three months, he began to independently analyze tradeoffs and even suggest optimizations. Six months later, he mentored a new intern, and the entire process was designed by himself.

I realized that the first one I trained had fast hands, while the second one I trained had judgment.

It's not that I mentored particularly well, but rather: Mentoring is not about copying your answers, but about replicating their thinking models.

▌How did one sentence of praise at a standup change an intern's trajectory?

Once a project handoff went especially smoothly, and I mentioned at the standup: "The interface documentation is organized so smoothly, Shelley's organization was quite critical."

Shelley was originally the quietest person in the team, and she even doubted whether she could pass probation.

Two weeks later, she was borrowed by another team and was specifically praised for "especially good collaboration and strong documentation skills."

She later told me: "That was the first time I felt I had a bit of 'presence'."

The moment you mention someone else's contribution may be a turning point in their career.

And this is precisely the most powerful ability of a force multiplier: amplifying the value of others.

▌You just haven't crossed the hurdle of carrying everything alone yet

I have also fallen into this trap myself.

When I first became a tech lead, I did almost everything personally. I tracked requirements myself, gave reviews myself, and even edited comments in code reviews.

The result: I was exhausted, team members were idle, and the team became my personal outsourcing team.

The most painful moment was when a team member wrote in 360 feedback: "Leader helped me a lot, but I'm not sure whether I can independently complete a similar project myself."

Doing more does not mean leading well.

Later I changed my strategy: I no longer handled requirements entirely myself, but first listened to the other person's thinking. After every project launch, the team meeting had to be led by the main responsible colleague for the review.

It was slower and messier, but they began to be able to run on their own.

And that same year, I got promoted again.

▌How to become a force multiplier? Try this three-day challenge list

✅ Day 1: Mention someone's name. At the next standup, find a specific opportunity to praise a team member. Remember to name the person + name the contribution.

✅ Day 2: Replace advice with questions. When you want to say "this logic is wrong," change it to "Where do you think users will get stuck if they enter from here?"

✅ Day 3: Do a live thinking session. Are you writing a proposal? Share your screen and talk through how you structure it and how you judge tradeoffs. Even if no one watches, it can become a treasure for future onboarding.

▌Ending · Leave an echo for those who have lit you up

I believe you have also been lit up by some "force multiplier":

They may not be your leader, but they can always ask the question that suddenly opens your mind. They may not do better than you, but they always leave the spotlight to you. They may have already left the company, but you still remember to this day how they helped you open your thinking and tear away your fear.

If someone like that comes to mind, find a chance to tell them directly: “Thank you for lighting the way for me.”