Her New Manager Arrived With No Experience — Then She Refused to Spend Another Day Training Someone She Was Now Reporting To

Photo credit: AI-generated image created using ChatGPT. Illustrative only.

After nearly a decade of climbing the ladder at her workplace, a woman thought she was finally being lined up for the top job—until the board quietly picked someone else and then told her she’d be responsible for teaching that person how to do it.

She’d been with the organization for a little over nine years, starting as a receptionist and eventually becoming a Regional Director. Along the way, she says, she held “almost every role” and built much of the internal infrastructure that kept the place running: a database, workflows, standard operating procedures, onboarding materials, and budget trackers.

So when her Executive Director announced a sudden retirement, it didn’t feel like a reach that she might be next. She’d already been training at that level for the past couple of years, she says, and there had been an understanding she would step in as interim and possibly transition into the role permanently after a probationary period.

A retirement turned into a scramble, and the board took over

The leadership change wasn’t happening under normal circumstances. The outgoing Executive Director’s wife had unexpectedly died, and after that loss he decided to retire with only a couple months’ notice.

At first, the transition sounded straightforward: she would fill in, keep things steady, and potentially move into the role for good. But when the retirement was formally announced, she says she was called into a meeting the following week and told the board wanted to run a “formal procedure” to fill the Executive Director position.

She applied. Then nothing happened—at least nothing that staff could see. She says employees, including her, were “kept in the dark,” and she never even heard back about whether she’d be interviewed.

Three months of silence ended with a single email

Nearly three months later, she says, an email finally went out to staff: a new Executive Director would start on the 1st.

There was no warning meeting, no explanation about the process, and no acknowledgment that internal candidates had applied. After years of being embedded in the organization’s daily operations, she was left finding out the same way everyone else did.

Then, a board member came into the office and met with her in person. After some small talk, she asked directly why she hadn’t been considered for an interview.

The board told her she wasn’t qualified—then asked for her expertise anyway

The board member’s answer landed hard. She says she was told the board decided she didn’t have the qualifications for the Executive Director role.

She describes feeling stunned and hurt, which is understandable given the years of work and the training she believed had been preparing her for that level. But the conversation didn’t stop at rejecting her candidacy.

Instead, she says the board member pivoted to what they still needed from her: because she had the most institutional knowledge, she would be “perfect” to help onboard and train the incoming Executive Director. The new hire, she was told, was transitioning not just into the organization, but into a new field of work, and would need to be “fully trained.”

That training wasn’t framed as a quick orientation. She says she was told to expect 5–10 hours a week starting in April dedicated to preparing the new Executive Director to do the job she’d been told she wasn’t qualified to hold.

She said no, and the board member said it wasn’t optional

In the moment, she refused. Her reasoning came out bluntly: if she didn’t have the qualifications to do the job, she argued, she shouldn’t be responsible for training the person who did.

That response, she says, was immediately labeled an overreaction. The board member told her, “There’s no need to overreact because it’s not really optional.”

Then came a list—documents, projects, contracts, budgets, databases, policies, and procedures that the new Executive Director would need to be oriented on. She says she “shut off” mentally after that, went home, and started questioning whether she’d handled it wrong. She later shared the details in the original post, asking others if refusing to train her new boss made her unreasonable.

But her bigger fear was sitting right under the surface: the organization had effectively signaled it didn’t see her as leadership material, while also treating her as indispensable labor for the incoming leader’s success.

Reactions centered on boundaries, leverage, and getting it in writing

Although the post focuses on her account rather than a long list of responses, the dilemma itself tends to pull people into practical, workplace-minded angles: what exactly is she required to do, and what happens if she doesn’t?

A common focus in situations like this is documentation—asking for the training expectations in writing, clarifying whether those 5–10 hours are added on top of current duties, and confirming who is authorizing the workload. When a board member says something “isn’t optional,” it raises the stakes, because it implies discipline could follow if she refuses.

Another point people often latch onto is compensation and scope. Training an Executive Director is not the same as showing a new coworker where the files are. If she’s being asked to transfer operational knowledge she spent years building—systems, budgets, procedures—then she’s being asked to do high-value work without the title or authority that usually comes with it.

And then there’s leverage. She’s the one who created the database, workflows, SOPs, and onboarding procedures. She knows how things actually run. The board’s decision may have placed her beneath a new leader, but it also revealed how dependent the organization is on what she knows.

The hard part is what comes next: train, refuse, or walk

Her story ends in an uncomfortable place: she’s still employed, still reporting to the organization that passed her over, and still facing pressure to train the person placed above her.

If she complies, she risks cementing a dynamic where her expertise is treated as a utility while her advancement is capped. If she refuses, she could be painted as uncooperative or “overreacting,” especially if leadership is already defensive about the hiring decision.

And if she chooses to leave, she may be walking away from nine years of progress and a workplace she helped build—but she’d also be stepping out of a setup where her value is acknowledged only when it’s convenient.

For now, the tension is unresolved: an experienced internal leader has been told she’s not qualified to lead, but qualified enough to teach someone else to do it. The next few weeks—especially once the new Executive Director arrives—will likely decide whether this becomes an awkward onboarding phase or the moment she realizes the job she’s been doing for years no longer has a future there.