Leading Experts with Humility: Strategies for Directors to Build Trust, Listen, and Learn
- Aug 6
- 10 min read
Starting a senior leadership role can feel strange when the people around the table know more than you do about the program, the country context, the technical field, or the history behind key decisions.
For a country director, executive director, or chief of party, that situation is not a weakness. It is the job. Senior leaders rarely lead because they are the top expert in every discipline. They lead because they help capable people do their best work together, make sound decisions, and stay focused on the mission.
The challenge is real, though. A leader who tries to prove expertise too quickly can lose trust. A leader who stays too passive can create confusion. The better path is steady, humble, and intentional: listen deeply, learn fast, respect what the team already knows, and create the conditions for shared leadership.

Accept that credibility comes from trust, not instant expertise
Many directors feel pressure to “earn the room” right away. That pressure can lead to over-talking, premature decisions, or a habit of giving an answer before asking enough questions.
Experienced staff usually do not expect a new leader to know everything. They do expect the leader to be honest, consistent, prepared, and respectful. Credibility grows when people see that you make decisions carefully and give credit where it belongs.
A useful early mindset is simple:
Your role is not to be the smartest person in the system. Your role is to help the system become smarter together.
That shift matters. It turns leadership from performance into service. It also helps a director avoid two common mistakes.
The first mistake is pretending. This sounds like using confident language to cover a knowledge gap, accepting praise for work you did not shape, or making technical claims without checking them. Experienced team members notice.
The second mistake is disappearing. A leader who says, “You all know more than I do, so just handle it,” may seem humble, but it can feel like abdication. Teams still need direction, protection, decisions, and clear priorities.
The middle ground is stronger. Say what you know. Name what you are still learning. Ask precise questions. Then make decisions in a way that reflects the team’s evidence and judgment.
For example, a chief of party new to a health systems program might say:
“I understand the donor requirements and the management risks. I am still learning the district-level referral patterns. Before we decide, I would like to hear from the clinical team and field coordinators about what they are seeing.”
That one sentence signals respect, responsibility, and clarity.
Practice active listening as a leadership discipline
Humility is not just a personality trait. In leadership, humility is a set of behaviors people can observe. Active listening is one of the most visible.
Active listening means more than staying quiet while others speak. It means listening with the intent to understand the meaning, context, and stakes behind what someone says. It also means showing that their input affected your thinking, even when you do not follow every recommendation.
Ask better questions
Broad questions often produce safe answers. Specific questions invite useful insight.
Instead of asking:
“Is everything going well?”
“Any concerns?”
“What do you think?”
Try asking:
“What is one risk you think leadership is underestimating?”
“Which decision from the last quarter helped the work, and which one slowed it down?”
“What would you do first if you were in my role for a month?”
“Where are we relying too much on one person’s knowledge?”
“What do communities, partners, or field staff understand that senior leadership may be missing?”
These questions do two things. They make space for expertise, and they show that candor is welcome.
Listen for patterns, not only volume
The loudest voice is not always the best signal. Senior leaders need to listen across roles, locations, languages, and levels of comfort with authority.
A country director may hear one story from senior technical leads and another from drivers, finance officers, community mobilizers, or regional coordinators. Both matter. The people closest to logistics, field relationships, and implementation details often see risks early.
Create several listening channels:
One-on-one conversations
Small group discussions
Anonymous feedback tools when needed
Field visits with open conversation
After-action reviews following major activities
Regular check-ins with operations and support teams, not only technical leads
Then look for repeated themes. If the same concern appears in different places, treat it as data.
Show what you heard
Listening loses power when it vanishes into silence. Close the loop.
You can say:
“Several people raised concerns about the reporting timeline. We cannot change the donor deadline, but we can adjust internal review steps. Here is what will change this month.”
Or:
“I heard the recommendation to delay the launch. After reviewing the risks, we will move forward, but with two added safeguards. I want to explain why.”
People do not need every decision to go their way. They need to know their input mattered.

