Leading a large team when you're the new one

On my first week leading a rooms operation, I stood in a back office and looked at a schedule with dozens of names on it, most of whom knew the building far better than I did. Some had worked that property longer than I had worked in hospitality. And I was the one now responsible for the standard they held every day. If you have ever walked into that, you know the specific feeling: not fear exactly, but the very loud awareness that you have authority you have not yet earned.

Here is what I have learned across teams of sixty, seventy, ninety and up. The gap between the authority you are given on day one and the authority you actually earn is the whole early job. You close it slowly, in public, with your hands. Nothing about it is a speech.

Why your instinct on day one is probably wrong

The instinct, when you feel that gap, is to close it fast by asserting yourself. Make a change so people see you are in charge. Announce a new direction. Correct something visibly. It feels like leadership. It is almost always a mistake.

The team does not need proof that you have the title. They can see the title. What they are quietly asking is different: Are you fair? Are you reliable? Do you actually understand this work, or are you going to make our jobs harder to make yourself look decisive? Every early action you take is read as an answer to those questions, whether you meant it that way or not.

Read down the right column and the early job comes into focus: answer the question they are really asking, not the one you assume they are.

The team does not need proof that you have the title. They need proof that you are worth following.

So the first move is not a move. It is to slow down and learn how the work really flows before you touch it. Where do arrivals bottleneck. Who is the person everyone quietly goes to when something breaks. Which parts of the written process does the team actually follow, and which have they wisely worked around because reality is messier than the binder. You cannot lead a system you do not understand, and on a large team the real system is never the one on paper.

How do you lead people who have been here longer than you?

This is the question people are most afraid to ask out loud. You are twenty-something, or new to the property, and there is a front desk veteran who has seen five managers come and go. The fear is that they will not respect you. The reframe that changed everything for me: their experience is not a threat to my authority. It is the single best resource I have.

So I use it, openly. I ask them how things work. I ask what the last few managers got wrong. I credit them in front of others when their knowledge saves us. A veteran who feels seen and enlisted becomes your strongest ally, because they carry informal authority you cannot assign, and when they nod along with a decision, the room relaxes. A veteran who feels threatened or ignored becomes a quiet, powerful undertow. You choose which one you get, largely by how you treat their experience in the first month.

None of this means pretending you have no role. You still make the calls. But there is a difference between deciding with someone's input and deciding over their head, and on a large team that difference is felt by everyone, not just the person in the conversation.

I will say the harder thing too. Occasionally a veteran will test you, not out of malice but because they have watched managers come and go and want to know if you are worth investing in. The test usually looks like a small challenge in front of others, a "we don't really do it that way here." The wrong response is to win the moment by pulling rank. The right one is to stay steady, take the point seriously if it has merit, and hold the line calmly if it does not. You are not trying to defeat the person. You are showing the whole floor that you can be disagreed with and stay fair. Passing that test quietly does more for your standing than any amount of early authority.

What earning trust actually looks like

People want a formula for trust, and the honest version is unglamorous. It is dozens of small, visible, repeated actions that all say the same thing: you can count on me. A few that have mattered most for me:

• Do the unglamorous task yourself. Jump on the phones during a rush. Take the difficult guest so an agent gets a break. Nothing buys credibility like a manager who does not consider any part of the work beneath them.
• Keep your small promises. If you said you would fix the broken printer or follow up on someone's schedule request, do it, and do it when you said. Reliability on tiny things is how people predict you on big ones.
• Be consistent with everyone. The standard cannot bend for the person you like. The moment the team sees a favorite, you have lost the fairness they were testing for.
• Say what you don't know. "I don't know that yet, I am still learning how you all run this. Walk me through it." Admitting the gap honestly costs you nothing and buys you a great deal.

This is the same trust-building work I would tell anyone learning to earn trust fast with a new team, only the numbers make it louder. On a team of ninety, you cannot have a deep one-on-one with everyone in week one. So your consistency has to be legible from across the floor. People who have never spoken to you are still forming a read of you, from how you handle the agent in front of them.

Change slowly, with two exceptions

The general rule is to hold most changes until you understand why the current way exists. Almost every "inefficient" process I wanted to fix on day three turned out to have a reason I could not see yet. Chesterton's fence is real, and on a busy operation the fences were usually built after somebody got hurt or a guest got burned.

