Resolving a Small Disagreement at Work | Learn Japanese in English

Japanese lesson set in a contemporary Tokyo everyday setting: At work, two teammates compare assumptions, check project notes, and agree on a focused compromise for a client task..

EN → JA / Level: B1

About This Lesson

Use Resolving a Small Disagreement at Work to practice Japanese conversation, pronunciation, vocabulary, grammar, and quizzes.

Dialogue

A

違う前提で考えたので、意見が合わないのだと思います。

chi-GAH-oo zen-TEH deh kan-GAH-eh-tah noh-deh, ee-KEN gah ah-wah-NAH-ee noh-dah toh oh-MOH-ee-mahs. I think we disagree because we made different assumptions.
B

クライアントは、まず簡単なバージョンを求めていると思っていました。

koo-RAI-ahnt wah, mah-zoo KAHN-tahn nah BAH-john oh moh-toh-MEH-teh ee-roo toh oh-MOH-tteh ee-mah-shee-tah. I thought the client wanted a simple version first.
A

クライアントは、すべての機能が入った完成版を期待していると思っていました。

koo-RAI-ahnt wah, sah-beh-teh noh KEE-noh gah hah-ee-tah kahn-SAY-ban oh tai-KEH-shee-teh ee-roo toh oh-MOH-tteh ee-mah-shee-tah. I thought they expected a complete version with every feature.
B

記憶だけで言い合うのではなく、メモを確認しましょう。

kee-OH-koo dah-keh deh ee-ee-AH-oo noh deh-wah nah-koo, MEH-moh oh kah-koo-NIN shee-mah-SHOH. Let's check the notes instead of arguing from memory.
A

メモには、速さが最も大切ですが、高度な機能が一つはまだ必要だと書いてあります。

MEH-moh nee-wah, hah-yah-SAH gah moh-ttoh-MOH tie-SETS deh-soo gah, koh-DOH nah KEE-noh gah ee-TOH-tsoo wah mah-DAH nee-SHOH dah toh KAH-ee-teh ah-ree-MAHS. The notes say speed matters most, but one advanced feature is still required.
B

その機能を含む、より簡単なバージョンが、ちょうどよい妥協案だと思います。

soh-noh KEE-noh oh foo-KOOM, yoh-ree KAHN-tahn nah BAH-john gah, CHOH-doh yoh-ee dah-KYOH-ahhn dah toh oh-MOH-ee-mahs. A simpler version that includes that feature sounds like the right compromise.
A

そのトレードオフを明確に説明できるなら、受け入れられます。

soh-noh toh-RAY-doh-oh-foo oh may-KAH-koo nee sets-MAY deh-KEH-roo nah-rah, oo-KEH-ee-reh-rah-reh-MAHS. I can accept that if we explain the trade-off clearly.
B

クライアントの優先事項を中心に説明できます。

koo-RAI-ahnt noh yoo-SEN jih-KOH oh CHOO-shin nee sets-MAY deh-KEH-mahs. We can frame it around the client's priorities.
A

決定に合わせて、タスクの説明を更新します。

keh-tsu-DAI nee ah-wah-SEH-teh, TAH-soo-koo noh sets-MAY oh koh-SHIN shee-MAHS. I'll update the task description to match the decision.
B

それなら、その意見の違いでプロジェクトが遅れることはないはずです。

soh-reh-NAH-rah, soh-noh ee-KEN noh chee-GAH-ee deh puh-roh-JEH-koo-toh gah oh-koo-REH-roo koh-toh wah nah-ee hah-zoo deh-soo. Then the disagreement should not slow the project down.

Word by Word