Use team expertise without surrendering accountability
Experienced teams bring deep knowledge, but directors still carry formal responsibility. The goal is to use the team’s expertise while keeping decision-making clear.
That balance is especially important for executive directors and chiefs of party, who often sit between staff, boards, donors, government partners, and communities. They need to honor technical judgment while also handling trade-offs.
A useful practice is to separate input, recommendation, decision, and ownership.
Decision stage | What the leader does | What the team contributes |
Input | Names the question and invites the right voices | Shares evidence, context, risks, and lived experience |
Recommendation | Asks for options and trade-offs | Advises what should happen and why |
Decision | Makes or confirms the decision | Understands the rationale and implications |
Ownership | Assigns responsibility and removes barriers | Carries out the work and reports what changes |
This structure prevents confusion. It also avoids the false choice between top-down control and endless consensus.
Make expertise visible
Some organizations have hidden experts. The person with the most useful knowledge may not have the highest title. A long-serving finance manager may understand donor risk better than anyone. A field officer may understand community trust better than a national-level adviser. A local operations lead may know which plans are realistic during rainy season, election periods, or harvest time.
Map expertise early. Ask questions like:
“Who do people go to when they need historical context?”
“Who understands the informal process behind this formal process?”
“Who catches mistakes before they become expensive?”
“Who has strong relationships outside the organization?”
“Whose knowledge is at risk if they leave?”
Then create ways for that expertise to shape decisions. Invite those people into planning early, not just when a plan needs fixing.
Give credit in public and ask for challenge in private and public
Credit builds trust. Directors sometimes receive praise for results that came from years of work by technical teams, local staff, and partners. Redirect that praise clearly.
Say, “The education team designed that approach before I arrived, and the field staff adapted it with schools. My role was to help remove a few barriers.”
This does not reduce your authority. It increases it.
At the same time, invite challenge. Experienced staff may hold back if they think disagreement will be punished. Make respectful dissent normal.
Try saying:
“I am leaning toward option two. Before we decide, I want to hear the strongest case against it.”
Or:
“If this fails, what will we wish we had asked today?”
These prompts make it safer to name risk before it becomes damage.
Build collaboration through clear roles and shared purpose
Collaboration does not mean everyone joins every conversation. That quickly becomes exhausting. Good collaboration means the right people work together at the right time with enough clarity to act.
Start with purpose. Teams with deep expertise can still drift when they lack a shared frame. A director should keep returning to the central questions:
What are we here to accomplish?
Who are we accountable to?
What must improve because of our work?
Which values will guide hard choices?
What do we need to stop doing so we can focus?
These questions are not abstract. They help teams choose between competing priorities.
For example, if a program has limited staff time, the team may need to choose between producing a polished report, responding to a partner request, or supporting a field activity. Shared purpose helps the group decide without turning every choice into a personal preference contest.
Create working norms before conflict escalates
Experienced teams often have strong opinions. That is a strength when handled well. It becomes a problem when people debate without rules.
Set simple working norms:
Disagree with ideas without attacking people.
Share relevant information early.
Name risks before deadlines are fixed.
Do not reopen decisions unless new information changes the picture.
Bring the people affected by a decision into the conversation before the decision is final.
Respect language differences and avoid using acronyms as a gatekeeping tool.
These norms sound basic, but they reduce friction. They also give the director something neutral to point to when behavior slips.
Use facilitation, not domination
A leader does not need to dominate the room to guide it. In fact, when leading experts, facilitation is often more useful than persuasion.
Good facilitation includes:
Framing the decision clearly
Naming what is known and unknown
Drawing out quieter voices
Pausing when the group rushes too quickly
Summarizing areas of agreement
Identifying the real trade-off
Confirming next steps, owners, and timelines
This keeps the group productive without wasting the knowledge in the room.

