Book 1:1 Discovery Call

+973 3541 1661 · coachrulahusseini@gmail.com

How to Lead When You Are Not the Expert

To lead when you are not the expert, own the questions, priorities and decisions rather than the technical answers. Learn enough of the field to ask sharp questions and judge risk, let your specialists lead on content, and add value through direction, removing obstacles and connecting the team's work to what the organisation needs. Being honest about your gaps builds more respect than pretending to fill them.

By Rula Husseini, ICF PCC · Reviewed 3 November 2026

Manager with a lanyard leaning in to listen as an engineer explains work on his screen

More leaders face this than admit it. A finance leader takes on procurement and IT. A commercial manager is asked to run an engineering function. A new general manager inherits departments they have never worked in. The team often knows more about the work than the person leading it.

That is not a flaw in the arrangement. Organisations do it deliberately, because leading a function and being its best practitioner are different jobs.

Your job is the decision, not the technical answer

Specialists answer 'how'. Leaders answer 'what, why and in what order'. When you accept that split, the pressure to become an instant expert drops, and you can focus on the questions only you are positioned to answer: which problems matter most, what trade-offs the organisation will accept, and who needs to be involved.

You still need judgement about the content. The point is that your judgement comes from asking good questions and weighing the answers, not from knowing more than the people who do the work.

Learn the field fast enough to ask good questions

Set yourself a learning plan for the first six to eight weeks. The aim is not mastery. It is enough fluency to follow a technical discussion, notice when something sounds wrong and know who to ask.

  • Ask each specialist on your team to give you a 30-minute walkthrough of their work, as if to a capable outsider.
  • Build a glossary of the terms you hear and do not understand, and check it with someone you trust.
  • Read the last three post-project reviews or incident reports. Failures teach you where the real risks sit.
  • Sit in on the work itself: a site visit, a release, a client delivery, an audit.
  • Find one expert outside your team, perhaps in another department, who can give you an independent view.

Questions that let experts lead the content

Good questions give your specialists room to think while making sure the thinking is complete. Use them in reviews, decisions and one-to-ones.

  • 'What are the two or three options, and what would you recommend?'
  • 'What would have to be true for this to fail?'
  • 'What are we assuming that we have not checked?'
  • 'Who disagrees with this approach, and what is their best argument?'
  • 'How would you explain this decision to the executive committee in two sentences?'
  • 'What do you need from me to make this happen?'

Where a non-expert leader adds the most value

Teams of specialists often lack exactly what a non-specialist leader can offer. Recognising this makes your contribution concrete rather than apologetic.

What the team often needsHow you provide it
Clear priorities when everything seems urgentRank the work against organisational goals and say no to some of it
A voice with senior stakeholdersTranslate technical issues into business language and secure resources
Decisions when experts disagreeClarify the criteria, hear both sides fully, decide and explain why
Protection from distractionsAbsorb requests and politics so specialists can focus
Development beyond technical skillCoach people on communication, influence and leading others

Three traps for leaders outside their specialism

  • Faking expertise. Specialists spot it within minutes, and you lose the right to be trusted on the things you do know.
  • Deferring on everything. If you never challenge a technical recommendation, you are not leading, you are approving. Ask the questions, then decide.
  • Retreating to what you know. It is tempting to spend your time on the parts of the job that match your background. The rest of the function notices which parts of it you avoid.

Example: a commercial leader taking over an engineering function

Imagine a commercial director in a Gulf manufacturing company who is asked to lead the maintenance and engineering department as well. The engineers are polite but sceptical. In the first meeting, the director says plainly: 'You know this work far better than I do. I will learn enough to ask good questions, and my job is to make sure you have what you need and that the right things get priority.'

Over the next two months, the director spends a morning a week on site, reads the last year of shutdown reports, and asks engineers to present options rather than single answers. When two senior engineers disagree on a major repair approach, the director does not pick the more confident voice. They ask each to set out the risks and costs, involve the finance team, and make a decision with the reasons written down. The engineers start bringing problems earlier.

A made-up case, but a familiar one: the engineers' trust came from the quality of the director's questions and decisions, not from technical knowledge.

Coaching for leaders out of their comfort zone

Leading outside your expertise often stirs up a quiet doubt about whether you belong in the role. That doubt can push you toward either faking or over-deferring. The guide on how to overcome imposter syndrome at work explores where it comes from.

Confidence coaching for leaders helps you separate what you genuinely need to learn from what is simply discomfort, and build a way of leading that does not depend on being the expert. Early in the role, it also helps to be deliberate about building credibility in a new leadership role.

About the author

Rula Husseini is an Executive Leadership & Mindset Coach (ICF PCC) based in Manama, Bahrain, with 26+ years in leadership, HR and talent development and 4,500+ coaching hours. She coaches executives, emerging leaders and teams in Arabic and English, in person and online.

Credentials and training →

Frequently asked questions

How do I earn respect from a team of experts I cannot match technically?

Show respect for their expertise, ask questions that show you are thinking seriously, and deliver what they need from a leader: priorities, resources and protection from noise. Respect follows when they see you make their work easier and their results more visible.

Should I tell my team I am not an expert in their field?

Yes. They already know, and saying it openly removes the tension. Pair the admission with what you will bring and how you plan to learn, so it sounds like clarity rather than apology.

How much technical knowledge does a leader need?

Enough to understand the main risks, follow a technical conversation and judge whether a recommendation has been properly thought through. That level is usually reachable within a few months of deliberate learning. Beyond it, your time is better spent on leadership work.

What do I do when two experts on my team disagree?

Agree the decision criteria first, then ask each person to make their case against those criteria, including the risks of their own option. Involve a third view if needed. Make the call, explain the reasoning to both, and agree what you will watch to know if it was right.

Leading a team that knows more than you?

Book a free discovery call to talk through how you want to lead them.