Motivational Interviewing in Executive Coaching: A Case

Motivational interviewing in executive coaching can support a conversation about mixed feelings toward a specific change. A leader may want colleagues to hear about project uncertainty earlier while also fearing that an incomplete update will create confusion. Exploring that ambivalence is different from persuading the leader to accept a sponsor’s agenda.

This guide develops the four MI tasks, OARS skills, language distinctions and importance-versus-confidence questions. A complete fictional example follows a leader’s chosen reporting experiment through missing authority, legitimate criticism, a missed deadline and a limited sponsor report. The worksheet organizes the conversation; it does not diagnose motivation.

Use current terminology and proportionate evidence

William Miller and Stephen Rollnick developed MI from clinical work. Their fourth-edition update describes a broader helping approach and uses partnership, acceptance, compassion and empowerment for its underlying spirit. Empowerment replaces the earlier spirit label evocation; evoking remains one of the four tasks.

In executive work, partnership means the coach contributes process skills while the client contributes knowledge of their situation. Acceptance includes respecting the person and their choice; it does not mean endorsing every action. Compassion keeps the client’s welfare central. Empowerment recognizes strengths and agency instead of treating the coach as the source of the client’s reasons.

Miller’s 2023 review, The Evolution of Motivational Interviewing, describes a substantial clinical literature with variable outcomes across contexts and practitioners. It is a developer’s review, not an executive-coaching trial. Clinical findings cannot be converted into a promised improvement in leadership performance, project reporting or business return.

Use an accurate description of your competence. Reading this guide is not training in clinical treatment or evidence that a conversation meets a formal MI fidelity standard. The example below illustrates MI-informed coaching decisions, without claiming that it was independently coded as competent MI.

Agree what is open to change

Specify the direction before selectively exploring reasons for change. “Become a better executive” is too broad. “Explore whether a proportionate earlier update would help colleagues respond to routine forecast uncertainty” gives the person something concrete to examine.

Distinguish a developmental choice from a role requirement. A material-risk notification required by policy is not an optional experiment in motivation. Clarify the real obligation with its authorized owner; coaching can then address support, understanding or practice within the actual boundaries.

A sponsor may describe the goal as “stop pushing back.” Ask what behavior and purpose are meant and hear the participant’s account. Legitimate disagreement, a missing decision right or an unreasonable workload should not disappear into a label such as low motivation.

MI is directional around an agreed change. It is not identical to neutrally listing equal pros and cons of every possible choice, a distinction Miller’s review discusses. Direction does not authorize covert persuasion: the person needs to know and accept what you are exploring and remain able to challenge the focus.

Use the four tasks flexibly

The MINT introductory guide explains the relationship and communication skills, although that page retains older third-edition labels. Use the developers’ fourth-edition terminology deliberately. Engaging, focusing, evoking and planning are interwoven tasks, not four boxes that must be completed once in order.

Engaging: understand this person’s situation

Listen for the client’s experience and check your understanding. An executive may arrive with a sponsor’s brief, a previous difficult reporting exchange and doubts about how coaching information will be used. Asking for a goal before addressing those concerns may produce a compliant answer rather than a useful working relationship.

An original prompt is, “What would help this conversation be useful, and what are you concerned it might become?” If the client says your questions feel leading, pause and repair the working relationship. More questions about benefits will not resolve that concern.

Focusing: choose a specific direction together

Clarify which part of the issue the client wants to examine. Earlier reporting could mean raising a tentative estimate, escalating a confirmed risk or asking for a missing decision. These actions have different conditions and may involve different owners.

Ask, “Which part is a choice you want to explore, and which part needs a factual answer about your responsibilities?” Record the actual focus. If the client reveals a misunderstood requirement, return to clarification rather than continuing toward the original plan merely because the coach prepared it.

Evoking: hear the client’s own reasons