Create an inclusive environment where expertise can surface
Inclusion is not only about kindness. It affects the quality of decisions. When people feel excluded, rushed, dismissed, or unsafe, leaders lose access to information they need.
For directors working across cultures, disciplines, and power differences, inclusion must be practical. It should show up in how meetings run, how decisions get made, how feedback is handled, and whose knowledge counts.
Watch the power dynamics around your role
A senior title changes the room. People may laugh at your jokes, agree with your first idea, or soften bad news because you control budgets, contracts, promotions, or access to donors and boards.
Do not take quick agreement at face value. Build habits that reduce pressure.
For example:
Speak last when you need honest input.
Ask people to write risks before discussing them aloud.
Invite a technical lead to brief you before a major decision.
Rotate who opens a discussion.
Give people time to respond after a meeting, especially if hierarchy or language barriers may affect participation.
Small design choices can change who speaks and what gets said.
Respect local and institutional knowledge
New leaders often bring useful outside perspective. That perspective can help question old habits. Still, outside perspective becomes harmful when it treats existing knowledge as an obstacle.
Before changing a process, ask why it exists. It may be inefficient for a reason tied to donor rules, government relationships, safety, community expectations, or past failures.
A humble leader says, “Help me understand the history,” before saying, “Here is the fix.”
This is especially important for expatriate leaders, new national leaders coming from another sector, or executives hired to lead long-standing organizations. Respect for local knowledge is not symbolic. It is a core management skill.
Make disagreement safer for people with less power
Some staff can challenge leadership with little personal risk. Others cannot. Short-term staff, junior employees, local partners, and people from marginalized groups may carry more risk when speaking candidly.
A director can reduce that risk by responding well when challenged. Do not punish tone when the content is useful. Do not label people as “negative” for naming real risks. Do not ask for honesty and then reward only agreement.
When someone raises a hard truth, try:
“Thank you for saying that. I want to understand it better.”
Then follow through. The team will watch what happens next.
Learn continuously and let the team teach you
Continuous learning is not remedial. It is part of senior leadership. The best directors keep learning because the work keeps changing.
A leader who learns openly sends a strong message: growth is expected at every level.
Build a learning plan for your first months
Do not rely on random exposure. Create a learning plan that covers the organization, the context, the people, and the technical work.
Include:
Key documents, such as strategy, budgets, risk registers, donor agreements, evaluations, and audit findings
Introductory conversations with team members across levels
Field visits focused on listening, not inspection
Briefings from technical, finance, operations, safeguarding, security, and monitoring teams
Partner and community conversations where appropriate
Time to understand past failures, not only current successes
Ask each team lead, “What should I read, who should I meet, and what should I understand before I make major changes?”
That question alone can prevent avoidable mistakes.
Seek mentorship from team members
Mentorship does not only flow from older or more senior people to newer staff. A director can be mentored by team members with deeper technical skill, community knowledge, language ability, or institutional memory.
This requires maturity. Some leaders fear that asking for mentorship will weaken their authority. Usually, it does the opposite. It shows confidence and respect.
You might ask a senior program manager:
“I would value your guidance on the history of our government relationships. Could we meet twice this month so I can understand what has worked and what has not?”
Or ask a field coordinator:
“When we visit the region, I would like you to brief me on community expectations and any sensitivities I should understand before I speak.”
This kind of mentorship is practical, focused, and respectful. It also helps team members see that their knowledge shapes leadership behavior.
Turn learning into better decisions
Learning should change how you lead. If you keep asking questions but nothing shifts, people may experience your listening as performative.
Look for ways to apply what you learn:
Adjust timelines based on operational realities.
Change communication habits based on staff feedback.
Revisit assumptions after field visits.
Protect team time when reporting demands grow.
Invite technical review earlier in planning.
Stop practices that create work without value.
When the team sees learning become action, trust grows.

Lead with humility and still provide direction
Humility does not mean hesitation. Teams need leaders who can listen well and still decide. A director who leads experts must hold both responsibilities at once.
Be humble about knowledge. Be clear about purpose. Be open to correction. Be firm about values. Be generous with credit. Be accountable for decisions.
The most trusted leaders often say some version of:
“I do not know enough yet. I want to learn from you. I will make the decision when it is mine to make, and I will explain my reasoning.”
That stance is steady. It respects expertise without hiding behind it.
For a country director, executive director, or chief of party, leading a more experienced team can become one of the greatest advantages of the role. The knowledge is already there. The task is to bring it forward, connect it, protect it, and use it in service of the mission.
Start with one step this week. Ask three people what they think leadership is missing. Listen without defending. Write down what you hear. Then act on one thing that will make the work better.
Trust rarely arrives all at once. It grows through repeated proof that the leader is listening, learning, and worthy of the team’s honesty.




Comments