Leader Member Exchange Theory in Executive Coaching
Nour
Founder, Coachful
Leader member exchange theory in executive coaching asks how a leader's working relationship with each employee affects access, support and influence. A manager can describe an open-door policy while consistently giving two familiar colleagues the context that everyone else receives after the decision.
The useful coaching question is what actually passes between people: information, commitments, feedback, help and opportunities. A closer relationship is not automatically a fairer system. This guide explains LMX, develops its limits and follows a fictional leader through an access audit, a declined offer, a revised assignment and a completed review.
Coachful is our #1 recommendation for organizing this coaching work. Use an original worksheet, agreed actions and subsequent session review to examine the leader's behavior. Software can preserve the evidence and follow-up; it cannot determine an employee's loyalty, manufacture mutual trust or replace fair management decisions.
Understand what the relationship lens changes
Graen and Uhl-Bien's 1995 theoretical paper develops LMX as a relationship-based approach. Its unit of interest is the leader–member pair, or dyad, rather than an average leadership style. Mutual trust, respect and obligation characterize developed working relationships. The authors' leadership-making approach encourages offering partnership development across the team instead of preserving a favored circle.
Consider a leader who asks everyone for ideas at the same meeting. One employee has already discussed the problem twice with the leader; another sees the choices for the first time. Counting invitations alone misses the difference. In our coaching application, ask when useful context arrived, whether there was time to use it and how the leader responded to the person's actual contribution.
Likewise, a leader's claim that an employee is dependable needs detail. Dependable at what, under which conditions, and with what support? Delivering a prepared analysis is different from agreeing to absorb every emergency. The latter may be an unsupported expectation attached to a good working history.
A relationship lens also changes the leader's accountability. The employee's contribution matters, but the leader controls many invitations, explanations and responses. A coach can help the executive examine those choices without pretending that the employee's viewpoint has already been heard. The leader's account remains one account.
Make relationship quality concrete without inventing a score
In our practical review, consider trust, respect and obligation as prompts for examining particular exchanges, rather than three boxes that certify a person. The following distinctions help an executive describe what needs attention without claiming access to another person's private feelings.
Trust needs an object. “I trust Theo” is too broad to guide a decision. Leila might rely on Theo to identify an operating risk while still needing independent approval for a budget. Likewise, Mina may trust Leila to explain a technical choice but remain uncertain whether a promised preparation window will survive an urgent request. Ask what each person is relying on and what observed event supports that reliance.
Respect must survive disagreement. A leader who praises an employee's expertise but dismisses every inconvenient finding has left an important mismatch. Look at whether the leader considers a reasoned objection, explains a rejection and credits the contribution accurately. Respect does not require accepting every recommendation. A clear, evidence-based refusal can be more useful than warm praise followed by an unexplained decision.
Obligation needs a boundary. Ask what was actually promised, by whom, for which period. A manager's past help does not silently create a standing commitment to accept extra work. An employee's accepted assignment does create a specific responsibility, but it also leaves the leader responsible for the agreed information, support and response.
These inquiries produce different actions. Unclear reliance may require an explicit check; dismissed expertise may require a real response; ambiguous obligation may require renegotiating the work. Replacing all three with “improve rapport” would conceal the choice. The leader can invite a discussion of these events without demanding that the employee report a feeling of trust.
Explain the three leadership-making phases carefully
The 1995 model describes three phases. In the stranger phase, exchanges mainly follow formal roles. An offered and accepted expansion of the working relationship can lead to acquaintance: broader information and resource exchanges, with limited tests of reciprocity. In mature partnership, mutual support and influence are more developed, and reciprocation can extend over longer periods. These are theoretical descriptions of relationship development, not a compulsory schedule.
For practical coaching, the following examples show different questions each description can prompt. They are our original applications, not a published assessment or a prescription to move every employee through stages.
| Description | Original workplace example | Useful coaching inquiry |
|---|---|---|
| Formal role exchange | A new analyst receives a task, deadline and approval route, but neither person knows how the other handles uncertainty. | Are expectations and ordinary support clear before judging initiative? |
| Testing a broader exchange | The analyst accepts a bounded comparison assignment; the manager promises protected time and a response to the recommendation. | Did both people understand and fulfill the actual offer? |
| More established partnership | Over repeated work, each can question assumptions and rely on the other's specific commitments. | Can they still disagree, maintain limits and explain decisions to others? |
The middle example matters because an offer is not an accepted commitment. A manager may call something a development opportunity while the employee sees an additional eight hours with no work removed. Clarifying the offer may reveal a workload problem rather than unwillingness to contribute.
Keep a separate distinction between professional boundaries and relationship quality. An employee can decline dinner, personal disclosure or optional stretch work while fulfilling their role well. Our recommendation is to develop working reliability without making personal closeness or unpaid availability the entry price for ordinary support.
Do not announce that someone has reached mature partnership after a successful fortnight. A limited assignment supplies evidence about those commitments under those conditions. It does not establish a permanent relationship state, confer promotion eligibility or cancel formal accountability.
Separate one strong relationship from team fairness
LMX differentiation concerns variation in relationship quality within a team. It is different from the quality of one relationship. Three productive conversations with one colleague do not show whether other people can obtain necessary information or have their work considered.
Erdogan and Bauer's 2010 study of 276 employees in 25 Turkish retail stores found that associations between LMX differentiation and several unfavorable attitudes, coworker relations and withdrawal behaviors depended on low justice climate. The study used employee surveys, supervisor reports and company records. Its single-company setting and measurement limitations constrain generalization; it was not a randomized executive-coaching trial.
The practical implication we draw is to review both a relationship and its surrounding allocation process. A leader might appropriately give a specialist more technical discussion while providing everyone affected with the decision criteria. Different work can justify different conversations. Familiarity alone is a weak explanation for withholding information needed to contribute.
Inspect both the process and its consequences. Who was considered for an assignment? Were the requirements visible? Who received the assignment and support? Who absorbed the extra work? A transparent invitation can still produce an unreasonable burden, and a reasonable allocation can still need a better explanation.
Fairness does not require publicly displaying employees' private career interests or individual coaching material. Explain the work criteria and available routes. Keep personal circumstances and confidential feedback with the appropriate audience.
Keep the evidence and measurement limits visible
The label “LMX theory” is widely used, but its theoretical status is contested. In Relational Dynamics of Leadership: Problems and Prospects (2022), Scandura and Meuser argue that LMX falls short as a leadership theory. Their critique distinguishes a relationship from the influence it may carry and questions whether common measures adequately explain the exchange process and its development over time.
That challenge is relevant to coaching: an improved relationship rating does not, by itself, explain what changed or establish that coaching caused better performance. Record specific changes in opportunity, leader behavior, employee response and work output. Other explanations, such as a clearer task, new information or reduced workload, may remain important.
If using a formal LMX instrument, establish the appropriate permissions, administration, interpretation and confidentiality arrangements. This guide does not reproduce its items or scoring. An original coaching record can support reflection without being represented as a validated LMX scale.
Do not manufacture the employee's side of a dyad from the executive's answers. A leader may believe frequent messages show support while the recipient experiences repeated interruptions. Ask for the other person's perspective through an appropriate, voluntary route. Explain who will see it, and do not promise anonymity within a tiny team where details identify the speaker.
Worked example: replace assumed disinterest with a fair offer
This entire case is fictional. Leila leads three analysts, Mina, Theo and Suki. She is considering a small pilot to improve an internal case-handoff process. She tells her executive coach that Mina is reliable on assigned analysis but “does not seem interested in broader decisions.” The coach helps Leila examine that interpretation before deciding what to change.
They review the last three handoff decisions using existing meeting invitations, briefs and decision notes. This is a limited audit of those decisions, not a relationship score or a review of every interaction.
| Evidence reviewed | Mina | Theo and Suki | What it establishes |
|---|---|---|---|
| Context before the three decision meetings | Received none of the three advance briefs | Both received all three | Unequal access to this preparation |
| Request for an option recommendation | Asked during the meeting | Asked before the meeting | Different time to prepare |
| Recorded explanation after a contribution | One suggestion rejected without a recorded reason | Reasons recorded for their proposals | An incomplete response to Mina's specific contribution |
Leila cannot infer Mina's ambition from those records. She tells Mina what she found: “I have asked you to react without the context I gave others. I also failed to explain my earlier decision. I want to correct those practices. Is there anything about receiving or discussing the brief that would help you?”
Mina replies that a written brief before the meeting would help. She prefers to put an initial recommendation in writing and discuss questions afterward. She does not request more social contact. Leila accepts that route and asks permission to use the preference when arranging the next piece of work.
Complete the offer, refusal and capacity decision
Leila's first offer is to chair a wider workshop and prepare the handoff comparison, estimated at eight hours in the coming week. Mina says she is interested in the comparison but declines the combined assignment: her existing work already requires 36 of her 40 available hours. Eight additional hours would make 44 before allowing for unexpected work.
The refusal is useful information. Leila does not remove Mina from ordinary briefings or call her uncommitted. Nor does she immediately give all the work to Theo, her familiar choice for urgent tasks. She separates the comparison from the workshop and agrees that she will chair the decision discussion herself.
After checking the work plan, Leila approves deferring a four-hour archive-cleanup report that has no dependency before the following month. The report remains assigned to Mina for that later period; it is not silently transferred to a colleague. Mina's coming week now has 32 hours of existing work, four hours for the comparison and four hours unallocated for interruptions: 40 hours in total.
The revised offer becomes a completed agreement, confirmed by both people on 2 May:
Purpose: Compare daily and twice-weekly review of internal handoff cases for a limited pilot. Make a recommendation, including one important limitation.
Output and time: A one-page comparison by 9 May, using up to four working hours. This replaces the deferred four-hour archive report in this week's plan. No workshop chairing or out-of-hours work is included.
Information and support: Leila provides the same current case-count summary and decision criteria to all three analysts. Mina may ask questions in writing. A 20-minute review with Leila is available within working hours.
Decision criteria: Capacity for the forecast 12 cases per week, a review opportunity on every working day, and no more than 90 minutes of weekly review time. Leila decides whether to authorize the pilot after checking the comparison.
Response and limits: Leila will give Mina a reasoned decision by 11 May. Mina can flag missing information or an estimate over four hours before proceeding. Accepting this task does not commit her to lead later rollouts.
Leila also checks her own time. Her 180-minute weekly allocation for this work contains 30 minutes for the common brief, three existing 20-minute individual meetings, 20 minutes for Mina's additional review, 20 minutes for checking the comparison, 20 minutes for the decision and explanation, and 30 minutes unallocated. The sum is 180 minutes. A new promise of support has a place in her schedule.
Return the actual work and an accountable decision
Leila sends the brief, but initially omits the case-count summary. Mina uses the agreed route to say she cannot assess capacity without it. Leila acknowledges the omission, sends the current summary to all three analysts and confirms that the 9 May deadline still leaves Mina the agreed preparation time. Mina checks her schedule and explicitly confirms that it does. The correction is completed before work continues.
Mina's comparison uses a planning assumption of five minutes per case. The estimate is provisional, not a measured permanent service rate. Her completed output reads:
| Option | Weekly planning capacity | Daily opportunity | Time and recommendation |
|---|---|---|---|
| Daily 15-minute review on five working days | 75 minutes supports 15 cases at the assumed five minutes each, above the forecast 12 | Yes, one scheduled review each working day | 75 minutes is below the 90-minute cap. Recommend a limited pilot. |
| Two 30-minute reviews each week | 60 minutes supports exactly 12 cases at the same assumption | No, several working days have no review | Within the time cap, but fails the daily-opportunity criterion. Do not choose for this pilot. |
Mina adds the limitation: unused time on a quiet day cannot handle a later burst automatically. A day with four cases would need 20 minutes at the assumption, beyond its scheduled 15. The pilot needs an exception decision rather than a claim that weekly capacity guarantees daily completion.
Leila checks the arithmetic and consults the operating owner, Suki, about the actual review allocation. Suki confirms that the 75 minutes replace 75 minutes of an existing 90-minute weekly handoff-administration block. They are not added to her full workload. The remaining 15 minutes in that block can cover a small overrun; further work requires Leila to reprioritize before it is accepted.
On 11 May, Leila authorizes a ten-working-day pilot with Suki as operating owner. She records why the daily option meets all three stated criteria and why the twice-weekly option fails one. Cases needing more time are flagged to Leila for a capacity decision; the pilot does not promise same-day completion of every case. Mina has supplied the analysis, not accepted operating ownership.
Leila returns that explanation to Mina and shares the decision and relevant operating instructions with Theo and Suki. She credits Mina's comparison, including its limitation. Mina replies that the explanation answers her question about how her contribution was used. This is an actual response in the fictional case, not a conclusion supplied by the coach.
Review the relationship and the wider consequences
At the end of the fictional pilot, Suki reports 24 cases and 148 minutes of actual review work across the ten working days. The first week used 80 minutes, including a four-case day that took 20 minutes and used five of that week's 15-minute remainder. The second week used 68 minutes. Against the two existing 90-minute administration blocks, 10 minutes remained in the first week and 22 in the second: 32 minutes altogether. Leila does not treat spare time in the second week as if it had covered the earlier burst. No further time was taken from colleagues.
The daily review opportunity occurred on all ten days. That does not mean every case was resolved that day; two needed additional information and were still open at the final review. Leila retains a further service decision about those cases. The small pilot is evidence about this arrangement, not proof of a permanent operating solution.
The relationship review separately examines Leila's commitments. All three analysts received the corrected common information before preparing; Mina chose a usable contribution route; the revised workload fit; Leila explained the decision on time. Her own relationship-work allocation took 165 minutes, leaving 15 of the planned 180 unused, rather than the originally reserved 30.
Mina says she can now see a route for contributing, but wants to see whether advance information remains available during a busy month. Theo says the common brief reduced repeated questions but asks whether he will still have specialist discussions. Leila confirms that relevant specialist work continues; necessary team context is shared, while confidential personnel matters remain restricted.
Leila and Mina agree to review the information route again on 8 June. Mina declines a proposed standing workshop-lead role and keeps the bounded analysis role for now. Leila accepts the decision. Neither person declares mature partnership achieved. The useful result is a corrected working practice and a kept commitment, with confidence in its continuation still unsettled.
Use Coachful to keep reflection separate from employer assessment
Create an original worksheet for the executive to record an observed exchange, the evidence, their interpretation, the employee's actual response, their own next commitment and the review date. These are coaching prompts, not copied LMX instrument items or a validated score. Distinguish a private journal entry from material intentionally submitted to the coach.
When opening a submitted form or worksheet, the coach can use Coach review to mark it Reviewed or Follow up and save private review notes. Those notes are private to the authorized coach team. They do not deliver feedback to the client and do not appear in the response PDF. Discuss the actual feedback in a session or an appropriate private client conversation.
Use Tasks for the executive's agreed actions, such as sending a corrected brief or checking whether the other person received an explanation. A completed task does not establish employee agreement or a fair allocation. Record the actual reply or decision separately. My Coaching can bring preparation and next actions into the client's ongoing work.
Check recap sharing before including sensitive employee information. Automatic session recap sharing is the default; review the approval setting and relevant Session Type overrides before promising review before release. Agree any sponsor summary and minimize unnecessary names or personal circumstances. See Coachful's features and our guide to client data privacy for the surrounding workflow.
Run a practical LMX-informed coaching review
- Choose a bounded question. Select one decision or opportunity pattern rather than rating the executive's entire team.
- Inspect actual exchanges. Compare relevant context, response and support records. Keep an interpretation separate from what the record shows.
- Develop the model accurately. Explain the dyad, possible relationship development and team differentiation. Do not assign permanent employee categories.
- Ask through an appropriate route. Invite the person's perspective without demanding disclosure or promising protection the coach cannot provide.
- Make a complete offer. State work, time, support, choice and decision authority. Obtain the actual answer and resolve capacity before calling it agreed.
- Test the leader's side. Check whether context, support and explanation arrived as promised. Repair a failure explicitly.
- Review two sets of results. Examine the specific relationship and the effects on other people, workload and work quality.
- Choose the next decision. Continue, revise or end the experiment on the evidence. Escalate formal employment concerns through appropriate organizational processes.
For a complementary way to examine observable conversational behavior, use our trust dashboard guide. Keep its categories distinct from LMX and from formal performance evidence.
Troubleshoot the patterns that distort the work
“Everyone was invited, so access was equal.” Inspect preparation, timing and usable routes, not only attendance. A meeting invitation can arrive after the real options have already narrowed.
“The employee declined, so they are not interested.” Return to the exact offer and answer. An oversized assignment, missing information or a different development priority may explain the refusal. Do not make optional participation a hidden test of loyalty.
“My strongest relationship should carry the repair.” Count that person's time and authority before asking for mentoring or emergency cover. Repairing exclusion by overloading a dependable colleague creates another problem.
“Better rapport resolves the performance concern.” Retain clear work standards and appropriate support. A specific recurring error still needs evidence, feedback and the correct management process. Coaching the leader's relationship behavior does not erase the work issue.
Frequently asked questions
Does LMX require an in-group and an out-group?
Those labels belong to its history; they are poor permanent labels for employees. Use the relationship lens to examine opportunities and commitments while reviewing the fairness of the team process.
Does fair treatment mean identical relationships?
No. Relevant roles, interests and support needs can differ. Explain work-related differences and preserve access to necessary information without demanding equal personal closeness.
Can a coach assess both sides from the leader's worksheet?
No. It records the leader's account. Another person's perspective requires an appropriate actual response, and any formal assessment needs its own permissions, handling and interpretation arrangements.
Is declining stretch work evidence of low LMX?
A refusal alone does not establish relationship quality. Clarify the work, resources and reason the employee chooses to share. Continue ordinary support and evaluate actual role performance appropriately.
Will an LMX-informed intervention improve performance?
No outcome is guaranteed. A bounded experiment can show whether particular commitments were kept and what happened to the work. It cannot isolate coaching's causal effect or establish permanent trust from a short case.
