A new manager takes over a team. In the first week, they ask for things and the things happen. Reports arrive on time. People turn up to the meetings. Nobody pushes back. From where the manager sits, it looks like the team is with them, and it’s tempting to read that as trust arriving quickly.
It usually isn’t. What’s arrived is compliance, and compliance is a much cheaper thing to get. People are doing what the role can make them do. Whether they have any confidence in the person holding the role is a separate question, and the early quiet doesn’t answer it.
Four words that get used interchangeably
Authority is when people do what you say because of your position. The title, the reporting line, the fact that you sign things off. It’s real and it’s useful, but it belongs to the role, not to you. Anyone in that chair would have it.
Compliance is what authority reliably produces: the requested behaviour, delivered. It tells you the instruction was followed. It tells you nothing about what anyone believes.
Influence is when people are more willing to move because they see value, meaning or a reason that makes sense to them. It doesn’t need the title. You can influence people who don’t report to you at all.
Trust is someone’s confidence in you with something they care about. Not confidence that you’re senior. Confidence that if they rely on you with something that matters to them, they’ll be alright.
These come apart constantly. Authority can produce complete compliance with no confidence behind it: people do what they’re told and privately expect it to go wrong. Influence can exist with no authority at all, which is why the person everyone actually listens to is often not the one with the biggest title. And trust comes only from what people repeatedly experience of you. A role can lend it to you. It can’t make it stick.
The loan that comes with the title
When a team extends confidence to a new manager on day one, that confidence is borrowed — from the role, the appointment, the organisation’s judgement in hiring them. Borrowed trust does a real job: it gets you a hearing you haven’t personally earned yet. But it’s a starting balance, not an income, and the first real test decides which way it moves. If what people experience matches the confidence they extended, it starts converting into the direct kind. If it doesn’t, it drops fast, and it can take some of the role’s credibility down with it.
What the gap looks like from inside a green report
Back to the project the manager inherited. Everything looks healthy. Updates on time, status green, no problems raised.
What’s actually happening is narrower. The team has learned to do what’s asked. The update goes in because the update is required. It’s marked green because green gets waved through and red invites a difficult conversation with someone they don’t yet know well enough to risk it with. There’s a developer who’s fairly sure a key deadline is going to slip. But it’s week two, the new manager is an unknown quantity, and flagging a risk early feels like volunteering to carry bad news to someone who might shoot the messenger. So she says nothing. The status stays green.
Every visible signal is good. Measured on whether they did what they were told, this team would score full marks. And all of it sits on top of a problem that’s growing precisely because nobody has enough confidence in the manager to bring it to them early.
The moment that decides it
Suppose the developer takes the risk. Week three, she mentions, carefully, that the integration work might not land on time.
That moment is worth more to the manager than a quarter’s worth of green reports, and what they do with it will have travelled round the team by the end of the day. If the response is irritation — why am I only hearing this now, whose fault is it — she has her answer, and so does everyone she compares notes with. The gap doesn’t close. It goes deeper underground, and the next risk arrives even later. If the response is “thank you, let’s work out what we do about it”, and the follow-through matches the words, something different happens. The team now holds one piece of direct evidence about what honesty costs with this manager. Not a value on a slide. A tested behaviour.
That’s how the gap closes, because the team isn’t reading the org chart. They’re reading conduct, one situation at a time. A useful discipline in the meantime: ask how you’d get this person to move if you weren’t the boss. Strip out the positional power and what’s left — clarity about what you expect, reasons rather than instructions, doing exactly what you said you’d do — is what actually creates confidence.
What the green really meant
Three weeks later, in the version where the developer stayed silent, the deadline slips in front of the client, and the manager finally learns what the green reports were reporting. Not the state of the project. The state of the relationship. The authority worked perfectly the whole time; everything asked for was delivered. But the one thing that would have saved the project was never going to be volunteered, and no instruction could have requested it, because the manager didn’t know it existed.
That’s what a confidence gap looks like. Nothing wrong on the surface, every box ticked, and a team quietly deciding, person by person, how much of the truth you can be relied on to hear. Authority can get you the behaviour. Trust makes the truth more likely. The green report was never lying, exactly. It just wasn’t about the project.