Leading a Senior Direct Report Without a Status Contest

An experienced direct report may not yet trust your judgment, understand your value, or see how you will help them succeed. Your job is not to win a ranking contest; it is to make the reporting relationship useful, fair, and predictable while remaining accountable for the team's outcomes.

Treat the tension as a working relationship to improve, not a verdict on either person's worth. The practical goal is mutual confidence: they can rely on your management, and you can rely on their expertise and professional conduct.

Three truths can exist together:

• They may know more than you in important areas.
• You remain ultimately accountable for team outcomes and for making decision rights clear; you own only the decisions assigned to your role.
• Neither fact requires either person to become smaller.

A helpful internal sentence is: "I do not need to out-expert them. I need to lead a system in which their expertise produces strong outcomes."

A status dynamic is a pattern in which one person appears to question another person's standing or authority. Diagnose it from observable behaviour and work impact, not from guesses about motives, personality, age, or career history.

Separate facts from interpretations before you act:

Layer	Example	What to do
Observation	They interrupted your answer three times in the planning meeting	Record the specific behaviour
Impact	The decision stayed unclear and two people asked who owned it	Name the work consequence
Possible explanations	Concern about quality, unclear roles, low trust, habit, or disagreement	Hold several hypotheses lightly
Test	Ask what they needed from the discussion and how they see decision ownership	Learn before concluding

Use neutral questions that make the relationship discussable:

• "I noticed we revisited the decision after I closed it. What concern was still unresolved for you?"
• "Where do you think my role is helping today, and where is it adding friction?"
• "When you challenge a direction in the room, what outcome are you trying to protect?"
• "What would good management from me look like on this work?"

Do not diagnose "they do not respect me" from one disagreement. Look for a repeated pattern across contexts, check the effect on the work, and give them a chance to explain what you cannot observe.

Expertise is deep knowledge or skill in a domain; management responsibility is accountability for priorities, decisions, standards, resources, and the team's environment. Respecting the first does not require giving away the second.

Make the boundary explicit and calm:

Their expertise should shape	Your management must provide
Technical options and trade-offs	A clear decision process
Risks that others may miss	Priorities and resource choices
Quality standards in their craft	Cross-team alignment and escalation
Coaching for less-experienced colleagues	Behavioural and delivery expectations
Recommendations in ambiguous situations	Final ownership when a decision is yours

Useful phrases:

• "You have more depth than I do in this domain, and I want that depth shaping the plan. I remain accountable for the final priority call."
• "I am asking for your strongest recommendation, including the risks. Once a decision is made, I need us both to execute agreed actions, represent it accurately, and use our agreed channel to request reopening if new evidence or a safety, policy, legal, or ethical concern arises."
• "I will not pretend to know what you know. I will make sure the right expertise, constraints, and stakeholders are present when we decide."

Delegation is not abdication. You can give them broad ownership while setting the outcome, constraints, decision rights, checkpoints, and support they can expect from you.

Trust grows when someone can predict that your words and actions will match. Use the first 30 days to learn with curiosity, make small commitments, and follow through visibly rather than trying to impress them with a grand gesture.

Period	Focus	Actions	Evidence of progress
Days 1–7	Learn their world	Ask about goals, strengths, frustrations, risks, and preferred working style	You can describe what they are protecting without caricature
Days 8–14	Remove one real obstacle	Resolve a dependency, clarify ownership, or improve access to a decision-maker	A concrete part of their work becomes easier
Days 15–21	Share responsibility clearly	Agree on decisions they own, decisions you own, and when to consult	Fewer reopened decisions and fewer surprises
Days 22–30	Review the relationship	Ask what is working, name one improvement for each of you, and renew commitments	Both people can state the working agreement

Keep a small commitment ledger for yourself:

Commitment:
Owner:
Due date:
Current status:
Next update:
Closed with the person on:

Choose commitments you can keep. One obstacle removed on Tuesday builds more trust than five ambitious promises forgotten by Friday.

A working agreement is an explicit set of expectations for how two people communicate, decide, challenge, and follow up. A dedicated one-to-one conversation turns hidden assumptions into choices both people can inspect and improve.

Open without accusation:

"Your migration-risk analysis caught a dependency the rest of us had missed and changed the rollout sequence. I want our relationship to use that depth fully and also make ownership clear. Could we spend this conversation agreeing how we work together when we align and when we do not?"

