交渉・調整・危機対応Negotiation, Coordination, and Crisis Communication
Chapter Objectives
By the end of this chapter, you will be able to:
- Recognize domain register for scheduling conflicts, project risks, public problems, apologies, stakeholders, and contingency plans.
- Use conditional mitigation such as ～ば, ～たら, and ～なら to propose solutions carefully rather than issuing blunt demands.
- Frame responsibility for a problem without assigning blame in a way that damages a working relationship.
- Deliver and receive a formal apology using escalating degrees of formality appropriate to the severity of a problem.
- Read a short internal notice describing a scheduling conflict and identify the problem, the proposed adjustment, and the requested response.
- Write a coordination message that proposes an adjustment, names a condition, and requests confirmation.
- Listen to a short excerpt resembling a crisis-response call and identify the problem, the immediate action, and the follow-up commitment.
- Avoid common errors such as over-apologizing without proposing a solution, escalating before attempting de-escalation, and using conditional language so vague that no clear commitment is made.
Communication Scenario
佐藤部長 approved Emma's recommendation, and the company has begun a trial multilingual consulting project with a municipal office. Two weeks in, the municipal office's contact person calls to say that a promised translated document will not be ready by the agreed date, because the office's own internal review has taken longer than expected. Emma is asked to help coordinate a response: she must acknowledge the delay without either overpromising a new date the team cannot meet or sounding evasive about what went wrong. At the same time, 佐藤部長 wants Emma to propose a concrete adjustment — for example, delivering part of the document on time and the rest slightly later — rather than simply apologizing and hoping the client agrees to wait. Emma discovers that negotiation and crisis language in Japanese depends heavily on naming a condition clearly, proposing a specific next step, and calibrating the apology to match the seriousness of the problem, neither more nor less.
- The learner studies core vocabulary for scheduling conflicts, project risks, public problems, apologies, stakeholders, and contingency plans.
- The learner studies conditional mitigation, responsibility framing, apology and repair, and escalation/de-escalation language.
- The learner reads a model internal notice about the scheduling conflict.
- The learner listens to an excerpt resembling a crisis-response phone call.
- The learner writes a coordination message proposing an adjustment.
- The learner completes a performance task combining reading, listening, and coordination writing.
Core Vocabulary
This chapter's vocabulary supports scheduling conflicts, project risks, public problems, apologies, stakeholders, and contingency plans. All items are drawn from professional written and spoken registers and are intended for recognition and, where marked productive, for controlled production in coordination messages and spoken repair.
| Japanese | Reading | Meaning | Status |
|---|---|---|---|
| 遅延 | ちえん | delay (formal, used for schedules and deliveries) | Productive |
| 対応策 | たいおうさく | response measure, contingency plan | Productive |
| 見直す | みなおす | to reconsider, to review (a plan or schedule) | Productive |
| 責任 | せきにん | responsibility | Productive |
| お詫び | おわび | apology (formal register) | Productive |
| 申し訳ございません | もうしわけございません | I am truly sorry (highest common formal apology) | Productive |
| 代替案 | だいたいあん | alternative proposal | Productive |
| 段階的に | だんかいてきに | in stages, gradually | Productive |
| 確認を取る | かくにんをとる | to obtain confirmation | Productive |
| 関係者 | かんけいしゃ | the parties involved, those concerned | Productive |
| やむを得ず | やむをえず | unavoidably, having no other choice | Receptive |
| 事態を収拾する | じたいをしゅうしゅうする | to bring a situation under control | Receptive |
Items marked Receptive appear in the reading and listening materials below but are not required for independent production in this chapter's performance task. Note that リスク, メリット, デメリット, and other Chapter 8 professional vocabulary remain productive and may recur here in a coordination context.
れんしゅう — Practice: Sort the vocabulary above into three groups: (1) words used mainly to name a problem, (2) words used mainly to propose a solution, and (3) words used mainly to apologize or take responsibility. Note any item that could plausibly belong to more than one group.
Script and Typography Focus
This chapter's script focus is the typography of internal notices and timelines used to coordinate a response to a scheduling problem. Coordination notices typically separate the situation, the cause, the proposed adjustment, and the requested action into short, clearly labeled sections, often using bolded labels such as 現状 ("current situation"), 原因 ("cause"), and 対応策 ("response measure"), so that a reader under time pressure can locate each part quickly.
When reading a coordination notice, look first for a label such as 現状 or 問題点 to find the stated problem, then for 原因 to find the stated cause, and finally for 対応策 to find the proposed response. Do not assume the cause is stated first; some notices state the proposed response before explaining why it is necessary.
れんしゅう — Practice: Before reading the Model Coordination Notice below, scan it for labeled sections and note which order — problem, cause, response — the writer actually used.
Pronunciation Focus
A formal apology such as 誠に申し訳ございません is typically delivered more slowly than surrounding speech, with a lower, steadier pitch and a brief pause afterward, signaling sincerity rather than haste. A proposed solution that follows, such as 代替案をご提案させていただきます, is usually delivered at a more normal pace with a clearer rising energy, signaling a shift from acknowledging the problem to moving toward resolution. Practice saying both sentences aloud, exaggerating the contrast between the slower, lower apology and the more forward-moving proposal, then reduce the exaggeration to a natural level.
Grammar and Sentence Patterns
This chapter authorizes risk language, conditional mitigation, responsibility framing, apology and repair, escalation and de-escalation, and summaries of agreement, together with continued keigo appropriate to high-stakes coordination between internal colleagues and external stakeholders.
1. Proposing a solution with conditional mitigation
Purpose: to propose an adjustment carefully, so that the proposal reads as a considered option rather than an unconditional demand or a vague hope.
- ご都合がよろしければ、来週の水曜日までに残りの部分をお届けする形でいかがでしょうか。If it is convenient for you, how would it be if we delivered the remaining part by next Wednesday?よろしければ + いかがでしょうか (conditional + soft proposal)
- こちらで担当者を一名追加できれば、スケジュールの見直しは不要になると考えております。If we can add one more staff member on our side, I believe a review of the schedule will not be necessary.できれば + と考えております
2. Framing responsibility without assigning blame
Purpose: to explain what caused a problem and who is responsible for the response, without phrasing the explanation as an accusation that damages the relationship.
- 今回の遅延の責任は当社にあると認識しております。We recognize that the responsibility for this delay lies with our company.責任は～にあると認識しております (owning responsibility without excessive self-blame)
- 原因を確認したところ、双方の連絡不足も一因であったことが分かりました。Upon checking the cause, it became clear that insufficient communication on both sides was also a contributing factor.双方の～も一因 (shared responsibility framing, avoids one-sided blame)
3. Calibrating apology to the severity of the problem
Purpose: to match the strength of an apology to how serious the problem actually is, since an apology that is too strong or too weak for the situation can itself create friction.
| Severity | Formula | Notes |
|---|---|---|
| Minor inconvenience | ご迷惑をおかけしております | acknowledges ongoing minor disruption, no admission of major fault |
| Clear delay or error | ご迷惑をおかけし、申し訳ございません | standard formal apology for a concrete, acknowledged problem |
| Serious failure | 誠に申し訳ございませんでした | stronger, past-tense form; reserved for significant failures |
| After resolution | お手数をおかけしましたことをお詫び申し上げます | closes the matter formally once a resolution has been reached |
- 今回はスケジュールの調整でご迷惑をおかけしております。This time we are causing you inconvenience with the schedule adjustment.minor-inconvenience register, ongoing 迷惑
- 納期に間に合わなかったこと、誠に申し訳ございませんでした。I am truly sorry that we did not meet the deadline.serious-failure register, past tense でした
Chapter 8 taught that a professional recommendation should state its conclusion directly and early. In a coordination or crisis exchange, the first move is usually different: acknowledge the problem, propose a concrete adjustment, and confirm agreement, escalating to a more formal or higher-level response only if the first attempt does not resolve the matter. Opening with an escalated apology or a formal complaint before attempting a direct, cooperative fix can make a manageable scheduling problem feel like a larger conflict than it is.
Grammar Practice
- Write a sentence using ～ていただければ to propose delivering a project in two stages instead of all at once.
- Rewrite the sentence 御社の確認が遅かったので、遅れました。 using a responsibility-framing pattern that avoids directly blaming the other party.
- Choose the appropriate apology formula from the table above for (a) a five-minute delay to a scheduled call and (b) a missed contractual deadline that affected the client's own launch date.
- Identify which formula in the table above would be least appropriate to use before a solution has actually been proposed, and explain why.
Model Dialogue
Setting: Emma calls the municipal office's contact person, 山本様, to address the delayed translation document. Formal register, external stakeholder, continued keigo.
Emma notes two follow-up actions: prepare the priority section for delivery this week, and send written confirmation of the staged schedule by Friday.
ないようりかい — Comprehension check: What condition does 山本様 name for accepting the delay? What two follow-up actions does Emma commit to before ending the call?
Guided Practice
タスク１ — Frame identification. Take the Model Dialogue above and underline the apology sentence, the responsibility-framing sentence, the conditional proposal sentence, and the confirmation sentence, labeling each.
タスク２ — Formula assembly. Using the apology table and the conditional mitigation pattern above, write a four-sentence mini-exchange: one sentence acknowledging a problem, one framing responsibility, one proposing a conditional solution, and one confirming next steps.
タスク３ — Severity check. Rewrite one sentence from タスク２ using a stronger apology formula appropriate to a more serious version of the same problem, and compare it with your original.
Listening Practice
Ask your instructor, a partner, or a text-to-speech tool to read the following short passage aloud.
きくタスク — An excerpt from a crisis-response call
この度はご迷惑をおかけし、申し訳ございません。社内の確認作業に想定より時間がかかった結果、資料の一部が予定通りにお渡しできない状況になっております。つきましては、優先度の高い部分を明日中にお渡しし、残りを来週前半に段階的にお渡しするという対応策を提案させていただきます。この件につきましては、本日中に書面でも確認を取らせていただきたく存じます。
聞くタスク — Listening task: Listen at least twice. (1) What apology does the speaker use, and what does that suggest about the severity of the problem? (2) What cause does the speaker name? (3) What contingency plan does the speaker propose? (4) What follow-up action does the speaker commit to?
Speaking Practice
コントロールされた練習 — Controlled practice: Apology, cause, proposal, or confirmation?
- Given a short sentence, identify aloud whether it functions as an apology, a stated cause, a conditional proposal, or a confirmation of next steps.
- Given a mild problem and a serious problem, produce aloud the appropriately calibrated apology for each.
- Given a scheduling conflict, produce aloud a one-sentence conditional proposal using ～ていただければ.
コミュニケーションタスク — Handling a short coordination call aloud
Using the Model Dialogue as a model, role-play or deliver aloud a short spoken exchange addressing a scheduling problem of your choice, including an apology calibrated to the problem's severity, a responsibility-framing sentence, a conditional proposal, and a confirmation of next steps.
ひとりでもできる練習 — Solo practice: Reading the crisis-response excerpt aloud
Read the Listening Practice passage aloud, delivering the apology sentence with a slower, lower, steadier pitch, and the proposal sentence with a more forward-moving pace. Record yourself and check whether the contrast between the two is audible.
Reading Practice
Read the model internal coordination notice below, drawn from the notice Emma helps prepare for her team, and complete the questions that follow.
社内連絡（抜粋）— Model Coordination Notice (excerpt)
現状：多言語対応サービスの翻訳資料の一部について、当初の予定通りにお渡しできない見込みとなっている。原因：社内確認作業に想定より時間がかかったことが主な要因であり、担当部署との連絡にも一部行き違いがあったことが分かっている。対応策：優先度の高い部分を先に納品し、残りを段階的に納品する形で進める。関係者への確認は本日中に書面で取り、金曜日までに最終的なスケジュールを共有する予定である。
- Identify the sentence that states the current problem, and name the label it appears under.
- Identify the sentence that names the cause, and explain both factors it mentions.
- Identify the sentence that names the proposed response, and explain what makes it a staged rather than an all-at-once solution.
- Identify the sentence describing the follow-up action, and explain what will happen and by when.
Writing Workshop
Draft a short coordination message addressing a scheduling or project problem, applying the apology, responsibility-framing, conditional-proposal, and confirmation frames from this chapter.
- Choose a problem. Select a plausible scheduling conflict, project risk, or public problem that you can discuss, real or invented for practice.
- Open with a calibrated apology. Choose the formula from the apology table that matches the severity of your chosen problem.
- Name the cause using a responsibility-framing pattern that avoids directly blaming one party.
- Propose a conditional solution using ～ていただければ or an equivalent construction.
- Confirm the next step, stating what will happen and by when.
- Write a one-sentence note in Japanese explaining why you chose that particular apology formula for this problem.
チェックリスト — Revision checklist:
- The apology matches the actual severity of the problem, neither overstated nor understated.
- The cause is framed responsibly without assigning blame in a way that damages the relationship.
- A concrete conditional proposal is offered, not a vague hope that the problem will resolve itself.
- A specific next step and deadline are named.
- Register remains consistent with a formal, external-facing coordination message.
Culture and Communication
In many Japanese professional settings, an apology such as ご迷惑をおかけしております functions partly as a way of acknowledging the other party's inconvenience and maintaining the relationship, and not only as a strict legal admission that one side is entirely at fault. This is one reason a coordination message may open with an apology even when responsibility is genuinely shared between both parties. This practice varies by organization, industry, and the seriousness of the matter, and it should not be treated as a fixed rule for every workplace or every kind of problem.
How quickly a problem moves from a working-level contact to a more senior person varies considerably by organization and industry rather than by region. Some organizations expect a working-level attempt at resolution before any escalation; others expect earlier notification to a supervisor even for minor issues. Where regional variation does appear, it tends to affect the directness of spoken interaction rather than the formal escalation structure itself.
Common Mistakes to Avoid
Error: Repeating 申し訳ございません several times without ever stating a concrete proposed adjustment, leaving the other party without a clear picture of what happens next.
Correction: Apologize once at an appropriate severity, then move directly to a conditional proposal: 申し訳ございません。優先度の高い部分を先にお渡しできればと存じます。
Error: Opening a minor scheduling issue with a formal written complaint or an unusually strong apology such as 誠に申し訳ございませんでした before attempting a direct, cooperative fix.
Correction: Match the response to the actual severity, attempting a working-level conditional proposal first: 少し調整させていただければ、対応可能かと存じます。
Error: Using a conditional so open-ended that it commits to nothing, for example できればなんとかしたいと思います。
Correction: Name the specific condition and the specific outcome: 優先度の高い部分を今週中にお渡しできれば、全体の遅れは最小限に抑えられます。
Chapter Review
Section A — ごい (Vocabulary)
1. Complete the Core Vocabulary sorting practice above.
Section B — もじ (Script)
1. Complete the Script and Typography Focus scanning practice above.
Section C — ぶんぽう (Grammar)
1. Complete the Grammar Practice exercises above.
Section D — どっかいりかい (Reading comprehension)
1. Complete the Reading Practice questions above.
Section E — かくこと (Writing)
1. Complete all six steps of the Writing Workshop, as part of the Performance Task below.
Section F — はなすこと (Speaking)
1. Complete the spoken coordination exchange from Speaking Practice, as part of the Performance Task below.
Performance Task
パフォーマンスタスク — 第９章
問題を収拾する — Bringing a Problem Under Control
Complete all four parts below to demonstrate integrated control of apology calibration, responsibility framing, conditional mitigation, and continued keigo.
- Listening: Complete the Listening Practice task above and identify the apology, cause, contingency plan, and follow-up action.
- Reading: Answer the Reading Practice questions on the Model Coordination Notice.
- Spoken production: Deliver your recorded coordination exchange from Speaking Practice, using at least one calibrated apology and one conditional proposal correctly.
- Written production: Submit your coordination message and formula-choice note from the Writing Workshop, checked against the revision checklist above.
Assessment focus: correct calibration of apology severity; responsibility framing that avoids one-sided blame; a specific rather than vague conditional proposal; a named follow-up action and deadline; and the ability to explain, in Japanese, why a particular apology formula fit the situation.
Answer Key
Core Vocabulary — Sorting practice
Open-ended; representative grouping: (1) naming a problem — 遅延, 責任; (2) proposing a solution — 対応策, 見直す, 代替案, 段階的に; (3) apologizing or taking responsibility — お詫び, 申し訳ございません, 確認を取る, 関係者. Some items, such as 責任, plausibly belong to more than one group.
Script and Typography Focus
Open-ended scanning task; confirm against the Model Coordination Notice, which presents its labeled sections in the order 現状, 原因, then 対応策.
Grammar Practice
(1) Open-ended; model: プロジェクトを二段階に分けてお渡しできれば、全体の負担を軽減できます。 (2) Open-ended; model: 確認に時間がかかった結果、遅れるという状況になっております。 (3) (a) ご迷惑をおかけしております for the five-minute delay; (b) 誠に申し訳ございませんでした for the missed contractual deadline. (4) 誠に申し訳ございませんでした is generally least appropriate to use before any solution has been proposed, since opening with the strongest apology before offering a concrete next step can make the situation sound worse than a working-level proposal might resolve, and can read as an admission of major fault before the facts have been fully explained.
Model Dialogue — Comprehension Check
山本様 names the condition that receiving at least the most urgent part of the document within the week would be acceptable. Emma commits to (1) proceeding with the staged delivery as proposed, and (2) sending written confirmation of the schedule by Friday.
Listening Practice — Model answers
(1) The speaker uses ご迷惑をおかけし、申し訳ございません, suggesting a clear, acknowledged delay rather than a minor inconvenience or a major failure. (2) The named cause is that internal confirmation work took longer than expected. (3) The proposed contingency plan is to deliver the highest-priority part the next day and the remainder in stages early the following week. (4) The speaker commits to obtaining written confirmation of this plan by the end of the day.
Reading Practice
(1) The sentence beginning 現状： states that part of the translation materials will not be delivered as originally scheduled. (2) The sentence beginning 原因： names two factors: internal confirmation work taking longer than expected, and some miscommunication with the responsible department. (3) The sentence beginning 対応策： proposes delivering the higher-priority part first and the remainder in stages, rather than delivering everything at once. (4) The final sentence describes obtaining written confirmation from relevant parties within the day and sharing a final schedule by Friday.
Chapter Review — Sections A through D
Open-ended; check against the Core Vocabulary, Script and Typography Focus, Grammar Practice, and Reading Practice sections above.
Chapter Review — Sections E and F, and Performance Task
These are open-ended, integrated production tasks. Evaluate the written coordination message, formula-choice note, and recorded exchange against the assessment focus listed under the Performance Task above.
Looking Ahead
いまできること — What you can do now
You can calibrate an apology to the severity of a problem, frame responsibility without assigning blame, propose a conditional solution rather than an unconditional demand, and confirm a concrete next step, while continuing to adjust keigo and register between internal and external audiences. This foundation in negotiation and crisis communication carries forward into Chapter 10, where Unit II's advanced keigo, academic and professional discourse, and coordination systems come together in a cumulative assessment.