Explore what matters about the agreed direction, including existing strengths and circumstances that make it difficult. The coach need not provide a sales pitch for the change. A client’s reason might be giving colleagues time to adjust dependencies, rather than appearing more confident to a sponsor.

Ask for detail: “When would an earlier conversation make a useful difference?” Then listen to the answer, including a reason your preferred approach may be unsuitable. A past punitive response may be relevant evidence about the environment, not an irrational fear to overcome.

Planning: develop a chosen, feasible next step

Planning concerns how to proceed when that is useful. It can include information, skill practice, a request for authority or a decision to narrow the action. Someone already willing to act may need this work rather than repeated questions about why change matters.

Ask, “What do you want to do, and what has to be agreed before it can happen?” Check timing, receiving owners, support and review. Considering an option is not accepting a plan. If the person does not choose an action, record that honestly instead of manufacturing a commitment to finish the session.

Use OARS without turning it into a script

OARS names open questions, affirmations, reflections and summaries. The purpose is responsive understanding and guidance, not achieving a quota of techniques. A closed factual question can also be useful when a reporting rule or deadline needs clarification.

A reflection can go beyond repeating words, but it remains a guess about meaning. Do not turn “You may be concerned about credibility” into a diagnosis. Our active-listening guide develops that practical distinction.

The fourth edition uses fixing reflex for the impulse previously called the righting reflex. Notice when you rush to solve the client’s problem. Advice is not automatically incompatible with MI: ask what the client needs, offer relevant information with permission and ask what they make of it. The developers call this Ask–Offer–Ask.

Distinguish reasons, commitment and discord

Change talk favors movement toward the particular change; sustain talk favors keeping the current situation. “I want fewer late surprises” and “I do not want an unconfirmed date treated as a promise” can occur together. Understanding the latter may reveal a necessary condition for a responsible plan.

The developers’ terminology also distinguishes preparatory language about desire, ability, reasons or need from language about commitment, readiness and steps already taken. “I could ask Cal” is not the same as “I will email Cal tomorrow,” and neither proves Cal has answered.

Discord concerns the working relationship. “You are only listening for reasons I should agree” asks the coach to examine their conduct. It is different from a client’s concern about the proposed reporting change. Do not describe either as a resistant personality.

Listen for what the person actually says and does. A coach’s selective summary can upgrade interest into commitment or remove an inconvenient limit. Invite correction, and change the record when the client supplies it.

A complete fictional executive example

Amina is a product director. Her sponsor, Bea, initially wants “less pushback and earlier warnings.” Amina wants colleagues to have useful information without treating every emerging uncertainty as a final failure. On 30 October 2026, they and coach Jon agree by email to two fifty-minute coaching sessions on 3 and 17 November, 10:00–10:50 Europe/London.

The agreed focus is proportionate earlier reporting of routine project uncertainty. Formal risk-reporting duties remain unchanged. Bea accepts that coaching is voluntary and that private dialogue, ratings and worksheets will not be included in sponsor reporting. Amina may approve an exact limited service summary later. The case is fictional, not a claim about a real company’s policy or an MI outcome study.

Hear ambivalence and correct the coach’s first account

Amina: I want fewer last-minute surprises, but I do not want to alarm people whenever a date is uncertain.

Jon: You are afraid people will think you have lost control.

Amina: That is only part of it. Last time, a tentative date was copied into the delivery plan as if it was confirmed. You are making this sound entirely like my confidence problem.

Jon: I put too much emphasis on an internal explanation. There was a real problem in how the information was used. You want earlier coordination and a clear distinction between a working assumption and an accepted date.

Amina: Yes. Other teams could look at dependencies sooner if the status was clear.

Jon: What would need to be different for that to be useful?

Amina: We need the reporting expectation and a person who will verify a date. I am considering asking Cal what belongs in the routine update.

Jon first writes “Amina will trial three early updates.” She corrects both the commitment and quantity: she has not agreed to any trial. They replace that note with “Considering clarification with Cal; no reporting trial agreed.” Repairing that record matters more than producing stronger-sounding commitment language.