There are two exceptions where you move immediately. Anything unsafe, and anything unfair. If a practice puts a person or a guest at risk, you fix it now and explain later. If something is treating part of the team unjustly, waiting to be polite about it just tells everyone you tolerate the injustice. Outside those two, patience is the more powerful choice. You will get your window to reshape things, and it will be far wider once the team believes you understand what you are changing.

When you do make your first real change, make it one they can feel the benefit of, not just one that makes your reports cleaner. Fix the thing they complain about at the end of every shift. Smooth the bottleneck that makes their nights harder. An early win that lightens the team's load buys you an enormous amount of goodwill, because it answers the question they have been asking about whether you are here to help them or to be seen. Save the changes that mostly serve you for later, once you have banked the trust to spend on them.

How do you learn a team of ninety in the first month?

You cannot do it from the office. The only way I know is to be on the floor, in the flow of the work, at different hours and on different shifts. The overnight team runs a completely different operation than the morning rush, and the person who only ever visits at 10 a.m. never really understands their building. I make a point of working alongside the sections I understand least, not to supervise but to see. What breaks at 3 a.m. Who covers for whom without being asked. Where the written process and the real one quietly diverge.

I also learn names faster than feels natural, and I learn them attached to something specific. Not just a name on a schedule but the agent who is unshakeable with an angry guest, the one who trains the new hires better than any manual, the one going through something hard at home this month. On a large team, being known as a person by the manager is rare enough that it lands. It tells someone they are not a line on a labor report. That single act of being seen does more to bind a large team to a new leader than most of what we are taught to do.

A first-month plan you can actually hold to

People want the abstract advice made concrete, so here is roughly how I sequence the first month on a large team. It is not rigid, but the order matters, because each phase earns the right to the next.

1. Week one, learn the mapWork different shifts, including the overnight. Write down where arrivals bottleneck, who everyone quietly goes to when something breaks, and which written steps the team has wisely worked around. Change nothing that is not unsafe or unfair.
2. Week two, learn the peopleAttach every name to something specific: the agent who is unshakeable with an angry guest, the one who trains new hires better than the manual, the one carrying something heavy at home. Ask the veterans how the last managers got it wrong.
3. Week three, bank reliabilityKeep the small promises visibly. Fix the broken printer you said you would. Take the phones during a rush. Do the unglamorous task in front of people, because on a team this size your consistency has to be legible from across the floor.
4. Week four, make one change they can feelFix the thing they complain about at the end of every shift, not the thing that makes your reports cleaner. An early win that lightens their load answers the question they have been asking about whose side you are on.

A worked example of the veteran test, because it almost always comes early. In my first weeks a long-tenured agent said, in front of two others, "we don't really do it that way here," about a checkin sequence I had asked for. Pulling rank would have won the sentence and lost the floor. Instead I said, "Tell me how you all do it and why," and listened. Half their version was better than mine, built from a guest problem I had not seen yet, so I adopted it and credited them for it. The other half was a shortcut worth closing, and I held that line calmly with the reason attached. The whole desk watched me get disagreed with and stay fair. That did more for my standing than any authority I could have asserted.

Leading at scale means leading through people

The last shift in thinking is the biggest. On a small team you can touch every guest interaction yourself. On a team of ninety you cannot, and the sooner you accept that, the better you lead. Your job stops being to do the work and becomes to build the people and the standards that do the work when you are not in the room.

That means finding the informal leaders and investing in them. It means being clear enough about the standard that it holds on a shift you are not working. It means the calm you bring, especially in the first hour of a shift, gets multiplied through supervisors who borrow it and pass it down. You are no longer leading ninety people directly. You are leading a handful of people well, and trusting the standard to carry the rest.

This is the shift that trips up strong individual performers the most. The very habit that got you here, doing the work brilliantly yourself, becomes the thing that caps you. If you are the best agent on the floor and you keep proving it, you have only ever solved one desk at a time. The leader's version of excellence is different and quieter. It is watching someone you developed handle a hard arrival exactly the way you would have, on a shift you are not even working, and knowing your fingerprints are on it without your hands being anywhere near. That is what leading at scale actually feels like when it is working, and it never stops feeling a little strange.

The first months are humbling, and they are supposed to be. You are being handed authority you have not earned and asked to earn it in public, on a team that has every reason to wait and see. But that gap closes. It closes on an ordinary Tuesday when a veteran you listened to backs your call without being asked, or when a new hire copies a standard they only ever saw you keep. That is the day you stop being the new one. Not because of anything you announced, but because of everything you did quietly while they watched.