A team that is hostile to a new manager almost never rejects the person: it is defending a way of working and processing a loss. Legitimacy is built in three moves — understand before deciding, hold a very small set of non-negotiables, and deliver an early concrete win that visibly benefits the team.
TrustLeader Editorial TeamUpdated
You are replacing a well-liked manager who left after eight years. Meetings are polite and empty. Véronique, fifteen years on the team, punctuates your decisions with «with the old manager, we did it differently» and routinely double-checks your instructions with someone else. Information reaches you after the fact. Nobody is openly aggressive, which makes this harder to address than a straight conflict: there is nothing to correct, and yet you have no real grip on what gets decided.
You are being assessed against criteria you do not know, set by someone who is no longer there. Two opposite strategies fail symmetrically: staking out territory with fast changes confirms the fear that you will destroy what worked, while a purely accommodating posture installs you as a caretaker nobody takes seriously. Add the time factor: your margin for error is concentrated in the first few weeks, exactly when you know the least.
Changing rituals, scopes or tools before understanding why they exist produces lasting rejection. Every rule in place was written by an incident; until you know the incident, you are deleting an answer without knowing the question.
Any dig at the previous manager attacks, by ricochet, eight years of the team’s work with him. You place yourself on one side of a line and stay there. Visible respect for what came before is the entry condition, not a courtesy.
Multiplying friendly gestures and avoiding every unpopular decision for three months reads as weakness and extends the testing period instead of closing it. A hostile team is testing solidity, not likeability.
Calling in your most critical team member for a formal correction in week three makes them a martyr and unites everyone else against you. That person is usually the best-informed member of the team: a resource before they are an obstacle.
Without a concrete demonstration, the testing period does not fade — it settles in. After three or four months the team has reached its conclusion, and reopening the file costs far more than dealing with it early.
Within the first two weeks, no exceptions: «What works here that I must not break? What has annoyed you for a long time? What do you expect from me?» Write everything down. These conversations give you both the map of the terrain and your first list of useful projects.
Do not avoid them; recruit them explicitly: «You know this team better than I do. I need you to tell me what I’m about to break without seeing it.» You convert a position of opposition into a position of expertise, which is both sincere and effective.
Take from the one-to-ones a problem everyone has endured and nobody has solved, then actually solve it. A useless meeting removed, a tool obtained, a decision finally made: that demonstration, not your stated intentions, is what establishes your usefulness.
Announce them early and hold them without exception: «What won’t change with me: commitments to clients get kept, information comes up, people are treated with respect in meetings. On everything else, I’m learning and I’m listening.» A small non-negotiable surface, rigorously held, produces more authority than a long list defended weakly.