Leading People Who Are More Experienced Than You
How to lead a team that knows more than you do about the work, using Andy Grove's task-relevant maturity, Amy Edmondson's situational humility, and Chris Hadfield's advice to aim to be a zero.
Your first team meeting is in an hour. The person at the end of the table has done this job for eighteen years and has worked for four managers, none of whom lasted. You have a plan, a title, and a very clear sense that your best contribution this morning is not to say anything wrong.
What do experienced people actually need from you?
Not your expertise. They have their own. What they typically lack is someone to make decisions across the team, clear goals, protection from distractions, and access to the people who control resources.
Generic advice tells new managers to "earn respect" and "show confidence." Ask an assistant and you will get the same: be authentic, listen, build trust. It is accurate and offers nothing to do in the first meeting.
The documented approaches are more specific about what to do with your lack of expertise, how to treat theirs, and what to do on day one.
Where does your value come from?
Andy Grove's High Output Management (1983) describes a manager's power as coming from two sources: position power, which comes from the role, and knowledge power, which comes from expertise. A manager's output, in his famous framing, is the output of the team. He also introduced task-relevant maturity: how experienced a person is at a given task. For highly mature people, he argues, the manager's job shifts toward setting objectives and checking results, and away from directing how the work is done.
Applied: Identify where you have value that does not depend on matching their expertise. It might be cross-team decisions, resources, priorities, or clarity about what success looks like. Then agree on objectives and the check, and leave the method to them.
"I have been put in charge of a team whose members have more experience than I do in [domain]. List the parts of a manager's job that do not depend on matching their expertise, such as setting objectives, removing obstacles, and coordinating with other teams. Then help me write a short statement of what I will own and what I will leave to their judgment."
Why it works: naming what you own makes it easier to hold that ground and to stop competing on what you lack.
How do you make it safe for them to correct you?
Edmondson's The Fearless Organization (2019) lists three leader tasks: set the stage, invite participation, and respond productively. Within inviting participation she includes situational humility, which means acknowledging what you do not know in the situation, and proactive inquiry, which means asking real questions rather than waiting for people to volunteer.
Applied: In the first meeting, say what you know and what you do not, and ask the team where you are most likely to go wrong. When someone corrects you, thank them and say what changes as a result. The correction rate in your first month tells you how safe they think it is.
"I am leading my first meeting with a team that is more experienced than I am. Draft a short opening that is honest about what I know and do not know, three questions asking where they see risks or blind spots in my plan, and a sentence of thanks I can use when someone corrects me. Keep it plain and not self-deprecating."
Why it works: asking for correction in advance makes it normal, so the first real one does not have to be brave.
What should you do on day one?
Chris Hadfield's An Astronaut's Guide to Life on Earth (2013) describes a principle from his career: when you join a new team, aim to be a zero. A minus hurts the team by creating problems, and a plus one tries to impress. A zero is someone whose presence does not cause harm and who listens and helps. He later commanded the International Space Station on Expedition 35.
His advice is aimed at newcomers rather than managers, so adapt it. You are accountable in ways a newcomer is not. The discipline that applies is listening before acting, learning how the team works, and not changing things to show that you have arrived.
Applied: For the first few weeks, ask more than you announce. Learn what is working, what annoys them, and what they would keep. Make small, visible improvements that help them before you propose anything large.
"Help me plan my first thirty days leading a more experienced team. Include the questions I should ask each person, what I should observe before changing anything, two small improvements I could make that help the team rather than showing off, and the point at which I should start proposing larger changes."
Why it works: a listening period with a planned end avoids both overreaching and drifting.
Which idea do you reach for?
| Approach | From | When it fits | Watch out for |
|---|---|---|---|
| Match oversight to maturity | Andy Grove, High Output Management | The team knows the work better than you do | Using "leave it to the experts" to avoid accountability for results |
| Situational humility | Amy Edmondson, The Fearless Organization | People hold back corrections or concerns | Humility that sounds like uncertainty about your role |
| Aim to be a zero | Chris Hadfield, An Astronaut's Guide to Life on Earth | You are new and about to make changes | Staying a zero too long once you are expected to lead |
What won't these ideas do?
They will not make a hostile person cooperative or fix a role that was set up badly. If you were put in charge without the authority to decide anything, no framework supplies it. And they will not tell you whether you are the right person for the job. They help you do the job well while you find out.
Andy Grove is in the Operator & Systems category, Amy Edmondson in People & Culture, and Chris Hadfield in Explorer & Adventurer. For the originals, read High Output Management, The Fearless Organization, and An Astronaut's Guide to Life on Earth. For a structured plan for a new role, First 90 Days Plan is a $99 tool built for it.
All the copy-paste prompts from this guide, and the rest of the Situations series, live at /prompts too, free to copy without reading the guide first.
Frequently asked questions
Do I need to be the expert to lead experts?
Grove's High Output Management separates knowledge power, which comes from expertise, from position power, which comes from the role. A manager with less task knowledge can still add value by setting clear objectives, removing obstacles, and making decisions across the team. Pretending to expertise you lack is the quickest way to lose the people who have it. The practical test is whether you can explain your decisions in terms of the team's goals, rather than in terms of what you personally know about the work.
What does Hadfield mean by aiming to be a zero?
In An Astronaut's Guide to Life on Earth, Chris Hadfield describes arriving on a new team aiming to be a zero: someone who causes no problems and takes up no extra attention, rather than trying to be a plus one. It is advice for newcomers. A leader has more responsibility, but the discipline of listening first applies. Treat the aim as listening first, and keep it for the first weeks rather than as a permanent stance, because a team still needs direction.
How should I handle being challenged by a more experienced person?
Treat it as information first. Edmondson's work on psychological safety suggests responding to challenge with appreciation and curiosity, since the way you respond decides whether challenge continues. You can still decide differently after hearing it. Distinguish disagreement about how from disagreement about what you are accountable for. Say what you heard, what you will take on board, and where you still disagree, so the challenge feels heard even when the decision stands.
What if someone resents reporting to me?
Raise it privately and directly, without accusation, and ask what would make the working relationship easier. Grove's focus on the one-on-one as a place to learn what a person needs applies here. Some resentment fades when people see you are competent at the parts of the job that are yours. Choose a calm moment, say what you have noticed, and ask what would help, listening more than you explain yourself.
How do I decide when I have to override their judgment?
When the decision belongs to you and the team's interests demand it, make it, explain your reasoning, and acknowledge the cost. Task-relevant maturity suggests leaving the method to experts and keeping responsibility for the outcome. Overriding on how they do it is different from overriding on what the team commits to. Explain the decision and the reason, thank them for their view, and ask for their help making it work in practice.
Can AI help me prepare for these conversations?
It can help you draft questions, plan a first meeting, and rehearse responses to pushback. It cannot tell you how a particular person is feeling or what history sits behind their reaction. Use it to prepare, then learn the rest by listening to the people in front of you. Bring it your real situation and have it play the skeptical expert, so you hear the hardest objection before you meet it live.
Written by Gareth Hoyle. Last updated 8 October 2026. Part of the authority.md guides library.
More guides.
Apologizing to a Customer When You Got It Wrong
How to write an apology a customer believes, using the Trust Triangle from Frances Frei and Anne Morriss, the Trust Equation from Maister, Green and Galford, and Robert Cialdini's commitment principle used ethically.
Asking for a Raise Without Turning It Into a Standoff
How to run a pay conversation as a problem you and your manager solve together, using three documented negotiation approaches from Fisher and Ury, Chris Voss, and Deepak Malhotra.
Running a Post-Mortem Without Blame That Still Changes Something
How to run a review after a failure that finds real causes without scapegoating anyone or letting accountability disappear, using Amy Edmondson, W. Edwards Deming, and Gene Kranz.