The restructure is done. Two teams have become one, three roles have changed, and the consultation the team was promised turned out to be a briefing. Or a decision everyone was told was final has been reversed, and nobody explained why.
The manager in the middle often didn’t make the call. They’re still the one the team looks at on Monday morning. For L&D, this is one of the most common moments where a manager needs help and gets a slide deck.
What actually breaks in a team after a difficult change?
Usually not the team’s view of the change itself. People can accept a decision they disagree with. What breaks is their confidence in what they were told and in whose interests were being weighed.
Trust is someone’s confidence in you with something they care about. After a badly handled change, two of the five Trust Questions tend to go open at once:
- Do they believe what I say? “We were told nobody’s role would change.”
- Do they believe I act with their interests in mind? “Nobody asked us.”
That pairing matters for how you develop managers through it. Communication training aimed at “explaining the change better” addresses neither. The team doesn’t need a clearer version of the message. They need evidence that what they’re told now is true, and that they’ll be involved next time.
Can the organisation fix this for the manager?
Partly, and the manager can’t fix all of it alone either.
Nicole Gillespie and Graham Dietz set out a framework for repairing trust after an organisation-level failure. Their argument is that every part of an organisation, including its leadership, shapes how trustworthy employees judge it to be, so each part can contribute to the failure and to the repair. They propose four stages: an immediate response, a diagnosis of what went wrong, reforming interventions, and evaluation. It’s a theory rather than a tested programme, and it’s written for organisations, not individual managers.
The useful point for L&D is the systemic one. A manager who repairs well inside a system that keeps repeating the failure will be undercut. A system that fixes its process while managers carry on as before will be undercut too. Repair research is also younger than most people assume. Kurt Dirks, Roy Lewicki and Akbar Zaheer described it in 2009 as a small but growing body of work, spread across disciplines, and there’s still no tested script for this.
What the manager does control is the part the team sees every day.
What should the manager say first?
Name what happened, in plain words, before anything else.
“We said nobody’s role would change. Three roles changed. I knew some of that earlier than I told you, and I should have said.” That’s harder to say than “I know things have been unsettling”, and it’s the only version that gives the team something to hold.
Two behaviours do most of the work here:
- Share relevant information openly, not selectively.
- Explain the reasoning behind decisions that impact others.
If there’s something the manager can’t share, they say so. “I can’t talk about individual roles yet. I can tell you when I’ll be able to.” Confidentiality is legitimate. Pretending there’s nothing behind the curtain isn’t.
The manager also doesn’t have to defend a decision they didn’t make, or pretend to agree with it. Separating the decision from how it was handled is honest, and it stops every question about the change being treated as disloyalty.
What will be different, and what won’t?
Be specific, and promise only what’s in the manager’s own hands.
A manager often can’t promise there’ll be no more change. Saying so is part of the repair. What they can promise is how they’ll handle the next one: when the team will hear, who’ll be asked, and what they’ll be told if something can’t be shared.
This is where “Only agree to what you can realistically deliver and control” stops being a planning habit and becomes a trust behaviour. One over-promise in the week after a restructure costs more than it would at any other time.
Why should the next promises be small?
Because small promises are the ones you can keep, visibly, soon.
In Maurice Schweitzer’s studies, what restored trust after untrustworthy behaviour was a consistent run of trustworthy actions. A promise helped at first but didn’t carry recovery on its own. That was a laboratory game with young participants, not a team after a restructure, so it gives a direction rather than a timetable.
In a team, the run of actions looks ordinary:
- The weekly update happens on the day promised, including the week there’s nothing new.
- The question raised on Tuesday gets an answer by Friday, even if the answer is “not yet, and here’s why”.
- The next rota or workload decision involves the people it affects. “Involve people in decisions that affect them.”
- When something slips, the team hears before they find out. “Give updates on progress and raise issues early when there are risks or delays.”
None of it is dramatic. That’s the point. The team is watching for whether what’s said matches what happens, and small promises give them lots of chances to see that it does.
How can L&D help managers do this?
Not with a one-off workshop on leading change. The moment where it matters is weeks after any session ends.
Help the manager choose one behaviour to practise with their team over the following month, the one that answers the question the team is most clearly asking. Have them rehearse the first conversation somewhere the stakes are low, with a peer or a coach, so the plain sentence isn’t being said for the first time in front of the team. Practising before it matters explains why. Then ask them to write down each small promise and whether they kept it, so there’s something specific to review.
If you use the Trust Leader Hub, this is the kind of focus a manager would set and practise in the flow of work. Their reflections are the manager’s own view of how it’s going, not a measure of the team’s trust.
How will the manager know it’s working?
Not from a pulse survey in week two.
The signs worth noticing are behavioural. Questions get asked in the meeting rather than afterwards. Someone raises a worry early instead of waiting for it to become a grievance. People stop checking whether the update is “actually true this time”. Those are things a manager can observe and write down, and they’re still the manager’s reading. The only way to know how the team sees it is to ask them, and to accept the answer.
Some confidence won’t come back, or will come back narrower than it was. That’s the team’s call to make, not the manager’s.
When this isn’t the manager’s job
If a change involved formal consultation, redundancy or a grievance, those routes come first and nothing here replaces specialist HR or legal advice. And a manager shouldn’t be asked to absorb blame for decisions taken above them. Repair at team level works best when the organisation is doing its part too.
The research below supports the general direction: repair after an organisational failure involves more than one level, and behaviour afterwards matters more than promises. The manager’s moves are Trust Leader’s recommended practice, not a tested method, and none of these studies test the Trust Leader approach. Reviewed 4 October 2026 by Scott Hunter.