It started as one of those totally normal workplace moments: a new hire joins, you get tapped to onboard them, and you do it because you’re competent and, frankly, because you’re a decent human. For weeks, one employee says, they walked the new teammate through systems, introduced stakeholders, reviewed drafts, and answered the kind of questions that only come from someone learning which button not to click. The payoff was supposed to be simple: the team gets stronger, and the trainer earns credibility for making it happen.
Instead, the payoff landed sideways. In a move that felt like a plot twist written by someone who’s never actually had a job, the boss named the new hire the project lead—on a project the trainer had been doing the heavy lifting to launch. When the trainer asked about it, they were told they should “be proud to support their growth.”
A promotion no one saw coming (except maybe the boss)
According to the employee, the new hire had been on the team for only a short stretch when leadership announced the change. The project was already in motion, with plans drafted, risks logged, and key relationships warmed up—much of it facilitated by the person who’d been training the newcomer. If this were a relay race, the trainer ran the first three legs, then got told their job was to clap loudly from the sidelines.
What stung wasn’t just losing the lead role. It was the framing: the boss positioned it as a character-building opportunity, like being passed over was a surprise bonus perk. “Be proud” can be a nice phrase, but in this context it sounded like: please don’t make this awkward for me.
The quiet workload behind “training”
Most companies talk about mentorship like it’s a feel-good extra, something you sprinkle on top of your “real” work. In reality, training someone new is real work—often the hardest kind. It’s mentally taxing, it slows your own output, and it requires you to translate all the invisible expertise in your head into something another person can actually use.
And it’s not just teaching tools. It’s teaching context, politics, timelines, and the difference between “this is a draft” and “this is the version the VP will forward to the CEO.” When you do it well, it’s almost designed to make you look replaceable: the new hire gets better, the process stabilizes, and suddenly your contribution is hard to point to in a single screenshot.
Why this kind of decision hits a nerve
Workplace experts often describe this as a classic recognition gap: the person who enables success isn’t always the one who gets credit for it. Companies love outcomes, but they’re inconsistent about rewarding the infrastructure that produces those outcomes. Training, documenting, steadying a project, smoothing stakeholder friction—those are the bones of good work, even if they don’t sparkle in a status update.
There’s also a power dynamic baked in. When a manager says you should be “proud to support,” it can sound less like appreciation and more like a polite instruction to swallow disappointment. It puts the employee in a tricky position: object and risk being labeled “not a team player,” or stay quiet and teach the organization that this move is acceptable.
Possible motives: strategy, optics, or plain old mismanagement
To be fair, there are scenarios where putting a newer employee in a lead role could make sense. Maybe the new hire has specialized experience from a prior company, or the organization is grooming them for a specific track. Sometimes managers also reshuffle leads to balance workloads, especially if one person is nearing burnout.
But even when the decision is strategic, the communication matters. Dropping it without acknowledging the trainer’s effort can feel dismissive, and framing it as a “growth” moment for someone else can be salt in the wound. If the boss genuinely valued the trainer, they’d likely say so plainly—and tie that value to opportunities, not just feelings.
The social fallout no one puts in the project plan
Moves like this can shift a team’s mood fast. The person who trained the new hire may feel less motivated to share knowledge next time, because they’ve learned that generosity can be converted into someone else’s title. And coworkers notice, even if they don’t say anything out loud.
It also puts the new lead in an awkward spot. If they’re smart, they’ll realize they were handed authority that someone else helped build, and that can create tension from day one. Nothing says “collaboration” like starting a leadership role with a silent cloud of resentment hovering over the kickoff meeting.
What employees are saying: “Support” is not a career plan
In conversations across workplaces, people are increasingly skeptical of vague praise that isn’t paired with concrete advancement. Being told you’re “valuable” is nice, but it doesn’t pay more rent or put your name on the performance review bullet that matters. When leaders lean on emotional language—“be proud,” “be excited,” “be a team player”—employees often hear, “Please accept less than you earned.”
This is especially touchy in environments where promotions are scarce and visibility is currency. Project leadership can be the difference between “solid contributor” and “next in line for manager.” Losing that chance can feel like losing a rung on the ladder you were already climbing.
What a better version of this could’ve looked like
If leadership truly wanted the new hire to lead, there were cleaner ways to do it. They could’ve named the trainer as program owner or senior lead and positioned the new hire as deputy lead, gradually handing off responsibilities. Or they could’ve split leadership: one person owns strategy and stakeholders, the other owns delivery details and coordination.
Even simpler, the boss could’ve acknowledged the trainer’s contribution in the announcement. A few specific sentences—what they built, what they taught, how they set the project up for success—wouldn’t fix everything, but it would show basic respect. People can handle disappointment better when it’s not wrapped in a bow of pretend gratitude.
The bigger takeaway: promotions reveal what a company really values
Organizations say they value mentorship, collaboration, and knowledge sharing. Then they reward the most visible role instead of the person who made the visible role possible. Over time, that teaches employees to protect information, avoid training others, and focus on optics—because optics are what get promoted.
And that’s the irony: the boss wanted “support for growth,” but the decision may shrink the team’s willingness to support anyone. If you want people to build others up, you can’t punish the builders. You have to reward them in ways that show you actually noticed.
For the employee who trained the new hire, the next steps depend on context—how often this happens, whether the boss can be reasoned with, and whether there’s a path forward internally. But one thing is clear: being told to “be proud” isn’t recognition, and it’s definitely not a substitute for opportunity. If pride is the only compensation on offer, it’s fair to start shopping around for a workplace that pays in more than vibes.
More from Willow and Hearth:
Leave a Reply