When Jon asks what she wants next, Amina chooses to email Cal by noon on 4 November. The case has now moved from considering an option to a specific commitment. Cal has not yet agreed to anything.

Use importance and confidence for different questions

Amina chooses to use two zero-to-ten conversation scales. For her, importance means how much a proportionate earlier routine update matters now, with zero meaning no importance and ten extremely important. Confidence means how sure she feels she can carry out the proposed update under current conditions, with zero not at all sure and ten completely sure.

She gives importance eight and confidence three. Her explanation is more informative than the numbers: coordination matters, but the current format and authority are unclear. Jon asks what supports the three and what makes the task difficult; he does not require her to justify a higher score.

These are Amina’s descriptions, not validated motivation measures or comparisons with other executives. She can decline the scale. A different confidence rating would not establish that Cal’s answer, time or authority exists.

Resolve the practical condition before the trial

Amina sends Cal her question at 11:40 on 4 November, twenty minutes before her chosen noon deadline. Cal, the reporting-policy owner, replies at 10:00 on 5 November. He distinguishes mandatory escalation of confirmed material risks from the routine uncertainty updates under discussion. Those obligations are not postponed by coaching.

Cal confirms that the proposed trial concerns routine uncertainties below the formal escalation threshold. He accepts four fields: what changed, what remains unknown, the current possible impact and any decision or verification request. Tentative dates must be labeled unconfirmed. Luis, the receiving project lead, accepts this format in their project email thread at 13:00 that day.

Amina then chooses two reporting opportunities, 6 and 12 November, both by 10:00. Luis accepts receiving them in that same project thread. This is the actual agreed trial, replacing Jon’s earlier unchosen three-update note.

Retain the first report’s missing owner

At 09:50 on 6 November, Amina sends:

The supplier file may arrive on 16 November rather than 12 November. That date is unconfirmed. The testing window could narrow if it changes. No schedule decision is requested yet. Can we keep the 12 November preparation checkpoint while the supplier date is checked?

The report arrives ten minutes before its deadline. At 11:10 Luis replies that the uncertainty is useful but the verification owner is missing. He will not change the testing schedule on an unconfirmed date. That criticism is legitimate; the draft’s phrase “is checked” conceals who will do the work.

On 9 November Amina asks Eli, the procurement owner, to verify the supplier date by noon on 13 November. Eli accepts at 11:30 that morning. Amina adds the named owner and accepted checkpoint to the thread. Luis acknowledges the clarification at 14:00. The first report is repaired; it was not complete on its initial send.

Keep the second miss visible

On 12 November, Amina has the agreed verification route but waits for a conclusive result instead of reporting the remaining uncertainty at 10:00. She sends at 15:20, five hours and twenty minutes late. The message states that Eli is checking by the accepted 13 November noon checkpoint and that the supplier date remains unconfirmed.

Luis acknowledges the message at 16:00 and retains the existing schedule pending verification. The report gives him a named route, but Amina has missed her chosen timing. On 13 November, Eli reports at 11:50 that the supplier has not confirmed a final date. A timely verification response can still contain an unresolved answer.

The trial therefore contains two planned opportunities and two eventual sends, one timely and one late. The first send required a later owner correction. No downstream schedule change, cost saving or general improvement in executive confidence has been demonstrated.

Complete the eight-field worksheet and actual review

At the 17 November session, Jon’s draft summary says Amina has established a successful early-reporting habit. She asks him to remove that conclusion. Two opportunities, one late, do not establish a habit. They preserve the narrower record below.

Her importance and confidence descriptions remain eight and three. Jon accepts them without calling the unchanged numbers failure. Amina says the format helps, but criticism and workload still make earlier sending difficult. No additional reporting experiment or later coaching session is silently added.

They use the remaining time to rehearse one reply to a copied tentative date: “Please keep this labeled unconfirmed. Eli owns verification; it is not an accepted delivery date.” This is practice, not evidence that a later colleague has followed it.