違う 違う means different here and describes 前提 as differing. It is used before a noun in 違う前提. In a work discussion, use it to identify that two people started from different conditions or ideas.
前提 前提 means assumption or premise here: the basis on which the speakers thought about the task. In 違う前提で考えた, it is followed by で to show the basis for thinking. This is useful when explaining why people reached different conclusions.
で で marks the basis or circumstances for the action in 違う前提で考えた. The pattern noun + で + action shows what basis someone used. Here it explains that the different assumptions led to the disagreement.
考えた 考えた means thought or considered in the past, referring to how the speakers approached the task. It is the past form of 考える. The pattern 前提で考えた is useful when describing how someone made a judgment.
ので ので means because or since and gives the reason in 違う前提で考えたので. It connects a reason to the result that follows. In a workplace conversation, use clause + ので when explaining why a problem occurred.
意見 意見 means opinion here, specifically the speakers’ views about the task. In 意見が合わない, it is the thing that does not match. This word is useful when comparing or resolving different views at work.
が が marks 意見 as the subject of 合わない in 意見が合わない. The pattern noun + が + predicate identifies what has the stated condition. Here it shows that the opinions, rather than the people directly, do not match.
合わない 合わない means do not agree or do not match in 意見が合わない. It is the negative form of 合う. Use 意見が合わない when describing a disagreement between people’s views.
の の turns the preceding statement 意見が合わない into an explanatory unit before だ in 意見が合わないのだ. The pattern clause + のだ presents the situation as an explanation or conclusion. Here it explains the reason the speakers disagree.
だ だ is the plain copula in the explanatory expression 意見が合わないのだ. It gives the preceding explanation an assertive ending before と 思います. This form is useful when presenting something as the underlying reason or fact.
と と marks the content of the thought in 意見が合わないのだと思います. The pattern clause + と + 思います reports what someone thinks. Here it marks the speaker’s conclusion about the disagreement.
思います 思います means think and expresses the speaker’s current view in 意見が合わないのだと思います. It is the polite form of 思う. Use the pattern 〜と思います when giving an opinion or tentative conclusion.
クライアント クライアント means client, the customer whose needs guide the task. It appears as the topic in クライアントは. In a project discussion, use it when referring to the customer’s request or expectations.
は は marks クライアント as the topic in クライアントは. It tells the listener that the following information concerns the client. This pattern is useful when introducing or contrasting a person’s request or expectation.
まず まず means first or to begin with and places the simple version at the first stage in まず簡単なバージョン. It helps organize actions or priorities in sequence. Use it when proposing what should happen before later steps.
簡単 簡単 means simple here, describing the version as limited or not complex. In 簡単なバージョン, it connects to the noun through な. This is useful when discussing a first or smaller version of a product.
な な links 簡単 to バージョン in 簡単なバージョン. It is used here because 簡単 describes the following noun. The pattern adjective + な + noun is useful for describing the type or quality of something.
バージョン バージョン means version, referring to a form of the product or task deliverable. It appears in 簡単なバージョン and より簡単なバージョン. In project work, use it to distinguish different levels or releases of the same product.
を を marks バージョン as the object of 求めている in バージョンを求めている. The pattern noun + を + verb identifies what someone wants or seeks. Here it shows which version the client wants.
求めている 求めている means wants or is seeking in クライアントは、まず簡単なバージョンを求めている. It is based on 求める and presents the client’s ongoing requirement or request. Use the pattern Xを求めている to describe what a person or organization is seeking.
思っていました 思っていました means thought or had been thinking, describing an earlier belief about the client’s request. It is based on 思う and presents that belief politely in the past. Use 〜と思っていました when explaining an assumption that existed before the current discussion.
すべて すべて means all or every in すべての機能. It gives the following noun complete scope. Use the pattern すべての + noun when referring to every item in a group.
機能 機能 means feature or function here, referring to the product capabilities. In すべての機能が入った完成版, it is the item included in the complete version. This word is useful when discussing which capabilities a product should contain.
入った 入った means included or contained in すべての機能が入った完成版. It is the past form of 入る and describes a version that has the features inside it. Use the pattern nounが入った + noun when describing something that contains a particular item.
完成版 完成版 means complete version, referring to a deliverable with all the features included. It appears in 完成版を期待している. In project planning, use it to distinguish the finished product from a simpler initial version.
期待している 期待している means expects or is expecting in クライアントは、すべての機能が入った完成版を期待している. It is based on 期待する and describes the client’s expectation. Use the pattern Xを期待している when stating what result someone expects.
記憶 記憶 means memory in 記憶だけで言い合う. It refers to what the teammates remember rather than what is documented. This word is useful when distinguishing personal recollection from written information.
だけ だけ means only or just and limits the basis to 記憶 in 記憶だけで. The pattern noun + だけ means only that noun or source. Here it emphasizes that relying only on memory is not a good way to settle the disagreement.
言い合う 言い合う means argue with each other in 記憶だけで言い合う. It describes a back-and-forth exchange between the teammates. Use it when people are disputing a point with one another instead of checking evidence.
なく なく connects the negative idea in 言い合うのではなく to the alternative action メモを確認しましょう. In this construction, it means instead of doing the preceding action. The pattern 〜のではなく、... is useful for replacing one approach with another.
メモ メモ means notes, referring to the written project information. In メモを確認しましょう, it is the thing the teammates will check. Use it when directing attention to brief written records.
確認しましょう 確認しましょう means let’s check or let’s confirm in メモを確認しましょう. It is the polite volitional form of 確認する and invites the other person to act together. Use it when proposing a joint check of information.
に に marks the location or source of the written information in メモには. Together with は, it presents the notes as the topic containing the stated information. This use is helpful when reporting what is written in a document or record.
速さ 速さ means speed and is the quality identified as most important in 速さが最も大切. It is marked by が as the subject of 大切. In project planning, use it when discussing how quickly something should be completed or delivered.
最も 最も means most and modifies 大切 in 速さが最も大切. It marks the highest degree among the priorities being considered. Use the pattern 最も + adjective when identifying the strongest or highest priority.
大切 大切 means important in 速さが最も大切ですが. It states the value assigned to speed before the contrast introduced by が. This word is useful when identifying which requirement matters most.
です です gives 大切 a polite predicate ending in 大切ですが. The following が connects this polite statement to a contrasting point. This form is useful when stating one fact politely before adding an exception or different requirement.
高度 高度 means advanced or sophisticated in 高度な機能. It describes the feature as technically advanced. Use the pattern 高度な + noun when identifying a more sophisticated capability or requirement.
まだ まだ means still or yet in 一つはまだ必要. It shows that the advanced feature remains necessary even though speed is the main priority. Use it when a requirement continues to apply at the current point.
必要 必要 means necessary or required in 高度な機能が一つはまだ必要. It states that at least one advanced feature must remain. Use the pattern nounが必要 when describing a requirement.
書いてあります 書いてあります means is written or says in the notes in メモには、...と書いてあります. It is the polite form of 書いてある and describes written information that remains available. Use the pattern 〜と書いてあります when reporting the content of a document.
その その means that or the mentioned and points back to the advanced feature in その機能. It comes directly before the noun it identifies. Use その + noun when referring to something already mentioned in the conversation.
含む 含む means include or contain in その機能を含む、より簡単なバージョン. It describes the simpler version as containing the mentioned feature. Use the pattern nounを含む + noun when specifying what a thing includes.
より より marks a comparative meaning in より簡単なバージョン, meaning a more simple version relative to another option. It comes before the describing word. Use より + adjective when comparing alternatives.
ちょうど ちょうど means just or exactly in ちょうどよい妥協案. It strengthens よい and presents the compromise as fitting the situation particularly well. Use ちょうどよい + noun when something is suitably right for a need.
よい よい means good or right in ちょうどよい妥協案. Together with ちょうど, it describes the compromise as appropriately suitable. This expression is useful when evaluating whether a proposed option fits the situation.
妥協案 妥協案 means compromise proposal, the proposed solution that keeps the required feature while simplifying the version. It appears in ちょうどよい妥協案. Use it when two sides accept a middle solution between different preferences.
トレードオフ トレードオフ means trade-off, referring to the balance between speed and including an advanced feature. It is the object of 説明 in そのトレードオフを明確に説明. In project discussions, use it when one benefit requires accepting a limitation elsewhere.
明確 明確 means clear or explicit and appears in the adverbial form 明確に説明. It describes the explanation as leaving the trade-off easy to understand. Use 明確に + verb when saying that an action should be done clearly.
説明 説明 means explanation or explaining in 明確に説明できるなら and 優先事項を中心に説明できます. It names the act of making the trade-off or plan understandable. Use it with を for the topic being explained, as in トレードオフを明確に説明.
できる できる means can or be able to in 明確に説明できるなら. It expresses the ability to explain clearly and is followed by なら to make a condition. Use the pattern 説明できる when stating that someone is able to explain something.
なら なら means if or in that case in 説明できるなら. It makes the ability to explain the condition for accepting the proposal. Use 〜なら、... when one action or situation depends on another.
受け入れられます 受け入れられます means can accept in this dialogue, referring to accepting the proposed compromise if the trade-off is explained clearly. The polite ending makes the statement suitable for a professional discussion. The pattern 〜なら、受け入れられます expresses conditional agreement.
優先事項 優先事項 means priority or priority item in クライアントの優先事項. It refers to what matters most to the client when shaping the solution. Use it with の to identify whose priorities are being considered.
中心 中心 means center or focus in クライアントの優先事項を中心に説明できます. It shows that the explanation will be organized around the client’s priorities. Use the pattern 〜を中心に説明 when making one topic the main focus of an explanation.
できます できます means can or is able to in 優先事項を中心に説明できます. It is the polite form of できる and presents the proposed explanation professionally. Use it after a verb or action noun when offering to do something.
決定 決定 means decision in 決定に合わせて. It refers to the agreement reached by the teammates. Use it with に合わせて when later actions should follow an agreed decision.
合わせて 合わせて means in accordance with or to match in 決定に合わせて、タスクの説明を更新します. It is the connective form of 合わせる and links the decision to the update. Use the pattern Xに合わせて Yを更新します when adjusting something to reflect a decision.
タスク タスク means task, referring to the work item being described and updated. It appears in タスクの説明. In project work, use it when referring to a specific assigned piece of work.
更新します 更新します means update in タスクの説明を更新します. It is the polite form of 更新する and describes the speaker’s planned action. Use the pattern objectを更新します when promising to bring information into line with a new decision.
それ それ means that or it in それなら. It refers to the proposal or condition just discussed. Use それなら when responding to new information and drawing a conclusion from it.
違い 違い means difference or disagreement in 意見の違い. It identifies the gap between the teammates’ opinions rather than the opinions themselves. Use the pattern nounの違い when describing a difference between two things or views.
プロジェクト プロジェクト means project in プロジェクトが遅れる. It is the work as a whole whose schedule could be affected. This word is useful when discussing the progress or timing of organized work.
遅れる 遅れる means be delayed or fall behind in プロジェクトが遅れる. It describes the project as losing time because of the disagreement. Use the pattern プロジェクトが遅れる when referring to a project’s schedule being delayed.
こと こと turns 遅れる into a noun-like event in 遅れることはないはずです. This lets the speaker discuss the possibility of the project being delayed as a topic. The pattern 〜ことはない is useful for saying that an event will not occur.
ない ない means not or there is no in 遅れることはない. Here it denies the occurrence of the project being delayed. Use the pattern 〜ことはない when reassuring someone that a particular event will not happen.
はず はず expresses an expectation in 遅れることはないはずです: based on the decision, the project should not be delayed. It follows the conclusion and presents it as the expected result. Use 〜はずです when making a reasoned expectation.

