How to earn a new team's trust fast

The first time I walked onto a floor as the new person in charge of people who had been there for years, I understood something in my body that no one had quite said to me out loud. They did not choose me. Someone above us decided I would lead, and now a room full of experienced agents was watching to find out what kind of manager had just landed on them. There was no hostility in it. There was something more honest than hostility: a wait-and-see patience, a reserved courtesy, a quiet collective decision to withhold real trust until I gave them a reason to extend it. That patience is the correct response, and learning to respect it changed how I show up in my first weeks anywhere.

I have started with new teams more than once, from a busy front desk in Waikiki to rooms operations in San Francisco leading groups of sixty to ninety and up, and the lesson has held every time. You do not talk your way into a team's trust. You behave your way in, in small, visible, repeated ways, over the ordinary days when nothing dramatic is happening. This piece is what I would tell anyone stepping into a team that did not pick them.

Why can't you just earn trust with a good first speech?

New managers love the opening speech. I understand the pull. You are nervous, you want to signal your values, you want them to know you are competent and warm and here to help. So you gather the team and you tell them your philosophy. And they listen politely, and almost nothing you say lands, because a seasoned team has heard opening speeches before. They have watched managers promise an open door and then vanish into the office. They have heard about respect from people who did not show any. Words are the currency they have learned to discount.

What they have not learned to discount is behavior, because behavior is expensive and hard to fake over time. So the speech that actually matters is not the one you give on day one. It is the hundred small things you do in the weeks after, each of which quietly answers the only question they are really asking: can I count on this person? Every promise you keep is a sentence in that speech. Every promise you drop is a sentence too, in the other direction.

This is the ground floor of frontline hospitality leadership. Before you can hold a standard or develop a person or have a hard conversation, the team has to believe you are reliable and fair. Trust is the substrate everything else grows in, and you cannot shortcut your way to it.

Small, visible reliability

If there is one phrase I would tattoo on a new manager, it is this one. Small, visible reliability.

Break it into its three words and each one carries part of the load.

Small, because trust is not built by grand gestures. It is built by the tiny things you follow through on. You said you would check on the broken keycard encoder before you left, and you did. You told an agent you would find out about their schedule request, and you came back with an answer even though the answer was no. These are almost invisible individually. Together they are everything, because they teach the team that your word and your action are the same thing.

Visible, because reliability that no one sees does not build trust, it just builds your own quiet virtue. In the early weeks I make sure I am on the floor, not in the back office, so the team can actually watch me work. When it gets busy, I get on a terminal and take guests. When there is a task nobody wants, the late arrival cleanup, the difficult phone call, the guest nobody else can calm, I take it myself, in view. Not to be a martyr, but because a team decides fast whether a manager is willing to do the work they ask others to do.

A team does not decide to trust you. They notice, slowly, that they already do.

Reliability, because the through line of all of it is predictability. People trust what they can predict. When my mood, my standards, and my word stay steady from Monday to Friday and from a slow Tuesday to a sold-out Saturday, the team can relax, because they know what they are getting. The most corrosive thing a new manager can be is inconsistent, warm one day and sharp the next, generous with one agent and cold with another. Inconsistency reads as instability, and no one extends trust to instability.

Watch before you change

The instinct of a new manager, especially an ambitious one, is to arrive and improve things. You want to show your value, so you start changing processes in the first week. This is the single fastest way to lose a seasoned team, because when you change a thing you do not yet understand, you announce that you were not curious enough to learn why it was that way in the first place.

Almost every process that looks inefficient to a newcomer exists for a reason that is invisible from the outside. The weird workaround at checkin solves a problem with the arrivals report. The odd way they stage keys prevents a mixup that once burned them badly. When I arrive, I spend my early weeks mostly watching and asking, not because I have no ideas, but because my ideas are worth more once they are informed. I ask the veteran agents to teach me their floor. I ask why things are done the way they are, and I listen for the history in the answer.

Then, when I do change something, I change one thing, and I make it something the team already feels the pain of. Fixing a problem they have been complaining about for a year buys more trust than ten improvements they never asked for. It tells them I was listening, and that my authority is pointed at their problems and not just my resume. This restraint is a big part of leading a large team you did not build, where the sheer weight of accumulated experience in the room demands that you earn the right to redesign anything.

The moves that build trust fastest