Close the sponsor loop with actual permission

Bea asks for confirmation that Amina is now “less resistant.” Jon explains that this is not an agreed or supported assessment. In the final session, Amina approves this exact alternative: “The two agreed coaching sessions are complete. Amina clarified a routine update format and tested two reporting opportunities: one timely, one late. Formal reporting duties remain unchanged. No further trial is agreed.”

Amina explicitly declines sharing the dialogue, ratings and worksheet. Jon sends only the approved summary to Bea by their existing service email at 12:00 on 17 November. Bea acknowledges at 14:00 and accepts the limited service report. Receipt is known; satisfaction with Amina’s performance is not inferred.

The engagement closes that day. It contains one hundred live coaching minutes, not one hundred minutes of whole-project work. Jon’s preparation and closing administration, Amina’s reporting, Cal’s advice and others’ receiving work are outside that live-time figure and are not quantified. No economic or causal return is calculated.

Recognize when willingness is not the missing condition

Imagine a leader already willing to delegate a decision but lacking required approval from another executive. Asking for more reasons to delegate does not change that authority. Planning might instead involve clarifying the permitted boundary or making a proposal to the actual policy owner.

This is a short illustration, not another observed case. Distinguish it from ambivalence: a person can want the action and still be unable to authorize it. Permission from a coach cannot substitute for organizational approval.

Likewise, if a participant declines the sponsor’s proposed development goal, examine the engagement rather than manufacturing change talk. A transparent revision or ending may be more responsible than continuing a service whose purpose is disputed.

Use Coachful to preserve the client’s actual choice

We build Coachful. Coachful is our #1 recommendation for organizing a chosen action and its review in a coaching workspace. Its records can hold the eight-field worksheet and agreed next step; they cannot determine MI competence, infer motivation or establish that an external owner accepted a request.

Use Clients > the client > Worksheets & resources to deliberately assign the appropriate worksheet. Explain the response audience and agree what belongs in it. Copying a private-resource link alone does not grant access, and a staff preview does not prove client submission.

A goal can connect the client’s actual tasks and habits through Daily momentum. Enter a task only when it reflects a chosen action. “Considering whether to ask Cal” should not become a completed trial; a task checked off does not prove a reply or policy approval. Keep the relevant correspondence in the organization’s authorized system and bring an appropriately limited account into coaching.

The ICF Code of Ethics addresses roles and information exchange. Apply the actual sponsor agreement rather than treating payment as permission to share private discussion. Our coaching-effectiveness research guide helps separate service observations from broader evidence, and Coachful’s features describe the workspace functions. No real client record or setting was changed for this case.

Develop the skill with observation and feedback

MINT’s learning guidance treats practice, observation and feedback as important to developing MI skill; an introductory workshop alone is not competence. Use suitable training and consent-based review, with a clear information-handling arrangement for any practice recording.

Ask whether your questions supported the agreed focus, whether a reflection was corrected and whether you noticed information that challenged your preferred plan. A client saying the conversation feels leading is useful feedback about your practice, not an obstacle to score away.

Frequently asked questions

Are the four tasks a fixed sequence?

No. New information can require returning to engagement or focusing. Amina’s concern about how a date was used had to be heard before planning the trial.

Should the coach remove sustain talk?

Understand its relationship to the specific change. A concern may reveal a missing condition or real consequence. Do not turn a reason for caution into a character judgment or hide it from the record.

Does a confidence score prove readiness?

No. Define what the person is rating and hear their explanation. Their number does not supply time, authority or a response from another person.

Can MI make someone accept a sponsor goal?

It should not be used as covert persuasion. Clarify actual duties and the purpose of coaching openly. A participant’s agreement or refusal must remain real.

Does this example show MI caused better reporting?

No. It is an original fictional application with a mixed trial and contributions from several people. One timely send, one late send and a repaired omission do not establish a causal effect or sustained performance change.