Grammar Points

〜はずです

完成版は必要なはずです。

kahn-SAY-ban wah nee-SHOH nah hah-zoo deh-soo.

The complete version should be necessary.

はず expresses an expectation or conclusion based on what is assumed to be true.

〜ている

クライアントは完成版を期待している。

koo-RAI-ahnt wah kahn-SAY-ban oh tai-KEH-shee-teh ee-roo.

The client is expecting the complete version.

ている can show an ongoing state or continuing expectation, not only an action happening now.

Japanese Vocabulary

クライアント noun
koo-RAI-ahnt client

クライアントは

バージョン noun
BAH-john version

バージョンを求めている

意見が合わない phrase
ee-KEN gah ah-wah-NAH-ee to disagree; for opinions not to match

意見が合わないのだと思います

確認する verb
kah-koo-NIN soo-roo to check; to confirm 確認しましょう
完成版 noun
kahn-SAY-ban complete version; finished version

完成版を期待している

簡単な adj
KAHN-tahn nah simple; easy

簡単なバージョン

期待する verb
tai-KEH-ee-soo-roo to expect 期待している
機能 noun
KEE-noh feature; function

すべての機能が入った

記憶 noun
kee-OH-koo memory

記憶だけで

求める verb
moh-toh-MEH-roo to want; to seek; to request 求めている
言い合う verb
ee-ee-AH-oo to argue with each other
前提 noun
zen-TEH assumption

違う前提で考えた

Quiz

Spelling

Tap the letters to spell the word.

to disagree; for opinions not to match

Show Answer意見が合わない

version

Show Answerバージョン

to want; to seek; to request

Show Answer求めている

client

Show Answerクライアント