What should you do when a manager will not change?

A manager who will not change requires a role decision, not an indefinite extension of coaching. If specific feedback, practical support, and a fair test do not change the work impact, reduce authority, narrow scope, or appoint another manager. Tell the team what has changed, protect people from retaliation, and do not wait for resignations to make existing evidence feel undeniable.

How do you know coaching has reached its limit?

Review the agreement, not your hope. The manager received specific examples, understood the expected behavior, had suitable support, and encountered comparable situations. If rollback decisions still miss their windows, concerns are still interrupted, and engineers still seek unofficial authority, the work result has not changed.

Do not reset the coaching period after every new explanation. There will always be context: a difficult release, an inexperienced team, a demanding executive, or a sudden incident. Management exists inside pressure. The question is whether the manager can create enough clarity and safety under normal pressure for the team to function.

Ask whether another month is likely to produce new information. If it only produces more examples of the established pattern, continued observation transfers the price of your uncertainty to the team. Make the role decision with the evidence you have.

What role options should you consider?

Narrow scope when the manager can lead a smaller area but cannot coordinate the current breadth. Remove approval rights that create avoidable bottlenecks. Add explicit delegates for release and incident choices. Define the new boundaries clearly so the team does not continue seeking permission from the old route.

Move the person to work that uses their strengths without people authority when that option genuinely fits. A strong technical contributor may be more effective as an architect or specialist. Do not present the move as a secret management role where influence remains unchanged and the new manager cannot act.

Replace the manager when the core relationship of authority is damaged or when change has not appeared despite support. Plan continuity for decisions, 1 on 1 conversations, performance responsibilities, and active delivery. Speed matters, but an unnamed temporary structure can recreate the same confusion.

How should you make the decision fairly?

Use documented behavior, impact, support, and response. Confirm that expectations were clear and that the manager had an opportunity to provide context. Apply company policy consistently and involve the appropriate people partner or legal support. Fair process strengthens a direct decision; it should not become a reason for endless delay.

Separate value as a person from fit for authority. The manager may have tenure, important relationships, or earlier achievements. Those facts deserve respect and do not erase current impact. A role carries present duties. Leadership must decide whether those duties are being met now.

Avoid bargaining with future attrition. You already know that work stalls and voice is suppressed. Waiting until a valued engineer resigns adds no useful diagnostic fact. It merely converts an operational pattern into an expensive loss.

What should you tell the team?

Tell people the operational change as soon as it is settled. Name who owns decisions, who conducts 1 on 1 conversations, and where concerns should go. You do not need to disclose private employment details. You do need to remove uncertainty about authority.

Acknowledge that the previous arrangement caused difficulty without inviting a public trial. You can say that decision flow and the working relationship were not meeting the standard, so leadership changed the role. Thank people for raising specific concerns and state how retaliation will be handled.

Do not claim the problem is solved on the announcement date. Ask people to judge the new structure through work. Return after several weeks to check whether risks surface earlier, approvals arrive in time, and unofficial workarounds are disappearing.

What if senior leaders resist acting?

Ask what evidence they believe is missing and what decision that evidence could change. Put an owner and date on the answer. If leaders acknowledge the impact but prefer to wait because of tenure or relationships, name that as a choice rather than continuing to call it investigation.

Do not send employees back to manage up, document forever, or reduce their own effectiveness so the damage becomes visible. Those tactics ask people with less authority to manufacture a crisis. Present the existing delivery, quality, and voice costs to the decision makers and recommend a concrete role change.

If your authority is limited, be honest with the team about what you can protect and what you cannot change. Do not expose private leader discussions, but do not promise action that is not coming. Honest constraints let employees make informed career and project choices.

Which response fits the continuing impact?

Choose based on the pattern rather than the least uncomfortable option. Delegation will not repair retaliation. A smaller team will not help a manager who rejects any self examination. Match the remedy to both capability and risk.

How do you carry out the transition?

1. Confirm policy and decision authority.
2. Select the new role or manager.
3. Define temporary decision ownership.
4. Speak privately with the manager.
5. Communicate operational changes to the team.
6. Protect current speakers from retaliation.
7. Review work flow after several weeks.
8. Repair systems that allowed the pattern to persist.

Prepare for mixed reactions. Some employees may feel relief, others loyalty, and others concern about instability. Do not ask the team to agree on the manager's character. Give them a reliable structure and invite questions about work, support, and the transition.

What should leadership learn afterward?

Review why the pattern lasted. Perhaps skip level meetings focused only on status, decision delays had no owner, or employees lacked a safe route around their manager. A replacement without a stronger listening system can leave the same early signals invisible.

Examine appointment criteria. Tenure, technical strength, and trusted relationships do not automatically predict useful people management. Future selections should include evidence that the person can receive dissent, make timely decisions, inspect their own contribution, and help others work when plans fail.

Close the loop with those who spoke. Explain which operational changes resulted from their evidence and thank them without making them responsible for the employment decision. Then keep observing. Trust returns when the organization responds consistently over time, not when a single manager leaves.

Finally, watch the new manager's incentives. If senior leaders still reward quiet status reports and punish bad news, a capable replacement will face pressure to recreate the old pattern. Make early risk, delegated judgment, and honest correction visible leadership expectations. The team needs a different system around the role, not only a different name inside it.

How do you protect the team while the role changes?

Remove the most risky authority first. If release decisions are blocked, publish a temporary approver. If performance feedback has become retaliatory, add review and prevent unilateral action. If incidents become chaotic, name another incident leader. Interim controls are not a final structure, but they reduce exposure while formal steps are completed.

Watch workload. Teams under a difficult manager often carry hidden coordination that becomes visible during transition. The staff engineer may already be making decisions, mentoring colleagues, and explaining plans upward. Do not simply make that burden official without removing other work, granting authority, and providing support. A rescue assignment can otherwise create the next burned out leader.

Preserve necessary records and handoffs. Active commitments, performance obligations, hiring decisions, and customer risks need named owners. Keep the transfer focused on work rather than inviting a final argument about the manager's character. Clear continuity protects both the team and the person leaving the role.

Monitor subtle retaliation or loyalty tests. A manager who retains another position may still influence assignments, reputation, or access. Tell employees where to report concerns and check proactively rather than waiting for a formal complaint. Also prevent coworkers from treating anyone who defended the manager as disloyal. The goal is a functioning team, not a winning faction.

Give the new manager an accurate but bounded briefing. Explain decision failures, hidden routes, and current protections. Do not hand over a list of supposed troublemakers. Ask the new leader to observe and build direct relationships. The transition should end the habit of sorting the team into supporters and critics.

Set a date to review whether the remedy fits. Delegation may clear approvals but leave fear untouched. A new manager may restore voice while inherited process gaps continue to slow delivery. Ask about both relationship and work flow. Adjust the structure based on current evidence rather than assuming that the personnel action completed every repair.

Recognize that trust may recover slowly. Employees who were ignored before may wait to see whether the new route survives a difficult release or disagreement. Do not demand visible enthusiasm. Provide consistent decisions, respond to concerns, and let ordinary experience change expectations. Leadership earns closure through reliable behavior after the announcement.

What are common questions?

Related: a team afraid of their manager, coachable or damaging, investigate a manager complaint.

Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.