How a young manager builds authority with a long-serving team

Age doesn’t tell you whether someone will be a good manager

The new manager is 29, and the operators on the shift have been doing the job for twenty years. On day one he hears: “Let’s see what you can teach us.” It is tempting to assume that an older workforce doesn’t want change. But that is a stereotype, not a diagnosis of the team. Ng and Feldman analysed 418 studies covering more than 208,000 people and found no support for most of the popular negative beliefs about older workers, including the general claim that they resist change. The practical conclusion is simple: don’t judge people through the lens of age. Find out what each person can do, what matters to them and what reservations they have about a specific idea. Otherwise you will create the very conflict you fear. In your first meetings, ask about the biggest risks in the process, not about who will “accept the new boss”. Then say which decisions you are responsible for. Respect for long service and clarity about your role can coexist.

Two false routes to respect: severity and endless consultation

Some young leaders tighten the screws: they shut down discussion, correct people in front of others and pull rank. Others are afraid to make any decision until they have everyone’s agreement. Both can undermine trust. In the first case people stop talking about risks; in the second they don’t know who is really responsible for the outcome. Edmondson’s research on psychological safety links the freedom to speak up with team learning, but it does not show that every decision should be made collectively. A sensible rule is: before changing a procedure, I listen to the people who know the process, then I make the decision and explain my reasoning. Employees can raise an objection without fear of being ridiculed. They don’t, however, get an automatic right of veto. What convinces people most is consistency: you settle similar cases by similar criteria, regardless of who is talking to you.

Draw on people’s experience, but don’t hand over your role

An experienced shift supervisor knows that a schedule that is faster on paper will cause downtime at changeover. Instead of replying, “The decision’s been made,” ask: “Show me where we lose time and what could go wrong.” This isn’t a test of your own knowledge; it’s a way of gathering the information you need to decide. Then separate three things: the facts about the process, the budget constraints and the criterion for choosing. You might say: “I’m taking the changeover risk into account. We’re setting a new sequence for the jobs, and after two shifts I’ll review the results with you.” The employee then sees that their knowledge shapes the plan, even though they aren’t running the whole plant. You don’t have to accept every opinion. But every significant point deserves fair consideration and a brief explanation of why it was used or rejected. Expert knowledge and the authority that comes with your role complement each other rather than compete.

What to say when someone publicly undermines you because of your age

At a briefing someone throws out: “When you’ve worked here as long as I have, you’ll understand.” You don’t need to respond with a lecture about respecting your superiors. It’s better to keep the conversation on the issue: “You may be seeing a risk I haven’t taken into account. Tell me specifically what it is. The responsibility for the decision stays with me.” That way you don’t get drawn into a contest over years of experience, but you don’t ignore potentially important information either. If someone repeatedly sabotages what has been agreed, talk to them about it in private: point to the situation, its effect on the work and how you expect objections to be raised. Distinguish an awkward joke from persistent humiliation or unequal treatment. Employment law protects against age discrimination, but not every comment automatically amounts to a breach. Establish the facts first and, if the behaviour is repeated, use your organisation’s procedures. What matters is that the rest of the team sees that debate about the work is allowed, but belittling people is not.

Your first decisions say more than an inaugural speech

A new boss can give a brilliant presentation and then hand the hardest shifts to whoever protests least. Predictability vanishes in an instant. Start with decisions everyone can see: how overtime is shared out, the order in which leave is granted, how you respond to breakdowns and the rules for reporting lateness. Set clear criteria before you decide who the arrangements apply to. Say what an exception looks like and who approves it. Rather than announcing that from now on things will be “fair”, show what that means in one specific case. A meta-analysis by Colquitt and colleagues links perceptions of organisational justice with important employee attitudes, but it does not offer a universal formula for every rota. The solution has to be adapted to the working conditions and to the rules that have been agreed. After a month, ask whether the system is actually working and let the team know about any change that’s needed. When you change the rules, explain what practice has shown. People don’t expect you to be infallible; they want to know what to expect.

Admitting a mistake doesn’t cost you the right to lead

Suppose that, despite warnings from the maintenance manager, you approved a deadline that can’t be met. The worst response is to look for someone on the team to blame. A better one: “I made a wrong assumption about the servicing time. I’m changing the schedule. Next time I’ll check that data before confirming a deadline.” This shows responsibility for the process, not public self-flagellation. It also helps to acknowledge the contribution of the person who warned you: “You were right to raise that – thank you.” There’s no need to add “for your age” or “the old school always knows best”. Come back to the issue the following week, because without a visible correction an apology remains just a statement. If your own boss demands an unrealistic deadline, set out the constraints and the options rather than pretending to the team that the problem doesn’t exist. A young leader’s authority doesn’t rest on always having the answer, but on being able to steer the team to a responsible decision.

Authority is not a reward for age, position or the longest service. It develops when a manager draws on the team’s knowledge, settles disputes by clear rules, takes responsibility for the result and doesn’t punish people for raising reasoned objections. A first difficult conversation handled well can matter more than an entire welcome speech.

How Empatyzer helps a young leader prepare for a difficult conversation

Imagine that tomorrow you are running a briefing with people who know the process better than you do. In a conversation with Em you can describe the task, previous tensions and three reactions you expect: a joke about your age, an accusation that you lack experience and a reasoned warning. Em will help you recognise which reactions call for an explanation and which call for a boundary, and prepare a short opening and responses without a defensive tone. If profiles are available in your organisation, you can take into account differences in how people make decisions and how much autonomy they need, instead of explaining everything by generation. Then you can rehearse a one-to-one conversation with the expert: how to ask for their knowledge while making it clear who decides. After the briefing, it’s worth going back to Em with what worked and what met with resistance. A short micro-lesson will help you consolidate the skill of setting boundaries without a show of power. That way you are working not on your image as the “young boss”, but on the everyday behaviour by which the team forms its view of you.