In Short
Managing someone with deeper technical knowledge than you does not strip you of authority. Your role gives you legitimate ground to address behaviour, professional standards, and team impact regardless of who knows more about the work itself. Prepare carefully, lead with what you observed, and keep the conversation anchored to outcomes.
A difficult conversation manager approach addresses performance, behaviour, or interpersonal concerns between a manager and an employee directly. It requires clear preparation, specific observations, and the courage to speak plainly about impact, even when the employee holds deeper subject matter knowledge than the manager does.
I watched a good manager shrink once. She had run operations for twelve years. She was sharp, trusted, and fair. But she had a senior engineer on her team who made her feel like she did not belong in the same room. Every time she tried to address his behaviour, his dismissiveness, his tendency to override colleagues without explanation, he buried her in technical language until she backed down. She told me later: "I kept thinking, who am I to challenge him? He knows this stuff inside out." That belief cost her the respect of every other person on that team.
A difficult conversation manager situation like that one is one of the most common traps in leadership. Your authority is real. Your responsibility is real. Neither of those things disappears because the person across from you has a deeper understanding of the code, the system, or the science. What disappears is your confidence, if you let it. This article gives you a process to hold that conversation well.
What You Need to Settle Before You Say a Word
The trap that catches most managers before a difficult conversation even begins is confusion about what kind of authority they actually have. You do not need to know more than your employee to manage them well. You need to be clear on your lane.
Your lane is this: behaviour, professional standards, team relationships, and outcomes. Their lane is the technical work itself. These are distinct. When a senior developer dismisses a colleague's concern without explanation, that is a behaviour concern. It does not matter whether the developer was technically correct. How they handled it is yours to address.
Before any conversation, write two things down. First, the specific thing you observed: what happened, when it happened, and who was affected. Second, the impact: what changed as a result, what risk it created, or how it affected the team. If you cannot write those two things clearly, you are not ready to speak.
This preparation is not bureaucratic caution. It is the foundation your confidence will stand on. If you walk into that room with a vague sense that something is wrong, a skilled expert will sense the gap and the conversation will slide away from you. If you walk in with two clear sentences you could read aloud, you stay on solid ground.
"The Conversation You're Avoiding Is the One You Need to Have."
"The Conversation You're Avoiding
Is the One You Need to Have."
Stop rehearsing conversations you'll never have. Say It Right Every Time gives you 115 word-for-word scripts and 16 proven frameworks to speak with confidence in every conversation that matters.
The Six-Step Process for Managing the Conversation
Step 1: Open Without Apology
Start the conversation by naming its purpose clearly. Do not open with qualifications about your own limitations. Do not say "I know you understand this better than I do, but..." That sentence hands away every ounce of authority before you have used it.
Instead, say something direct: "I want to talk about what happened in Tuesday's planning meeting. Specifically, how the discussion ended and what effect that had on the team."
You are naming an event and signalling a purpose. That is enough. A clean opening sets the frame for everything that follows. If you struggle to start this kind of conversation without it becoming immediately tense, the preparation in that linked piece will help.
Step 2: State What You Observed, Not What You Concluded
This is where most managers drift into trouble. They say what they think the behaviour means rather than what they actually saw. "You are dismissive of your colleagues" is a conclusion. "You interrupted Marcus three times before he finished his point, and then the room went quiet for the rest of the session" is an observation.
State the observable facts first. Then pause. Give the employee a moment to respond before you move forward. This matters especially with technical experts, because sometimes there is genuine context you do not have. You want to hear it. Just not as a way of abandoning the concern.
Step 3: Name the Impact Without Inflating It
After you state what you observed, name what it cost: the team, the project, or the working relationship. Be accurate, not dramatic. "Three people came to me after that meeting to say they did not feel they could contribute" is specific and honest. "The whole team is demoralized" is an inflation that invites a counterargument.
This step is where the conversation earns its weight. Impact is the reason for the conversation. If an expert employee is going to take your concern seriously, they need to hear that something real was affected, not just that you personally felt uncomfortable.
When conflict patterns like this one persist between colleagues, the breakdown goes deeper than a single conversation. The D.E.A.L. Method for resolving conflicts that fracture team dynamics offers a structure for those longer-running situations.
Step 4: Invite Their Perspective with a Genuine Question
Ask a real question and then listen properly. Not "Do you see how that came across?" which is not a question at all. Something open: "What was happening for you in that moment?" or "How did you see that conversation going?"
You may hear something that adds genuine context. A technical expert may have known that Marcus's approach carried a serious risk the rest of the room was not aware of, and they handled the pressure badly. That does not excuse the behaviour, but it shapes how you respond.
What you are watching for in this step is whether the employee engages honestly or whether they deflect into technical detail to move you away from the interpersonal concern. If they do deflect, name it calmly. "I hear that the technical constraints were real. I want to come back to how the room was affected." That sentence keeps you in the conversation without dismissing them.
If you feel a defensive reaction rising in yourself during this exchange, the C.O.R.E. Framework for staying grounded during tense workplace conversations gives you a reliable method for keeping your footing.
Step 5: Be Clear About What Needs to Change
This step is where many managers soften into vagueness because they feel awkward directing someone who clearly knows more than they do. Do not soften here. Be specific.
"What I need from you going forward is this: when you disagree with a colleague's direction in a meeting, you flag the concern without cutting them off. If the technical risk is serious, bring it to me before the meeting so we can address it together."
That is a clear, actionable expectation. It does not require you to have technical knowledge. It requires you to hold a professional standard. Your employee can respect that, even if they find it inconvenient, because it is fair and it is specific. Vague requests like "just be more collaborative" give them nothing to work with, and they give you nothing to return to in a follow-up.
Step 6: Agree on a Next Step and Name It
Close the conversation by confirming what happens next. A specific follow-up, not a vague intention. "I will check in with you in two weeks. I will be paying attention to how the next two team meetings go. If it is working, I will tell you. If there is still a concern, we will talk again."
That structure shows you are serious without being punitive. It gives the employee clarity about what success looks like. And it creates a natural moment for recognition if they do make the adjustment, which is exactly what you want, because recognition after a difficult conversation builds more trust than any single piece of praise in a calmer moment.
When the Conversation Happens Remotely
Remote difficult conversations with technical experts carry an additional risk: the employee can control how much of themselves they reveal. On a video call, they can turn off their camera, claim a bad connection, or respond in clipped sentences that give you almost nothing to work with.
A few adjustments make a real difference. First, send a brief note before the call that names the topic: "I want to talk about how Tuesday's planning session ended. I will call you at two o'clock." Do not write the full concern in the message. Just name the subject so they are not ambushed, and so they arrive present rather than defensive.
Second, keep the camera on for both of you if at all possible. Body language carries more of the conversation than words do in these moments. Third, speak a little more slowly than feels natural. The slight delay in digital audio means that pauses, which are important in any difficult conversation, need to be held a beat longer than in person.
If tensions between team members have built to the point where remote conversations are not enough to repair the damage, the B.R.I.D.G.E. Method for rebuilding relationships after genuine breakdown offers a structured path forward.
Where Managers Go Wrong in This Situation
Most of the errors I have seen in this specific situation come from the same root: the manager's discomfort with the knowledge gap. Here is where that discomfort leads people astray.
The mistake: Trying to prove technical competence during the conversation.
Why it happens: The manager feels exposed and reaches for credibility by demonstrating they understand the work.
What to do instead: Stay in your lane. Your authority is not technical. Say what you observed and what it affected. Do not wander into territory the employee knows better than you.
The mistake: Over-apologising for not knowing the technical detail.
Why it happens: It feels respectful. It is actually disarming.
What to do instead: Acknowledge their expertise once, briefly, and then move on. "You know the technical side of this better than I do. What I need to talk about is how this situation played out with the team."
The mistake: Accepting a technical explanation as a reason to drop the behavioural concern.
Why it happens: The explanation sounds credible and the manager does not want to seem ignorant by pushing back.
What to do instead: Separate the two things clearly. "I hear that the technical approach was sound. That is not what I am raising. I am raising how the decision was communicated." A useful framework for handling conflict when it surfaces in real time during a meeting can help you practise this kind of separation under pressure.
The mistake: Ending without a clear expectation.
Why it happens: The conversation felt tense and the manager wants to close on a positive note.
What to do instead: Warmth and clarity are not opposites. You can close with genuine respect and still name exactly what needs to change. Both things matter.
When a defensive reaction comes up during the conversation itself, the C.O.R.E. Framework for staying calm when feedback triggers defensiveness gives you a practical method for recovering without losing ground.
Your Pre-Conversation Checklist
Use this before every difficult conversation with a technical expert. It takes five minutes and it will change how you walk into the room.
- Write down the specific event you are addressing: what happened, when, and who was present.
- Write down the concrete impact: what it cost the team, the project, or the working relationship.
- Write two open questions you will genuinely listen to the answers of.
- Write the one clear expectation you will state before the conversation ends.
- Identify your own discomfort: what part of this conversation makes you want to back off? Name it privately so it does not catch you off guard in the room.
- Decide when and how you will follow up, and plan to name that at the close of the conversation.
That list is not complicated. But in my experience, most managers who walk into these conversations without it find themselves reacting to the employee rather than leading the exchange. Preparation is not a sign of anxiety. It is a sign of respect, for the conversation and for the person you are having it with.
For situations where two colleagues are locked in a pattern of refusing to cooperate and your role is to intervene as the manager, the D.E.A.L. Method for defusing tension between colleagues gives you a specific process for those triangulated conversations.
Frequently Asked Questions (FAQ)
What is a difficult conversation manager approach when the employee is more technical?
A difficult conversation manager approach in this context means leading from your role, not your technical knowledge. You focus on observable behaviour, outcomes, and team impact rather than challenging the employee on technical grounds. Your authority is legitimate even when your expertise is narrower.
How do you prepare for a difficult conversation with a technical expert?
Write down the specific behaviours or outcomes you need to address before the conversation begins. Separate what you have observed from what you have assumed. Prepare two or three open questions that invite the employee to explain the technical context, so you can respond to facts rather than impressions.
How do you maintain authority in a difficult conversation when you lack technical knowledge?
Your authority as a manager does not come from knowing more than your team. It comes from your responsibility for outcomes, team health, and professional standards. Stay in that lane. Address what you can see, the behaviour and its impact, and let the employee own the technical detail.
What should you avoid saying in a difficult conversation with a subject matter expert?
Avoid language that attempts to challenge or correct their technical judgement when you lack the knowledge to do so credibly. Do not bluff, and do not over-apologise for not knowing. State clearly what you observed, what impact it had, and what you need to change. Keep the conversation grounded in outcomes.
How do you stop a technical expert from derailing a difficult conversation?
When an employee uses technical complexity to redirect the conversation away from a behavioural or professional concern, name what is happening calmly. Say something like: I understand the technical context matters. What I need us to focus on right now is the impact on the team. That redirection keeps you in control.
How do you follow up after a difficult conversation with an expert employee?
Send a brief written summary within 24 hours that confirms what was agreed, not a formal document, just a clear note. Schedule a follow-up conversation within two to three weeks to review progress. This creates accountability without surveillance and shows the employee you take the outcome seriously.
The knowledge gap between you and your most technically skilled people is not the obstacle. The obstacle is the belief that it disqualifies you from leading. It does not. A difficult conversation manager approach is built on clarity about what you saw, what it cost, and what you need to change. That clarity belongs to your role. Use it.
