英語でチーム間の対立を誰も責めずに扱うには？C1上級：分裂文、倒置、改善措置の記録

チーム間の対立で最も役に立つ英語は、人ではなくプロセスに焦点を当てます。分裂文（cleft）がまさにその働きをします：“It was the private scope change that caused two days of rework.” 倒置（“Only after the missed training window did both teams see the gap”）は書面の記録に重みを加えます。会議は事実に沿って進め、担当者と期限を合意しましょう。このテーマはC1（上級）レベルで、チーム間の意見の対立に向き合う社会人の方に向いています。1日15分で十分です。

この記事が向いている人

振り返り会議や、2つのチームが問題を違う見方で捉えている会議を進めるチームリーダー、プロジェクトマネージャー、オペレーション担当者。
同僚の判断が問題を招いたことを、個人攻撃にせずに伝える必要がある方。
対立の後に記録を書き、双方にとって公平な内容にしたい方。
まだ早い場合：書面のフォローで根拠と意見を分けるのがまだ難しいなら、B2の、根拠を明確にした製品提案のフォローメールから始めましょう。
簡単すぎる場合：分裂文と倒置がすでに自然に使えるなら、提案書が試行の結果を誇張しないようにする限定の副詞に進みましょう。

サンプルページを開く

単語カード

Can I just make sure I've understood this correctly?

clarification frame. check your understanding

Can I just make sure I’ve understood this correctly? The scope changed in a private chat?

Would I be right in thinking …?

clarification frame. check an inference

Would I be right in thinking Service worked from the earlier plan?

Let's try not to get personal here.

fact-focus frame. stop personal criticism

Let’s try not to get personal here; both teams met their internal deadlines.

Can we try and stay focused on the facts?

fact-focus frame. redirect to evidence

Can we try and stay focused on the handover log?

会話

Maya When the scope changed in a private chat, my team continued using the old plan for two days.

Owen I was trying to resolve the issue quickly, but I can see that the effect was exclusion.

Maya What we need is one recorded decision and an accountable owner.

Owen I do agree. I’ll reopen the decision with both teams and publish the final scope by 15:00.

Maya I'll bring the Service view to the review and make sure disagreement is recorded as evidence, not disloyalty.

文の形

fronting

emphasis structure. move selected information to the beginning

The missing handover owner we need to fix first.

negative expression + inversion

fronting with inversion. invert auxiliary and subject after a negative opening

Rarely have the two teams reviewed a scope change together.

only + fronting and inversion

fronting with inversion. invert after an initial only phrase

Only after the missed training window did both teams see the gap.

participle fronting + inversion

fronting structure. front a participle phrase and invert be

Included in the revised process is a named handover owner.

it-cleft

cleft structure. focus a noun phrase or adverbial

It was the private scope change that caused two days of rework.

what-cleft

cleft structure. move focus to the end after a what clause

What we need is one recorded decision.

the person/place/reason/thing + relative clause

fixed emphasis frames. focus a selected person, place, reason or thing

The reason why Service missed training is that it received the earlier plan.

topic fronting without inversion

fronting structure. emphasize an object or complement

Personal labels I will remove; factual disagreement I will keep.

追加の練習

Analyse the evidence

Maya and Owen review the case documents at a desk.

A product team and service team share a launch deadline. Two product leads change the scope in a private chat, intending to save time. Service works from the earlier plan for two days and misses a training window. In the retrospective, product staff say service is resistant; service staff say product ignores operational knowledge. Delivery data shows both teams met their own deadlines but the cross-team handover had no named owner. The two teams now need to discuss the conflict openly, agree who owns each handover and repair the decision process.

Write the decision record

Subject: Repair actions after the launch-scope conflict

The retrospective confirmed that product leads changed the launch scope in a private chat. Service then worked from the earlier plan for two days and missed a training window. What caused the failure was not one team’s effort; it was the absence of a recorded cross-team decision and named handover owner. Both teams met their internal deadlines.

Owen acknowledged that he intended to save time but that the effect was exclusion. Maya explained that describing service as resistant undermined constructive conflict. We agreed to reopen the scope decision today. Owen will publish the final scope and rationale by 15:00. The launch manager will chair a thirty-minute review with both teams, and Maya will record the unresolved Service risks.

From now on, a scope change is valid only when Product and Service confirm it in the decision log. The launch manager herself will assign one owner to every cross-team handover. We will review missed updates, reopened decisions and psychological-safety feedback after four weeks.

Please add factual corrections by noon; personal labels will be removed from the final record.

Changed-constraint transfer

Maya Design approved a new checkout flow, but Support saw it only after customer testing began.

Owen The team met its test date, but the handover excluded the people who own customer questions.

Maya What we need is one recorded release decision and a Support readiness owner.

Owen I’ll reopen the decision and publish the final flow by 14:00; you’ll record unresolved support risks.

Create the action brief

A design team began testing a revised checkout flow with twenty customers. Support received the flow after testing started and has no approved answers for two new payment errors. Both teams met their internal dates, but the release decision has no named Support-readiness owner. Draft a record that removes personal labels, emphasizes the process failure, captures both teams’ feedback, assigns owners and makes release conditional on verified support answers.

Audit the repair record

stakeholders

identify who benefits and carries risk

Name affected groups before selecting the response.

evidence boundary

state what the current evidence cannot prove

Keep forecasts separate from observed outcomes.

fallback

define what happens if the plan fails

Assign a trigger and a recoverable alternative.

review

state when and how the next decision occurs

Name measures, owner and date.

この単元を学ぶ

どの方法で学びますか？