• Keep tiny promises. Track the small things you commit to and close every one, even when the answer is no. Reliability on the trivial is what earns you belief on the important.
• Take the worst task in view. When something hard or unpleasant comes up in the early weeks, do it yourself where they can see. It resets what they expect from a manager.
• Back your people in public. When a guest is wrong and your agent is right, defend the agent in the moment. A team learns whether courage is safe here from whether you protect them.
• Admit what you do not know. Competence plus humility beats confidence alone. Asking a veteran to teach you does not shrink your authority. It grounds it.

What about the people who have been here longer than you?

This is the hardest and most delicate part. On most new teams there is at least one person, often several, who has forgotten more about that specific property than I currently know, and who may quietly wonder why they are not the one leading. If I handle those people badly, they can make my life very hard, not through open rebellion but through the slow, deniable friction of a team that has decided not to help me. If I handle them well, they become my greatest allies, because the team already trusts them, and their trust in me transfers.

The move is not to compete with their experience. It is to honor it, out loud and sincerely, and to lean on it. I go to the most respected veteran early and I say some version of the truth: you know this floor better than I do, and I need you to teach me. That sentence costs me nothing and it disarms almost everyone, because it replaces the story they feared, that I would arrive and act like I knew better, with a story they can respect, that I arrived ready to learn. It also happens to be true, which is why it works. You cannot fake this. A seasoned person smells performed humility instantly. Real humility, the kind that actually defers to their knowledge and changes your plans based on what they tell you, is rare enough that it builds trust quickly.

None of this means abdicating. I am still the one who decides, still the one accountable, still the one who holds the standard. Deferring on knowledge is not the same as deferring on authority. But there is no contradiction between being in charge and being the student of the people you lead, and the managers who understand that difference age into the ones teams follow willingly. Part of setting that tone is what you do in the very first sixty minutes of a shift, which is its own discipline I have written about in the manager on duty checklist for the opening hour.

A worked example: your first two weeks

If it helps to have a concrete shape rather than a principle, here is roughly how I spend the first two weeks with a team that did not choose me. The order matters as much as the actions.

1. Days one to three: be seen doing the work. I stay on the floor, not in the back office. When it gets busy I get on a terminal and take guests. The team's first read of me is visual, and I want it to be a manager who works, not one who watches.
2. Week one: ask the veterans to teach you. I go to the most respected long-tenured agent and say the plain truth: you know this floor better than I do, teach me. I ask why things are done the way they are and listen for the history in the answer.
3. Across both weeks: keep a promise list. Every small thing I commit to, I write down and close, even when the answer is no. Reliability on the trivial is what earns belief on the important.
4. End of week two: fix one real pain point. One change, and something they have been complaining about for a year, not an improvement they never asked for. It tells them my authority is pointed at their problems, not my resume.

Notice that changing processes does not appear until the very end, and even then it is one thing they already feel. The first two weeks are mostly watching, working, and keeping small promises. That looks like doing very little. It is actually the whole foundation going in.

Trust is spent as fast as it is earned

Here is the sobering half of the truth. Trust builds slowly, through all these small consistent acts, and it can be spent in a single moment. One promise you break and forget about. One time you throw an agent under the bus in front of a guest to save yourself. One flash of temper that tells the team your calm was conditional. Any of these can undo weeks of quiet goodwill, because trust is not a trophy you win and keep. It is a running balance, replenished by reliability and drained instantly by any evidence that you cannot be counted on.

The same handful of moments can move the balance either way, which is worth seeing plainly.

Every entry in the left column takes weeks to accumulate, and every entry in the right can spend it in a single shift.

That sounds fragile, and it is, but it is also freeing, because it means the method never changes. You do not graduate from earning trust. The same small, visible, reliable behavior that builds it in week one is what maintains it in year three. I have never reached a point with a team where I could coast on accumulated goodwill, and I have stopped wishing for one, because the requirement to keep showing up honestly is exactly what keeps me honest. The moment I feel I have earned enough trust to relax the standard I hold myself to is the moment the balance starts to drain.

So if you are stepping into a team that did not choose you, put down the speech. Nobody needs your philosophy yet. Keep your small promises, take the hard task where they can see it, ask the veterans to teach you, and change one thing that fixes a pain they already feel. Do that steadily for a few weeks, and you will notice something quiet happen: the reserved courtesy warms, the wait-and-see softens, and one day you realize the team is bringing you problems instead of hiding them. That is trust, and you did not talk your way into it. You behaved your way in, one ordinary reliable day at a time, which is the only way it has ever been done.