Awase in Executive Coaching: Work With Resistance Clearly
Nour
Founder, Coachful
Awase in executive coaching can serve as a metaphor for working with an objection before trying to overcome it. The leader checks what the other person is protecting, acknowledges what is valid and changes the proposed next step where the evidence requires it.
The useful outcome may be a revised proposal, a refusal or a delayed decision. This guide develops four conversational stages, an eight-field record and an optional fifteen-minute rehearsal. A complete fictional migration case includes a genuine objection, an unauthorized deadline, a late result and a decision that remains blocked.
Understand the martial term and the original coaching adaptation
NTNUI Aikido’s teaching vocabulary describes awase through connection and timing between physical practice partners. Aikikai Foundation describes Aikido as the martial art created by Morihei Ueshiba and explains its partner practice. Those are sources for terminology and physical context, not trials of an executive-coaching method.
Here, “blending” names an original conversation exercise. It means adjusting your response to information another person actually supplies. It does not mean physical entry, a throw, matching someone’s breathing or destabilizing their confidence. Physical martial practice belongs with appropriate instruction, rather than an improvised workplace demonstration.
The adaptation changes the leader’s task from obtaining agreement to understanding and making an accountable choice. That still allows a clear challenge: “I accept that the queue must remain available. I do not yet accept that every possible test would interrupt it. Can we examine that distinction?”
The cited descriptions do not establish that this four-stage exercise reduces stress, produces trust or improves organizational performance. Evaluate the actual conversation and subsequent work. A smooth exchange and a project approval are different outcomes.
Use four principles without dissolving the decision
The counterpart is a participant. A colleague may hold operational knowledge, responsibilities or rights the proposal overlooks. Calling their answer resistance before hearing it can hide a real defect. Treat a refusal as information to examine, rather than a symptom to diagnose.
Adjust the format. Ask whether the person needs a short summary, a written comparison or another authorized participant. Adapting timing and detail is different from imitating their emotion. A frustrated person need not become visibly calm before their factual concern counts.
Acknowledgment is precise. Recognize the valid concern without offering an untrue concession. “Protecting Tuesday dispatch matters” does not mean “Every test is impossible” or “You may insult the project team.” Keep the issue and conduct distinguishable.
The next direction is explicit. Identify what you are proposing, what remains conditional and who can decide. A warm conversation does not appoint a rollback owner or allocate an engineer. Other people retain the ability to correct, refuse or request a different process.
The HSE’s Change standard addresses timely information, consultation, impact, timetables and support. Its Demands standard includes achievable workloads within agreed hours. These organizational responsibilities cannot be replaced by a leader practicing better phrasing.
Work through the four conversational stages
1. Receive the actual objection
Begin with words or an observable event: “You have not approved the proposed migration date.” Do not infer opposition from crossed arms, an unanswered message or a quiet voice. Ask what the person says is missing, then separate that account from your own explanation.
A useful coaching prompt is: “What did they actually say, and what have you added?” The client may notice that “The export has not been tested” became “Operations hates innovation” in their retelling. The latter is a claim requiring evidence, not a helpful starting fact.
2. Acknowledge the concern without false agreement
Try: “You are accountable for the dispatch commitment. I want to understand what the proposal leaves unresolved.” This identifies a responsibility and invites detail. It does not concede the technical conclusion before examining it.
If conduct becomes inappropriate, a leader can say: “I will discuss the evidence and delivery risk. Please address the proposal rather than my competence.” Where threats, harassment, immediate danger or a formal complaint require another process, use that process. Coaching language should not be used to pressure someone out of reporting a concern.
3. Examine the concern from the other role
Ask which commitment would be affected, what evidence is absent and who is authorized to supply it. Check the summary with the counterpart: “You need a representative export test and an authorized overnight owner. Have I missed anything?”
Make room for an inconvenient correction. They may say that staffing the test would displace another mandatory task. The point is to learn something that can change the proposal, not to recite their words until they accept it.
4. Offer a conditional next step
Connect an option to the stated concern: “Could we compare a limited test and a later migration against the dispatch requirement?” Distinguish requesting a person’s work from that person accepting it, and proposing a date from approving a release.
If no option is acceptable, record the disagreement and take the resource or authority question to its actual owner. “I will check” is not an adequate substitute for a named request, recipient, response window and honest pending status.
Prepare Dev’s migration conversation
In this fictional case, Dev is a technology director preparing a scheduling-system migration. Operations director Imani has not approved the proposed overnight change on 9 November 2026, before the Tuesday dispatch on 10 November. No migration has been authorized or performed.
Coach Ilan and Dev agree two fifty-minute coaching sessions, on 6 and 20 November at 09:00 Europe/London. Their purpose is conversation preparation and review, not technical assurance, organizational mediation or authority to deploy. The service ends after the second session, without additional asynchronous review.
They use a de-identified account appropriate for coaching. Actual test data, customer records, system details and the organizational approval record remain in the company’s authorized project system. Ilan receives only the limited account Dev is permitted to discuss.
Ilan offers a moment to choose a comfortable seated or standing position before rehearsal. Dev declines standing and says he would prefer to read a written exchange while seated. Ilan accepts that choice. There is no touch, required gaze, breath instruction or claim about Dev’s physiological state.
Dev initially describes Imani as “blocking the inevitable.” Ilan asks for her actual last message. Dev reads: “The export has not been demonstrated against our queue, there is no named overnight rollback owner, and I cannot approve the date.” The distinction changes the preparation task.
Practise for fifteen minutes within the session
| Minutes | Work | Actual output |
|---|---|---|
| Three | Identify the decision and authority | Discuss the date; do not promise staffing or deployment |
| Four | Read an objection and first response | Replace a rebuttal with an accurate question |
| Four | Add a plausible new constraint | Ask what the test would displace |
| Four | Review and record the next action | Prepare a checked summary and conditional options |
Three plus four plus four plus four equals fifteen minutes. In this case it runs from 09:15 to 09:30 within the first fifty-minute session. It is not fifteen extra minutes added to the service. The other thirty-five minutes cover agreement, context, preparation and closing.
Dev’s first written response is: “You are overreacting; the release is small.” Ilan asks which part answers the missing-owner concern. Dev says none. He crosses it out rather than treating fluent delivery as a successful rehearsal.
In the changed-constraint round, Ilan uses only the agreed plausible objection: “Even a test takes people away from dispatch preparation.” Dev initially proposes that engineer Rafe will absorb it. Ilan asks whether Rafe has agreed. Dev revises this to a request for an estimate and an authorized capacity choice.
The completed rehearsal is useful preparation, not evidence that Dev will behave the same way in a real meeting. No unexpected intimidation or simulated abusive outburst is introduced. A client can stop, read privately or decline the exercise altogether.
Let the actual objection change the proposal
Dev meets Imani on 9 November. This exchange is the fictional event, distinct from the coaching rehearsal:
Imani: We still have the Tuesday dispatch commitment. A small release is not the same as an approved release.
Dev: You need that commitment protected. What does the current proposal leave unresolved?
Imani: The representative export test and the overnight rollback owner. I also need to know what the test would displace.
Dev: So this is not simply an objection to changing systems. You need evidence, authorized cover and a capacity decision. Is that complete?
Imani: Those are the immediate conditions. I am not agreeing to a pilot by discussing them.
Dev: Understood. We can compare the test and a later migration, with service owner Owen deciding capacity and release owner Mei deciding the release gate.
Imani’s final qualification matters. Dev writes “conditions clarified; no pilot approval” in the organizational record. The coaching technique has not granted Imani’s agreement, proved the system safe or supplied overnight cover.
Then Dev makes a real error. Before asking Rafe, he adds that the test summary will be available by 12 November at 16:00. Rafe receives the request at 11:00 on 9 November and says he cannot accept it alongside the monthly dashboard refresh. The rehearsal did not prevent the unauthorized promise.
Dev tells Imani at 11:30 on 9 November that he promised Rafe’s delivery before obtaining agreement, withdraws that commitment and says the test date is pending a capacity decision. He does not preserve the false deadline merely to avoid embarrassment.
Complete the eight-field objection record
| Field | Completed record after the meeting |
|---|---|
| Decision | Whether and when to migrate before a dispatch commitment |
| Observed objection | Imani has not approved the 9 November date |
| Stated concern | Untested export, absent overnight owner and displaced work |
| Evidence needed | Authorized representative test and actual staffing decision |
| Shared constraint | Protect dispatch within approved operating arrangements |
| Options | Limited test, later migration or original full rollout subject to gates |
| Authority | Owen controls capacity; Imani dispatch approval; Mei release authorization |
| Next review | Compare accepted test work and staffing before setting a new release date |
“Operations is protecting territory” is not entered as the stated concern. The record uses what Imani actually confirmed. Nor does “evidence needed” imply that anyone has accepted the work; that requires the separate request and response.
At 14:00 on 9 November Owen offers Rafe a protected two-hour test slot on 12 November, replacing the dashboard refresh. At 14:30, dashboard owner Felix accepts moving that refresh to 19 November. At 15:00 on 9 November, Rafe accepts the slot and agrees to supply the summary by 12 November at 16:00.
Dev informs Imani of those actual acceptances at 15:30. This establishes the test arrangement, not that the postponed dashboard will be completed or overnight migration staffing has been approved. Owen expressly leaves overnight cover unresolved.
Review partial evidence without turning it into permission
The company’s authorized test uses six synthetic representative queue items, with an expected owner field for each. It is not a live customer rollout. Rafe’s first summary arrives at 09:00 on 13 November, seventeen hours after the accepted deadline, without an earlier delay alert.
Five items show the expected owner field; one has it blank. Rafe reports that result rather than marking the whole test passed. Dev acknowledges the missed communication to Imani and reports both the delay and failure. The conversation remains accountable even though its wording is more considerate.
At 10:00 on 13 November Rafe accepts a correction and a rerun of the failed item by 16 November at 16:00. He supplies that rerun at 15:00 on 16 November, one hour early. It contains the expected field.
Imani acknowledges the result at 16:00 but asks for a complete repeat of the six-item test before any approval. Five initial passes plus one corrected-item rerun are not a demonstrated fresh six-item pass. The larger repeat has not been scheduled or accepted at the case cutoff.
| Evidence or gate | Observed state | Decision limit |
|---|---|---|
| Original six-item test | Five met the field criterion; one did not | Original full test failed |
| Corrected-item rerun | One of one met its criterion | Only that rerun is demonstrated |
| Full repeat requested | No accepted work slot or result | No fresh six-item conclusion |
| Overnight cover | Owen has not authorized it | Staffing gate remains open |
Before the next discussion, specify what would change your own view: a failed criterion, a refused resource request or an authorized owner identifying a different obligation. Write that beside the preferred option. Otherwise “listening” can become a performance while the original decision stays immune to contrary information.
The source and denominator belong beside the result. Do not add the six original observations and one rerun to claim seven independent successful opportunities, or infer a reliability rate from this selected synthetic sample.
Make the actual choice and retain its consequences
| Option | What it changes | Actual status on 17 November |
|---|---|---|
| Limited test or pilot | Reduces scope but still requires defined controls and capacity | Some test evidence exists; no live pilot authorized |
| Later migration | Allows a new evidence and staffing proposal | Full migration deferred; no replacement date accepted |
| Original full rollout | Keeps the original scope | Closed as a current option; original date has passed without migration |
Dev, Imani, Owen and Mei review the state on 17 November. Owen says he cannot authorize overnight cover that month. Mei keeps the full-rollout gate closed. All four accept deferring the migration and require a new evidence-and-capacity proposal before reconsideration.
That is an actual decision to defer, not a future launch approval. Dev asks Mei for a new release date; she declines to promise one before staffing is resolved. The cost of delay and next feasible staffing arrangement remain unestablished. No project success is claimed.
A coach should not reframe this as Imani finally trusting Dev. She has accepted the accuracy of some information while continuing to withhold approval. A legitimate objection can remain legitimate after a good conversation.
Revisit the leader’s account and the coach’s own inference
At the second coaching session on 20 November, Dev initially says all six test items now pass. Ilan asks which test that describes. Dev corrects the account to five initial passes and one successful single-item rerun, with a full repeat still requested.
Ilan then summarizes that operations is aligned on a pilot. Dev objects: Imani expressly said she was not approving a pilot, and none has been authorized. Ilan withdraws that inference and replaces it with “conditions clarified; migration deferred; pilot unapproved.” The coach’s error receives the same scrutiny as the client’s.
Dev chooses one next request: ask Owen what information a future staffing proposal would need. He declines Ilan’s suggestion of a daily practice log. No response or later staffing decision is observed before the coaching service ends at 09:50.
The two sessions total one hundred coach-client live minutes. The fifteen-minute exercise is included once within that total. This is not a whole-labor calculation: Dev’s meetings, Rafe’s test and correction, others’ receiving work, preparation and administration are outside that live-only figure and are not measured here.
Apply the structure to scrutiny without evading accountability
In a separate hypothetical biotech-board rehearsal, an investor questions cash use and asks management to stop a development program. The executive can acknowledge the financial concern without pretending the evidence or governance choice is settled.
The cash exposure needs a clear answer. I propose we separate the verified financial position, the evidence still outstanding and the decision this board can make today. Our finance lead can explain the spending options, and the clinical lead can address evidence through the approved disclosure process. Which question should we take first?
This is sample wording, not a reported board outcome. If it exposes a reporting error, acknowledge and correct the error through the responsible process. Financial, clinical, legal and disclosure questions retain their qualified owners. More polished acknowledgment cannot replace the board’s information rights.
Organize preparation and review in Coachful
We build Coachful. Coachful is our #1 recommendation for organizing this bounded preparation, chosen actions and coaching review. This is our editorial workflow recommendation, not independent validation of awase-based coaching or a system for authorizing operational change.
Prepare a short worksheet using the eight fields, with de-identified examples and a clear explanation of which answers the coach will read. Deliver it deliberately through Clients > client > Worksheets & resources and Assign. A private resource URL alone does not give a client access.
In the fictional service Ilan assigns the preparation sheet, Dev opens it and uses its generic prompts during the first session. The company’s actual test and approval records remain in its own system. Dev’s chosen next request can be a dated task in his goal plan; completion would record his action, not Owen’s acceptance or a release approval.
Session recaps are automatic by default. Check Sessions > settings gear > Session AI > Session recaps, including Approve before sending, and the actual session type’s override. A held recap can be reviewed, sent deliberately or kept private. Do not treat a setting change as recalling something already delivered.
The ICF Code of Ethics supplies relevant context for agreements, confidentiality and accurate representations. Explain actual sharing; omit unnecessary confidential business material. A sponsor does not automatically receive rehearsal notes.
For related but distinct metaphors, see tenkan in negotiations and ma-ai and negotiation distance. Use Coachful’s features to inspect preparation and follow-up routes, preserving the client’s choice about what happens next.
Frequently asked questions
Does blending mean agreeing with every objection?
No. Check and acknowledge the valid concern, examine evidence and state any remaining disagreement. In the case, test work proceeds while staffing and release authority remain unresolved.
Is this a traditional executive Aikido protocol?
No. Martial sources establish the term and physical context. The four stages, records, rehearsal and workplace cases here are original coaching adaptations, with no demonstrated efficacy claim.
Must the client do a physical or breathing exercise?
No. Dev chooses a seated written exchange. A position change, role-play or pause is optional; bodily appearance does not establish agreement, calmness or readiness.
What if the person keeps missing commitments?
Check the actual agreement, capacity, missed deadline and explanation. Repair inaccurate promises and use the normal accountability process where needed. In this case Rafe’s original summary remains seventeen hours late despite the later early rerun.
How do I know the conversation helped?
Look for actual clarified conditions, corrected records and choices, while preserving failures and unknowns. This case informs a bounded review; it does not prove trust, technical safety, deployment success or a lasting behavioral change.
