Awase in Executive Coaching: Responding to Criticism

Awase in executive coaching can be used as an optional metaphor for understanding criticism before choosing a response. A leader can acknowledge a missed commitment, examine a disputed explanation and refuse an irresponsible guarantee. The useful result is a clearer working task, rather than automatic agreement.

Awase comes from Aikido language concerning linking or blending. This guide's workplace adaptation is ordinary conversation preparation, not martial instruction or a clinically validated method for changing another person's nervous system. It requires neither contact nor body-focused practice.

The original case follows an executive who chooses written rehearsal, addresses a shareholder concern and then sends a late, inaccurate report. The correction matters as much as the conversation: a well-delivered answer cannot compensate for inventing another person's agreement.

Keep the martial origin and workplace adaptation distinct

In his published excerpt from Dueling with O-sensei, Ellis Amdur links awase with linking or blending and challenges a romantic interpretation in which contact automatically establishes peace. That is one practitioner's account, rather than proof of a universal leadership technique.

Aikikai describes Aikido in its official overview as a martial art with partner practice and an emphasis on moving beyond a collision of strength. Its account concerns its training tradition. It does not establish that a coaching phrase controls colleagues or that a physical exercise is appropriate for a workplace client.

The adaptation here asks: what is valid in this concern, what requires investigation, and what can I responsibly offer? A client may prefer those ordinary words and decline the martial metaphor altogether. The task remains available.

Do not cast shareholders, colleagues or customers as opponents whose energy must be redirected. They can have legitimate interests and information the executive lacks. A metaphor that encourages covert control has stopped serving accurate communication.

Distinguish understanding from surrender

Acknowledging a missed date does not establish every allegation about its cause. Understanding why a shareholder wants certainty does not make a forecast certain. The leader should name those distinctions rather than hope a warm tone communicates them.

For a client who routinely appeases others, praise an accurate refusal when appropriate. Calling every concession harmony can reinforce the difficulty. Ask what the person wants to preserve, what they can decide and what they are no longer willing to promise.

Offer preparation that the client can decline

Ask what would help the client think. They might want a quiet pause, comfortable seating, the written question or a review of the decision criteria. Do not insist that the person describe sensations, change posture or use controlled breathing to demonstrate readiness.

A conversation-only alternative should be usable immediately. Read the concern, underline its factual part and identify the next question. No physical contact, balance challenge, pushing, pulling, surprise approach, forced eye contact or simulated attack is needed.

The NHS guidance on change and uncertainty includes choosing useful strategies, comfortable pacing and support when needed. That general advice does not validate Awase or promise a physiological reset. Persistent health concerns call for appropriate professional support.

If someone is distressed, exhausted or unable to continue usefully, offer a genuine pause, another format or rescheduling. Do not treat tears, silence or discomfort as proof of a breakthrough. Stay within competence and discuss suitable support when coaching is insufficient.

Case: a missed launch and a demand for certainty

This fictional account concerns Eren, a chief executive; Quin, the independent coach; Noor, a shareholder; and Seth, the board chair. The measured coordination runs from 20 March to 7 April 2057. A promised 15 March launch has already been missed.

Existing governance establishes Seth's chairing role and the audience for the selected project account. Eren may share that operational material with Noor and Seth, while private coaching conversations remain outside it. Earlier project work, source creation, governance and the original launch failure are outside the measured period, not free work.

All four accept the bounded work budgets listed later before the activities begin. The current project estimate has forty engineering hours remaining and twenty-eight authorized hours available in the next planning week. The twelve-hour gap has no approved reallocation or overtime. These are future project estimates, separate from the coordination minutes in this guide.

On 20 March, Eren spends twenty-five minutes selecting the current source facts and preparing for coaching. Quin spends twenty minutes reviewing the agreed context and preparing the session. Both attend a forty-five-minute private session on 21 March; Quin then spends ten minutes on notes.

A real choice within the coaching rehearsal

Quin offers an ordinary pause or written preparation. Eren declines posture and breath-focused practice and chooses the written facts. The following complete selected exchange occurs within their session:

Quin: Would a quiet pause help, or would you rather work from the written question?
Eren: The written question. I do not want to work on my posture or breathing.
Quin: We can do that. What concern can you acknowledge without accepting an unsupported explanation?
Eren: We missed the launch. I hear every criticism as a claim that I am incompetent.
Quin: Is that what Noor has actually said, or your interpretation of the concern?
Eren: It is my interpretation. Noor asked what management will do about the delay.
Quin: What would an accurate answer preserve?
Eren: The missed date, the unallocated work and a refusal to guarantee what we cannot yet schedule.

The coach does not diagnose Eren or Noor. Eren can retain the uncomfortable feeling while checking what was actually communicated. Written rehearsal addresses a response, not the engineering work itself.

