The short answer
When an Engineering Manager asks you to transfer a failing developer to another department to avoid initiating a Performance Improvement Plan, they are attempting to outsource their managerial duties. Firing or formally coaching a low performer is the hardest part of leadership. The manager is using the excuse of "team morale" to avoid an uncomfortable confrontation, expecting human resources to act as a cleanup crew for their cowardice.
As an Engineering People Manager, you cannot allow lateral transfers of uncoached, failing employees. Passing a low performer to another department is an act of organizational sabotage. It corrupts the talent density of the company, forces another manager to deal with a problem they did not create, and exposes the company to massive legal liability if the employee is eventually terminated without a documented paper trail.
You must explicitly reject this administrative avoidance tactic. You will enforce the requirement for structured performance documentation. By refusing to process the transfer and forcing the manager to initiate the formal remediation process, you protect the broader organization from toxic competence issues. You must force the manager to do the job they are paid to do: manage performance.
Why this question is a trap
The trap relies entirely on the emotional manipulation of "team morale." The Engineering Manager is framing the transfer as a benevolent act that protects the culture of their specific engineering pod. They want you to believe that a formal PIP will create a toxic environment and cause other developers to quit. They are using this hypothetical crisis to intimidate you into bypassing the standard HR protocols.
If you yield to this pressure and transfer the developer, the consequences are disastrous. The developer will arrive in their new department with the exact same performance deficiencies. When they inevitably fail again, the new manager will demand to know why HR transferred a failing employee without a warning. You will look completely incompetent and complicit in hiding bad performance.
Furthermore, granting this transfer trains the Engineering Manager that they never actually have to manage difficult people. They will realize that your department is a dumping ground for anyone they do not want to coach. Every time an employee struggles, they will simply ask for a transfer. You must break this cycle immediately by establishing a hard boundary around performance accountability.
What most people say
Most frontline HR managers panic when a line manager uses the "morale" excuse. They want to be viewed as supportive business partners, so they try to find a quiet compromise. They say something like, "I understand that PIPs are really stressful for the team. Let me see if the QA department has any open headcount where they might be a better fit, and we can just quietly move them over there next week so you do not have to deal with the formal paperwork."
This response is an absolute failure of operational leadership. By agreeing to quietly move the employee, you completely invalidate your own performance management policies. You surrender the company's talent standards simply to help a weak manager avoid an uncomfortable conversation. You essentially lie to the QA department by giving them a failing employee. You have sacrificed your professional integrity and the company's operational efficiency for absolutely zero gain.
What to say instead
"I will not authorize a departmental transfer to bypass a performance issue. Reassigning a struggling developer without a documented remediation process corrupts our organizational talent standards and exports failure to another team. You must deliver the formal Performance Improvement Plan this week, explicitly detailing their coding deficiencies and establishing a clear thirty-day milestone for correction or termination."
This script is a flawless execution of performance governance. You open with a direct, uncompromising refusal. Stating clearly that you will not authorize a transfer to bypass a performance issue stops the demand in its tracks. You do not ask for permission to hold the line. You declare the legal and operational reality of the human resources department.
You immediately diagnose the exact operational damage their demand will cause. By stating that reassigning the developer "corrupts our organizational talent standards and exports failure to another team," you raise the conversation from a minor HR dispute to a serious discussion about corporate integrity. You force the manager to confront the unethical nature of their request. You prove that you are protecting the entire company, not just processing paperwork.
Finally, you dictate the operational path forward. You outline exactly what the manager is actually required to do. You mandate that they deliver the formal PIP this week. You specify that the plan must detail their "coding deficiencies" and establish a "clear thirty-day milestone for correction or termination." You solve the problem by forcing the manager to execute the standard corporate procedure, leaving absolutely no room for avoidance.
The phrase to anchor on
Without a documented remediation process.
How to deliver it
Deliver this response with the cold, immovable authority of a compliance auditor. Your tone must project complete professional detachment and total command of your performance ledger. Do not sound angry that they asked to skip the PIP, and do not sound intimidated by their concern for morale. Treat the interaction as a routine enforcement of management physics.
Maintain direct, unwavering eye contact with the Engineering Manager. When you mention exporting failure to another team, speak slowly and deliberately. You want the ethical weight of that concept to land heavily in the room. When you dictate the requirement to deliver the formal PIP this week, keep your voice entirely neutral. You are making a literal business routing decision to solve their performance problem, not begging for their understanding.
Mistakes that cost you the room
The most fatal mistake is offering to deliver the PIP to the employee yourself. If you volunteer to run the performance meeting because the manager is scared, you instantly lose your authority. You become a proxy for weak leadership. You are the Engineering People Manager, not a hitman. The direct manager must own the feedback and deliver the consequences themselves. Your job is to coach the manager, not do their job for them.
Another critical error is debating the actual impact of a PIP on team morale. Do not say, "Actually, firing low performers improves team morale." While this is true, you will lose a subjective argument about team feelings with the person who manages that specific team daily. Anchor entirely on the policy governance and the lack of a documented remediation process. The rules apply regardless of the perceived emotional impact.
Do not ask the manager to just give the employee a verbal warning instead. A verbal warning without documentation is legally useless and fails to establish the necessary paper trail for termination. Demand the formal, written plan immediately.
Practice plan
First, memorize the exact parameters of your company's approved performance improvement process. You must be able to state the exact requirements for a PIP, including duration, specific goals, and consequences. If you do not have the hard requirements ready, the manager will claim your process is too vague to use.
Second, practice the transition from the hard refusal to the PIP mandate. You must sound entirely comfortable telling a technical manager that their avoidance tactic is rejected while smoothly enforcing the formal solution. Record yourself delivering the script until the cadence sounds effortless and entirely devoid of emotional friction.
Finally, run the drill in the Talk Rightly studio. Focus heavily on keeping your facial expression completely neutral. When a manager makes an emotional plea based on team morale, any sign of anxiety or sympathy will invite them to push harder. You must train your body to remain perfectly still under pressure, projecting absolute certainty in your departmental boundaries.