Building trust as a new manager

Your first week as a manager, someone on your team will show you something — a process, a system, a way of working — and you will think: this is obviously broken. I can fix this.

You might even be right.

Fix it anyway and you will have made your first management mistake. Not because the fix is wrong, but because you have just told your team something they will not forget: this person arrived with their conclusions already formed. They are not here to learn. They are here to install their version of things.

Trust in a new manager is not built on being smart. It is built on being reliable. Those are different things, and most first-time managers confuse them.

The mistake everyone makes

The pressure on a new manager is real. You were promoted — or hired — because someone believed you could run this. You feel the weight of that. And the fastest way to demonstrate that the belief was justified, the way that feels most obvious, is to demonstrate your judgment. Change something. Improve something. Show results.

This instinct is understandable and almost universally counterproductive.

When you change things fast, you are not demonstrating competence. You are demonstrating that you do not understand what you do not know yet. Every team has institutional knowledge that is invisible from the outside: why that process exists, what it replaced, what broke when they tried something else. When you override that knowledge in week two, you signal that you think the map you arrived with is more accurate than the territory they have been living in.

The people on your team notice this. They do not always say it out loud. They adjust. They start managing what they tell you. They route around you. And six months later you are confused about why your team feels distant, why information arrives late, why you seem to be hearing about problems after they have already escalated.

The answer is your first two weeks.

The credibility-trust formula

Here is the distinction worth writing on a card and keeping somewhere visible.

Credibility is your demonstrated capability. Trust is the belief that you will use your capability in service of the team — not yourself, not your career, not your need to be seen as effective.

New managers usually have some credibility before they walk in the door. They were good at something, which is why they were promoted. But trust starts at zero. You cannot transfer it from your previous role. You cannot borrow it from your manager’s endorsement. You have to build it, action by action, in this job, with these people.

The good news is that trust is built faster than most people think — but only with the right inputs. The wrong inputs (fast visible changes, opinionated decisions made before you understand the situation, arriving with your conclusions) build the opposite of trust. They build wariness.

The right inputs are: listening, keeping small promises, and protecting your team from above. In that order.

The trust-building timeline

Phase one: listen before you change anything

The first thirty days have one job: understand what you walked into.

That means running a one-on-one with every person on your team within the first two weeks. Not a performance conversation. Not a goal-setting session. A listening session. The questions that matter are: What is going well that you want to make sure I do not accidentally break? What is one thing that is getting in your way that no one has fixed? What do you wish the last manager had understood?

These questions do three things. They surface information you cannot get from the org chart or the handover document. They signal to each person that you see them as a source of knowledge, not just a unit of output. And they start building individual relationships before you have made any decisions that affect those relationships.

You will hear things that are contradictory. One person’s broken process is another person’s workaround that prevents a bigger problem. That is fine. Your job in phase one is not to resolve the contradictions. It is to understand them.

Take notes. Refer back to them in future conversations. Few things build trust faster than a manager who remembers what someone said six weeks ago.

Phase two: small commitments, kept exactly

By week three or four, you will have heard things that you can actually fix. Not the big structural things — not yet — but the small friction points. The one-off that blocks the team twice a week. The approval that bounces between two people and takes four days. The meeting that everyone knows is useless.

Pick one. Fix it. And before you fix it, say out loud to the person who raised it: “I am going to deal with this by end of week.” Then deal with it by end of week.

This is the mechanical engine of trust-building: make a small commitment, keep it, do this repeatedly. It sounds too simple to be the actual answer. It is the actual answer.

What you are doing is building a track record. Your team has no data on you yet. They do not know if you follow through. They do not know if you say things because you mean them or because you want the conversation to end. Every kept commitment is a data point. Every failed one is a data point in the other direction. The ratio matters. In the first ninety days, the ratio is everything.

Keep your commitments small enough that you can keep them. Do not over-promise in week one to look energetic. You will not be able to deliver, and the one broken commitment in a thin dataset lands harder than you think.

Phase three: give your team air cover

This one is less talked about, and it might be the most important.

Your team is producing work. That work is being evaluated, questioned, redirected, and sometimes criticised by people above you in the org. Your job is to be the buffer.

Air cover — a military term for fighter aircraft protecting ground troops from enemy fire — means absorbing the pressure that comes from above before it reaches your team. When your skip-level is unhappy with a timeline, your team hears that through you, calmly, with context and a plan. They do not hear it as panicked urgency in a Slack message at 9 pm. When a stakeholder wants to change scope mid-sprint, you have that conversation. Your engineers are not in that room.

What you are doing is buying your team the cognitive space to work. Constant top-down pressure fragments attention and degrades output. Shielding your team from it is not protecting them from reality — it is your actual job. Reality-processing is what they pay you for.

The trust signal here is subtle but powerful. When your team realises you absorb pressure rather than transmit it, they start working with more confidence. They know that a bad day in the org does not immediately become a bad day at their desk. That confidence is not complacency. It is the condition under which good work happens.

You will sometimes need to transmit reality — there are moments when your team needs to understand the urgency. But that is a deliberate choice, not a default. Default to absorption.

Phase four: earn the right to change the bigger things

Somewhere around day sixty, if you have listened well, kept your small commitments, and absorbed the pressure from above, something shifts. People start sending you the real problems. They come to you with the idea before it is polished, the concern before it is a complaint. The conversations get longer and more honest.

That is when you have earned the right to change the bigger things.

Not because you now know more about the domain — you probably knew most of what you know now before you walked in. But because your team trusts that when you change something, you are changing it for them, not at them. That distinction is everything. The same change, made at day ten versus day seventy, lands completely differently because the context around it is different.

When you do propose a bigger change, frame it honestly: “I have been here two months, I have seen this thing repeatedly, and I think there is a better way. Here is what I am thinking — tell me what I am missing.” That posture — confident but curious — is only available to you if you have spent sixty days demonstrating that you actually update when you hear what you are missing.

What failure looks like six months in

By month six, the manager who changed everything in week one is usually dealing with a version of the same problem: they have a capable team that is slightly less engaged than when they arrived. Not dramatically less — just slightly. The one-on-ones are a little shorter. The feedback is a little more guarded. The team executes, but they do not volunteer.

This is not a crisis. It does not show up in any metric. But it is the slow leak that limits what the team can actually become. And tracing it back to its origin is almost always uncomfortable, because the origin is usually an early decision that felt like competence.

The manager who spent the first sixty days listening is, by month six, dealing with a different problem: they have more information than they can act on, and they have to make choices about what to prioritise. That is the correct problem for a manager to have.

One thing to carry into your first week

If you take nothing else from this: your first week is not the time to show what you know. It is the time to show how you listen.

Walk into every conversation with a notebook and a question, not a position. “Tell me how this works from your perspective” is a more powerful opener than anything you could say about your vision or your experience or your ideas for the team.

The vision and the ideas will matter. They will matter enormously — eventually. But first they need to be grounded in this team, in this context, in what these specific people know that you do not.

Trust is the permission structure for everything else you will want to do. Build it slowly. Keep your promises small and exact. Protect your team from above. And change the bigger things only after you have demonstrated, repeatedly, that you are worth following.

That is the job. The rest is tactics.