Obtain the receiving work before assigning it

Eren spends fifteen minutes on 22 March preparing and sending Noor and Seth an invitation and selected project facts. It requests a twenty-minute discussion on 24 March, fifteen minutes each for reading and acceptance on 23 March, a ten-minute report review and reply on 27 March, and up to five minutes each for a correction read and reply on 29 March if needed.

The invitation promises an accurate report by 25 March at 17:00. The stated review route and budgets concern this finite exchange; they do not create an unlimited obligation to respond. Both recipients spend fifteen minutes on 23 March reading the material and accepting those specific slots in replies.

Eren spends ten minutes on 24 March reading both acceptances before the meeting. Quin does not attend the board discussion or receive its private conversations. A coach's preparation does not authorize them to observe or report on a separate meeting.

Meet the substance of the criticism

Eren, Noor and Seth meet for the agreed twenty minutes on 24 March. Eren records the selected decisions during that discussion. Their discussion includes this complete selected exchange:

Noor: We were promised a launch on 15 March. The delay makes me question whether management has control of the project.
Eren: We missed that commitment. I also failed to give a clear warning before it passed. Those responsibilities need an answer.
Noor: Then give me a date that I can rely on.
Eren: Forty engineering hours remain, with twenty-eight authorized next week. I cannot guarantee completion while twelve hours and the dependencies are unresolved.
Noor: I am asking for a supported forecast, not permission to ignore the delay.
Eren: That distinction matters. I can give you the current assumptions and what must be decided. I cannot turn them into an approved plan by calling them one.
Seth: Keep the report clear about who can authorize additional capacity. This discussion does not approve overtime or a new launch date.
Noor: I will review that report. Reviewing it is not agreement with the plan.

Noor's concern remains legitimate. Eren accepts responsibility for the missed warning while resisting a broader inference that has not been established. Seth preserves the authority boundary. None of those moves secures the missing engineering hours.

The gap is twelve of forty required hours, or 30% of the estimated work. Relative to the twenty-eight available hours, it is about 42.9%. State which denominator is being used. A communication exercise cannot make either comparison disappear.

A later error defeats the first reporting goal

Eren does not send the promised accurate report on 25 March. Instead, Eren works from 17:40 to 18:00 on 26 March reading the meeting record, composing and sending V1 to Noor and Seth. That twenty-minute block is mixed reading and writing. The report is twenty-five hours late.

Worse, V1 says Noor agreed to the twenty-eight-hour plan and treats the discussion as approval of a new launch commitment. Those statements contradict the actual exchange. A calmer conversation has not prevented an inaccurate record.

Noor spends ten minutes on 27 March reading V1 and returning a correction: Noor agreed to review the report, not approve a plan or date. Seth uses ten minutes reading V1 and sending a separate correction that no additional capacity or launch commitment was approved. Both retain the valid concern about management follow-through.

Eren spends twenty minutes on 28 March reading both corrections, repairing the report and sending V2 to Noor and Seth. Within that same block, Eren also sends Quin a selected learning account through their existing individual coaching conversation, excluding unrelated board material.

V1 was late and incorrectly attributed approval to Noor and the meeting. I apologize for both errors. The 15 March launch was missed, and my earlier warning was inadequate. The current estimate is forty engineering hours, with twenty-eight authorized next week and twelve still without approved allocation. Noor agreed to review the report, not approve a plan or launch date. Seth did not authorize additional capacity. No replacement launch commitment is approved by this account. The next planning decision needs the proper authority and current evidence. This correction records the position; it does not complete the remaining project work.

The apology does not erase the missed reporting promise or require Noor to feel satisfied. The corrected account also avoids claiming that twenty-eight hours can complete forty hours of work.

Complete the return and retain the mixed result

Noor and Seth each use five minutes on 29 March reading V2 and replying to Eren. Noor confirms that the record now represents the limited agreement but says the late report and false attribution still damage confidence. Seth accepts V2 as the corrected account, without approving a new launch date or capacity.

Quin uses ten minutes that day reading Eren's selected learning message and sending a coaching comment. It asks Eren to compare the accurate boundary held during the meeting with the later reporting error. This is an actual delivered comment in their private conversation, rather than an internal review assumed to reach the client.

Eren spends ten minutes on 30 March: five reading and recording Noor's and Seth's existing replies, and five reading Quin's comment. There is no new acknowledgment or uncounted recipient meeting.

Eren uses ten minutes on 6 April preparing for the learning review. Eren and Quin meet for twenty minutes on 7 April; Quin then spends five minutes on notes. They examine the original reporting failure, the repair and Eren's temptation to translate a difficult discussion into reassuring approval.