アカウントをお持ちですか？

無料アカウントで1つの単元をずっと開いておけます。

誰も責めずに対立を語る会話

スコープの変更が非公開のチャットで決まり、サービスチームは2日間、古い計画のまま作業していました。誰のせいかではなく、影響が言葉にされている点に注目してください。

聞いて答えてみましょう。マヤは何を求め、オーウェンは15時までに何を公開しますか？（記録された1つの決定と責任を持つ担当者、そして最終的なスコープです。）

Maya When the scope changed in a private chat, my team continued using the old plan for two days.

Owen I was trying to resolve the issue quickly, but I can see that the effect was exclusion.

Maya What we need is one recorded decision and an accountable owner.

Owen I do agree. I’ll reopen the decision with both teams and publish the final scope by 15:00.

Maya I'll bring the Service view to the review and make sure disagreement is recorded as evidence, not disloyalty.

分裂文：人ではなくプロセスに焦点を当てる

分裂文は1つの文を2つに分け、1つの要素を際立たせます。it-cleftは原因を特定し、what-cleftは要点を、英語で主な強勢が置かれる文末に回します。日本語の「必要なのは、記録された1つの決定です」という「〜のは〜だ」の形はwhat-cleftとほぼ同じ構造なので、そのまま活用できます。“It was the private scope change that left Service on the old plan”は直せる出来事を、“Owen changed the scope”は人を指しています。強調のdo（“I do agree”）は、約束の前に本当に同意していることを示します。

“It was the private scope change that caused two days of rework.”：2日分の手戻りを生んだのは、非公開でのスコープ変更でした。
“What caused the failure was not one team’s effort; it was the absence of a named handover owner.”：失敗の原因は一方のチームの努力ではなく、引き継ぎの担当者がいなかったことでした。

重みを加える倒置と前置

rarely、not once、only afterのような否定や限定の表現で文を始めると、助動詞が主語の前に来ます。助動詞がなければdoやdidを補います。“only after”や“only when”では、時を表す節ではなく主節を倒置します。日本語には助動詞と主語の順序を入れ替える規則がないため、この手順は抜けやすいポイントです。記録では1回の倒置が重みを加えますが、会議で何度も使うと暗記した台詞のように聞こえます。

“Rarely have the two teams reviewed a scope change together.”：2つのチームがスコープ変更を一緒に見直したことはめったにありません。
“Only after the missed training window did both teams see the gap.”：研修の機会を逃して初めて、両チームは抜けに気づきました。
“Included in the revised process is a named handover owner.”：分詞の前置
“Personal labels I will remove; factual disagreement I will keep.”：目的語の前置、倒置なし

緊迫した会議を事実に沿って進める表現

反論する前に確認し、“resistant”（非協力的な）のようなレッテルを避け、意見の違いを条件に変えましょう。

確認する：“Can I just make sure I’ve understood this correctly? The scope changed in a private chat?”
推論を確かめる：“Would I be right in thinking Service worked from the earlier plan?”
事実に戻す：“Let’s try not to get personal here; both teams met their internal deadlines.”
反対する：“I see what you mean, but speed did not justify excluding Service.”
歩み寄る：“I’m prepared to keep the deadline if both teams confirm the scope.”

自分に合った方法でこの単元を学ぶ

6つの要素で書く改善措置の記録

外部の人でもそのまま実行できるよう、170〜200語で書きます。新しいケース：サポートチームは顧客テストが始まってから新しい決済フローを知り、2つの新しい決済エラーについて承認済みの回答がありません。

事実：“Customer testing began before Support received the flow.”
原因：“What caused the gap was a release decision with no Support-readiness owner.”
双方の見方：“Design met its test date; Support cannot yet answer two payment errors.”
担当者：“Design will publish the final flow by 14:00.”
条件：“Only when Support has approved answers will the flow be released.”
ルールと見直し：“From now on, both teams confirm release decisions in the log; we will review it on Friday.”

よくある間違い

強調を不自然にしたり、事実を非難に変えてしまったりする間違いです。

“Only after the review we saw the gap.” 倒置します：“did we see”。
“What we need it is one decision.” “it”は不要です。
“It was the private change caused the rework.” “that”を残します。
“The reason is because …” 改まった文章では“The reason is that …”を使います。
“Service is resistant.” 行動を説明します：“Service worked from the plan it received.”

1日15分の練習

職場で実際にあった意見の対立か、上の決済フローのケースで練習しましょう。

3分：“They never tell us anything”のような不満を、it-cleftとwhat-cleftで書き換えます。
3分：RarelyとOnly afterで始まる文を、焦点の語に強勢を置いて言います。
7分：改善措置の記録を書きます。
2分：声に出して議論します。意見の対立がまったくないチームは健全でしょうか？“What matters most is …”を使ってみましょう。

次のステップ

次は、quite、only、not absolutelyのような限定の副詞です。提案書が試行の結果を誇張しないようにしてくれます。

よくある質問

英語の分裂文（cleft sentence）とは何ですか？

1つの要素を際立たせるために2つに分けた文です。it-cleftは原因を強調し（“It was the private change that caused the rework”）、what-cleftは要点を文末に回します（“What we need is one decision”）。

英語でonlyやrarelyの後に倒置するのはどんなときですか？

否定や限定の表現が文頭に来るときです：“Rarely have we …”、“Only after the review did we …”。日常会話より書面の記録に向いています。

職場で個人攻撃に聞こえないように英語で反対するには？

まず相手の要点を認め、それから根拠を示します：“I see what you mean, but the handover had no owner.” 人柄ではなく行動について話しましょう。