Cover five topics:

1. Success: "What outcomes would make the next quarter successful for you and for the team?"
2. Strengths: "Where do you want me to lean most on your expertise?"
3. Support: "What friction should I remove, and what support is useful rather than intrusive?"
4. Challenge: "How should we challenge each other before a decision? What should happen after it?"
5. Feedback: "How do you prefer to receive feedback, and how will you tell me when my management is getting in your way?"

Close with specifics, not a warm but vague ending:

"I heard that you want early context, room to shape technical choices, and no last-minute surprises. I need risks raised directly, decisions challenged before closure, and agreed direction supported afterward. I will send the agreement today and review it with you in two weeks."

Document the agreement in a few bullets. It is a shared operating note, not a contract designed to catch them out.

Managerial credibility is confidence that your involvement improves the work. Earn it by making sound trade-offs, removing friction, and using the direct report's expertise visibly rather than competing with it.

Look for leverage only your role can provide:

• Clarify a priority that has caused repeated churn.
• Secure a decision from another team or leader.
• Protect focused time from low-value requests.
• Bring customer, commercial, or organisational context they cannot easily access.
• Resolve unclear ownership between functions.
• Give public credit for their analysis and show where it changed the decision.

Visible use of expertise sounds like this:

• "Priya's risk analysis changed the rollout sequence; we are starting with the reversible path she identified."
• "I asked Daniel to lead the design review because this is his deepest area. I will own the cross-team decision and resourcing."
• "Your recommendation was option B. I chose option A because of the regulatory deadline; I want the record to show both the advice and the constraint."

Credit does not mean automatic agreement. It means their contribution is accurately represented, considered, and connected to the outcome.

Feedback is useful information about behaviour and its effect, offered to improve future work. Give it close enough to the event to be specific, but not when either person is flooded, the setting is public, or the issue needs facts you have not checked.

Use consent as a readiness check, not as permission to avoid your responsibility:

• "I have an observation from today's review that could help our working agreement. Is now a good time for ten minutes?"
• "This is important feedback I need to give. Would later today or tomorrow morning let you engage with it properly?"
• "I want to discuss how that challenge landed in the room. Do you have capacity now, or should we hold it for our one-to-one at three?"

If they say no, agree a near-term time. If the matter involves safety, harm, policy, or an immediate delivery risk, state that it cannot wait and move to a private setting.

Praise and corrective feedback should both be specific. Do not hide a needed expectation inside a "feedback sandwich" that makes the message hard to trust.

A feedback sequence gives the conversation structure without turning it into a performance. Move from an observable event to its impact, invite their view, clarify the shared expectation, and offer practical support.

The sequence is observation → impact → question → expectation/support:

Observation
Name what happened, with a specific time and setting.

Impact
Explain the effect on the work, decision, team, or relationship.

Question
Ask for their perspective and listen for missing context.

Expectation and support
State the future standard, then agree what will help them meet it.

A complete example:

"In today's roadmap meeting, after I confirmed that reliability work would take priority, you said the decision was uninformed and reopened the debate with the wider group. The team left unclear about whether the priority was settled, and two owners paused their planning. What concern did you believe still needed to be heard?"

Listen, summarize their answer, and then continue:

"I understand that you thought I had missed the migration risk, and I want you to raise risks that serious. The expectation is that you challenge the evidence directly before closure. Once the decision is closed, execute the agreed actions and represent it accurately. If new evidence or a safety, policy, legal, or ethical concern arises, use our agreed channel to request that we reopen it. I can support that by sharing decision context a day earlier and reserving ten minutes for your risk review. Can we try that in the next planning cycle?"

The standard is about decision clarity and professional challenge, not deference to rank. If your own behaviour contributed, name it plainly: "I gave you too little context, and I will correct that. The expectation about how we challenge a closed decision still stands."

Respect means treating a person's expertise, dignity, and role as legitimate; agreement means reaching the same conclusion. You can preserve respect through a firm disagreement, and you can agree with someone while still treating them poorly.

Use this distinction in difficult moments:

Respectful disagreement	False harmony or disrespect
"I understand your recommendation and the risk behind it; I am choosing differently because..."	Pretending to agree, then quietly reversing the decision
Asking them to critique before the decision	Dismissing their concern because you are the manager
Recording their dissent accurately	Requiring enthusiastic agreement as proof of loyalty
Expecting professional execution after closure	Allowing repeated public undermining in the name of expertise