The result is a corrected, received account and a more precise learning question. The initial launch and reporting targets remain missed. Project completion, additional engineering work, a new launch authorization and restored confidence have not been established.

Count all coordination, including receiving work

The total is 405 active person-minutes against 490 accepted minutes, leaving eighty-five within those budgets. Live work contributes 190 already included: ninety for the private session, sixty for the three-person board discussion and forty for the learning review. Other preparation and handling contribute 215.

These figures do not include earlier project work or future engineering and governance decisions. They are not a productivity saving, physiological measure or whole-business cost. The client's chosen written route is a legitimate option without an invented bodily outcome.

Rehearse a boundary, not an opponent's compliance

Choose a manageable version of the criticism and agree how the client can stop or change the rehearsal. Do not intensify an attack to test resilience. Try a response that acknowledges the valid concern, identifies uncertainty and names an action within authority.

Then rehearse a less cooperative return. The other person may repeat the request, reject the forecast or object to the proposed process. The client can restate a limit, ask the chair to clarify authority or end the exchange when appropriate. Success does not require controlling that person's feelings.

If the delivery includes insults or threats, a separate boundary and organizational response may be needed. Acas describes unwanted bullying conduct and employer responsibilities. A coaching exercise does not replace those responsibilities, establish a legal classification or guarantee protection.

Prepare a realistic route back to the issue: discussion of the missed commitment can continue with an appropriate chair or process, while unacceptable conduct is addressed. Consider power and consequences before prescribing a confrontation to someone with limited authority.

Prepare a boundary with a workable next route

A boundary should identify what the person will discuss, what must change and what they can actually do if the conduct continues. It should not imply authority the client lacks. A chair, employee and external supplier may need different routes even when each has a valid concern.

Here is an original rehearsal statement for someone who can pause the meeting:

I will discuss the missed commitment and the evidence about its causes. I am not willing to continue while personal insults replace that discussion. If they continue, I will pause this meeting and ask the chair to agree a suitable next route. Pausing does not settle the project issue or remove my responsibility to answer it. We can return to the facts, required decisions and reporting arrangements when the discussion can proceed appropriately.

This is a proposed practice example, not an instruction to confront someone regardless of risk. Adapt it to the client's actual authority and available support. If a direct statement would expose them to retaliation or danger, explore a safer process rather than grade them on delivery.

Review the conversation through six distinct questions

After an exchange, separate what was said from what the client hoped would happen. An immediate agreement can conceal an unauthorized promise; continued disagreement can coexist with an accurate answer. These six original questions support a short written review:

1. Accuracy: Which factual concern did I acknowledge, and what needs correction?
2. Understanding: What did the other person actually confirm or challenge?
3. Authority: Did I make a decision I could make, or borrow someone else's approval?
4. Boundary: What limit did I state, and what happened when it was tested?
5. Commitment: What specific action and date now require follow-through?
6. Uncertainty: What relationship, delivery or safety concern remains unresolved?

Choose a single issue for the next rehearsal rather than repeat the whole conversation with a more polished tone. For example, practice answering a repeated request for certainty, correcting an attribution or admitting a missed responsibility. Keep the actual commitment in an operating record so reflection does not replace doing the work.

Review accuracy and follow-through in the workspace

Coachful is our #1 recommendation for organizing the preparation, chosen response and learning account described here. This is an editorial recommendation without a market-ranking study or promise of conflict resolution. Compare the features with the actual workflow.

A selected worksheet can support the client's preparation. Coach review on a submitted worksheet is private internal handling; if the coach promises feedback, send the intended comment through the agreed route and include the client's reading time. Eren's actual comment route is the existing individual conversation.

A task or habit activity count describes recorded practice, rather than proving that a response was accurate or another person felt understood. The demonstration images are illustrative. They do not show Eren's records or establish a change in stress, confidence or hormones.

Use active listening to check the actual concern and a clear session wrap-up to identify what remains to be done. Keep the client's selected material and private coaching audience distinct from an operational report.

Frequently asked questions

Does Awase mean agreeing with criticism?

No. The adaptation concerns accurate contact with the issue before choosing a response. Evidence and authority still constrain what can be promised.

Does the client need somatic exercises?

No. Written or conversation-only preparation can be used. Any offered attention or movement option should be comfortable, voluntary and within competence.

Can it calm a hostile person?

No reliable guarantee is established here. The other person retains their reactions, and serious misconduct needs appropriate protective processes.

Does a confident response prove good leadership?

No. Check the content, authority, actual record and later follow-through. Eren's composed meeting response was followed by a late, inaccurate report.

What would count as useful progress?

A clearer concern, an accurate decision, a maintained boundary and fulfilled commitments can be useful. Keep refusals, missed promises and unresolved relationship concerns visible.