Say the principle aloud when needed: "You do not have to agree with every call. I expect you to execute agreed actions and represent the decision accurately. If new evidence or a safety, policy, legal, or ethical concern arises, request explicit reopening through our agreed channel."

Continued dismissiveness is a repeated pattern of belittling, ignoring, or undermining legitimate contributions or role responsibilities. Once you have checked context, made expectations clear, and offered support, treat recurrence as a performance and conduct issue rather than an invitation to prove yourself harder.

Use a measured escalation path:

1. Name the recurrence: cite the new observation and connect it to the earlier agreement.
2. Clarify the standard: explain the behaviour required and why the work depends on it.
3. Ask what blocks change: surface skill, incentive, workload, or relationship barriers without excusing the impact.
4. Set a review point: agree on observable behaviour and a near-term date.
5. Document factually: record events, impact, expectations, support, and follow-up.
6. Use normal management channels: involve your manager or people partner according to policy if the pattern persists or is serious.

A firm phrase:

"We agreed that concerns would be raised directly and that closed decisions would not be mocked in group settings. Yesterday's comment repeated the pattern. This needs to change. In the next two reviews, I expect you to state the risk, propose an alternative, and avoid commentary about another person's competence. I will make space for your challenge and observe the next two meetings; we will review progress on Friday."

Apply the same standard you would use with any direct report. Do not diagnose arrogance, threaten status, collect allies, or retaliate by withholding meaningful work.

Anti-patterns are tempting responses that make the relationship worse even when they briefly relieve your discomfort. Replace status-protecting tactics with actions that improve clarity, dignity, and delivery.

Anti-pattern	Why it fails	Better move
Proving you are the smartest person	Turns work into a contest and hides useful gaps	Ask for depth; contribute context and decisions
Over-deference	Creates role ambiguity and delayed accountability	Respect expertise while naming decision rights
Patronising praise	Feels strategic rather than sincere	Give specific credit tied to an outcome
Public correction for effect	Costs dignity and invites defence	Correct privately unless immediate clarity is necessary
Avoiding feedback until frustration spills	Produces vague, emotional accusations	Address a specific pattern early
Assigning motives	Makes an untestable story the centre of the conversation	Use observation, impact, and questions
Using access or information as leverage	Damages trust and team performance	Share context needed for good work
Demanding visible submission	Confuses leadership with dominance	Require shared standards and clear execution

Watch for the quieter anti-pattern of doing their work to earn legitimacy. Your role is to create conditions for strong work, make accountable calls, and coach the relationship—not to duplicate their expertise.

Leading a highly experienced direct report works when expertise and accountability reinforce each other. Build trust through curiosity, useful commitments, visible follow-through, clear decision rights, and feedback that protects dignity while holding the standard.

• Diagnose behaviour and impact; do not invent motives.
• Give expertise real influence without abandoning management ownership.
• Use the first 30 days to learn, remove friction, clarify decisions, and review the agreement.
• Make credibility visible through useful outcomes and accurate credit.
• Give timely, private feedback with a readiness check.
• Structure feedback as observation, impact, question, expectation, and support.
• Treat respect and agreement as separate.
• Escalate persistent dismissiveness through normal, documented management practice.

The test is not whether they acknowledge your level. The test is whether the relationship produces clearer decisions, stronger work, honest challenge, and reliable follow-through.

Use this checklist before and after your next one-to-one. It turns the lesson into observable preparation rather than a general intention to "build rapport."

• [ ] I can describe the behaviour and impact without assigning a motive.
• [ ] I can name the expertise I want to use and the responsibility I still own.
• [ ] I know one friction point I can remove within 30 days.
• [ ] I have made only commitments I can track and keep.
• [ ] We have discussed success, support, challenge, decisions, and feedback.
• [ ] Our decision rights are clear before the next contested decision.
• [ ] I will credit their expertise accurately and visibly.
• [ ] My feedback is specific, private, and close enough to the event.
• [ ] My script includes observation, impact, question, expectation, and support.
• [ ] I have separated respect from agreement in my language.
• [ ] I have set a review point if dismissiveness has repeated.
• [ ] I am using shared standards, not dominance, as the basis for accountability.