Resolving a Small Disagreement at Work | Learn Korean in English

About This Lesson

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

Dialogue

서로 다른 가정을 해서 의견이 다른 것 같아요.

suh-ROH DAH-reun gah-JUNG-ul HAE-suh ee-GYUN-ee DAH-reun gut gah-TAH-yoh. I think we disagree because we made different assumptions.

고객이 먼저 간단한 버전을 원한다고 생각했어요.

goh-GAEK-ee MUN-juh gan-DAHN-han BUH-jun-ul WON-han-dah-go seng-GAH-kae-ssuh-yoh. I thought the client wanted a simple version first.

저는 고객이 모든 기능이 들어간 완성된 버전을 기대한다고 생각했어요.

juh-nun goh-GAEK-ee MOH-deun gee-NEUNG-ee deu-ruh-GAHN wan-SUNG-dwen BUH-jun-ul gee-DAE-han-dah-go seng-GAH-kae-ssuh-yoh. I thought they expected a complete version with every feature.

기억에 의존해서 논쟁하는 대신 메모를 확인해 봐요.

gee-UHK-eh ee-JOHN-hae-suh non-JAENG-ha-nun dae-SHIN meh-MOH-reul hwah-GEEN-hae BWAH-yoh. Let's check the notes instead of arguing from memory.

메모에는 속도가 가장 중요하지만 고급 기능 하나는 여전히 필요하다고 적혀 있어요.

meh-MOH-eh-nun SOHK-doh-gah gah-JAHNG joong-YOH-hah-jee-man goh-GEUP gee-NEUNG HAH-nah-nun yuh-JUN-hee pee-RYOH-hah-dah-go juh-KYUH ee-SSUH-yoh. The notes say speed matters most, but one advanced feature is still required.

그 기능이 들어간 더 간단한 버전이 적절한 타협안 같아요.

guh gee-NEUNG-ee deu-ruh-GAHN duh gan-DAHN-han BUH-jun-ee juk-JUHL-han tah-HYUH-bahn gah-TAH-yoh. A simpler version that includes that feature sounds like the right compromise.

그 타협의 장단점을 분명하게 설명한다면 받아들일 수 있어요.

guh tah-HYUH-beh jahng-DAHN-juhm-ul boon-MYUNG-hah-geh sul-MYUNG-han-dah-myun bah-dah-deu-REEL soo ee-SSUH-yoh. I can accept that if we explain the trade-off clearly.

고객의 우선순위를 중심으로 설명할 수 있어요.

goh-GAEK-eh oo-SUN-soon-WEE-reul joong-SHIM-uh-roh sul-MYUNG-hal soo ee-SSUH-yoh. We can frame it around the client's priorities.

결정한 내용에 맞게 작업 설명을 수정할게요.

gyul-JUNG-han nae-YONG-eh maht-GEH jah-GUHM sul-MYUNG-ul soo-JUNG-hal-GEH-yoh. I'll update the task description to match the decision.

그러면 그 의견 차이 때문에 프로젝트 진행이 늦어지지는 않을 거예요.

guh-ruh-MYUN guh ee-GYUN chah-EE ttae-MOON-eh puh-roh-JEK-teu jin-HAENG-ee neu-juh-JEE-jee-nun ah-NEUL guh-YEH-yoh. Then the disagreement should not slow the project down.

Word by Word

서로 “서로” means mutually or each other; here it shows that the assumptions differ between the people involved. It is used with an action or state shared between two or more people, as in “서로 다른 가정을”. This is useful when comparing two teammates’ views.

다른 “다른” means different and describes the noun “가정을”. It is the noun-modifying form of 다르다, so it appears before a noun in “서로 다른 가정을”. Use this form when distinguishing one thing from another.

가정을 “가정을” means assumptions and marks them as the object of making assumptions. In “서로 다른 가정을 해서”, the speakers made different assumptions, which caused the disagreement. The pattern “가정을 하다” is useful when discussing beliefs about a situation.

해서 “해서” links making assumptions with the resulting disagreement, giving the meaning “because of making” or “by making”. It is the connective form of 하다. A verb or action followed by 해서 can introduce a reason or cause.

의견이 “의견이” means opinions or views, with 이 marking them as the subject of “다른”. In “의견이 다른 것 같아요”, the meaning is that the opinions differ. The pattern “의견이 다르다” is useful for describing a disagreement neutrally.

것 In “의견이 다른 것 같아요”, “것” turns the preceding situation into something that can be described as seeming a certain way. Together with “같아요”, the phrase means “it seems that the opinions differ”. The pattern clause + 것 같아요 is useful for giving a cautious assessment.

같아요 In “의견이 다른 것 같아요”, “같아요” makes the preceding statement sound like an impression or inference: “it seems” or “I think”. It is the polite form related to 같다. Use this construction when stating an assessment without sounding completely definite.

고객이 “고객이” means the client and marks the client as the subject of wanting in the quoted idea. In “고객이 먼저 간단한 버전을 원한다고”, the client is the person whose preference is being reported. This pattern is useful when explaining what a client wants.

먼저 “먼저” means first and establishes the order in which something should happen. Here it says that the simple version is wanted before a later or more complete version. It is commonly placed before the action or item that comes first.

간단한 “간단한” means simple and describes “버전”. It is the noun-modifying form of 간단하다, so it appears before the noun in “간단한 버전을”. Use this form when describing a simple product, plan, or explanation.

버전을 “버전을” means version and marks the version as the object of what the client wants. In “간단한 버전을 원한다고”, the client wants a simple version first. The object-marking form is useful when identifying the version being requested.

원한다고 “원한다고” reports that someone wants something; here it means “that the client wants”. It combines 원하다 with the indirect-quotation ending -다고 before “생각했어요”. This pattern is useful when reporting another person’s request or preference.

생각했어요 “생각했어요” means thought and presents the speaker’s earlier belief politely. It is the past polite form related to 생각하다 and follows the reported idea in “원한다고 생각했어요”. Use this pattern when explaining what you previously believed about a situation.

저는 “저는” means “as for me” or “I”, with 는 marking the speaker as the topic. Here it contrasts the speaker’s assumption with the teammate’s assumption. It is useful when politely presenting your own position during a disagreement.

모든 “모든” means all or every and describes “기능”. In “모든 기능이 들어간”, it indicates that the version includes every feature under discussion. It is a determiner placed directly before a noun when referring to a complete set.

기능이 “기능이” means feature or function, with 이 marking it as the subject of “들어간”. In “기능이 들어간 버전”, the features are what are included in the version. This pattern is useful when describing the scope of a product or version.

들어간 “들어간” means included or containing in “기능이 들어간 버전”. It is the noun-modifying form related to 들어가다 and describes a feature as being included in something. Use it before a noun when specifying what a product or version contains.

완성된 “완성된” means completed or finished and describes “버전”. It is the noun-modifying form related to 완성되다, giving “완성된 버전” the meaning “a complete version”. This form is useful when discussing the state of a deliverable.

기대한다고 “기대한다고” reports that someone expects something; here it means “that the client expects”. It combines 기대하다 with the indirect-quotation ending -다고 before “생각했어요”. This pattern is useful when reporting another person’s expectations about a result.

기억에 “기억에” means in or based on memory in the expression “기억에 의존해서”. The particle 에 marks memory as what the reliance is placed on. This form is useful when describing information or decisions based on remembered details.

의존해서 “의존해서” means relying on and connects reliance on memory with the action of arguing. It is the connective form related to 의존하다 in “기억에 의존해서 논쟁하는”. Use this pattern when explaining that an action is based on a source or support.

논쟁하는 “논쟁하는” means arguing and describes the activity in “논쟁하는 대신”. It is the noun-modifying form related to 논쟁하다. Together with 대신, it presents arguing as the action to avoid in favor of checking the notes.

대신 In “논쟁하는 대신”, “대신” means instead of and introduces the action chosen in place of arguing. The construction means “instead of arguing from memory”. It is useful when proposing a different action as an alternative.

메모를 “메모를” means the notes or memo and marks them as the object of checking. In “메모를 확인해 봐요”, the speakers choose the written notes as their evidence. This form is useful when referring to notes, records, or documented project information.

확인해 “확인해” means check or confirm and connects the action to “봐요” in “확인해 봐요”. It is the connective form related to 확인하다. The construction suggests trying the action of checking something.

봐요 In “확인해 봐요”, “봐요” functions as an auxiliary related to 보다, not as the main meaning “see”. Together, the phrase politely suggests trying or checking the notes. This construction is useful when proposing an action to a colleague.

메모에는 “메모에는” means “in the notes” or “as for the notes”, combining 에 with the topic marker 는. In “메모에는 ... 적혀 있어요”, it introduces information recorded in the notes. This pattern is useful when stating what a document or record says.

속도가 “속도가” means speed, with 이 marking it as the subject of what is important. In “속도가 가장 중요하지만”, speed is identified as the highest priority. The pattern “속도가 중요하다” is useful when discussing project priorities.

가장 “가장” means most and modifies “중요하지만” to identify the highest degree of importance. Here it shows that speed matters more than the other considerations mentioned. Use it before an adjective when selecting the top priority.

중요하지만 “중요하지만” means “is important, but” and connects the priority of speed with an exception. It combines 중요하다 with the contrastive ending -지만. This form is useful when acknowledging one priority while adding another condition.

고급 “고급” means advanced or high-level and describes “기능”. In “고급 기능”, it identifies the feature as an advanced feature required by the client. It is placed before a noun when discussing the level or sophistication of a product element.

기능 “기능” means feature or function. In “고급 기능 하나”, it refers to one particular product feature that must remain in the simpler version. This noun is useful when discussing what a software product or service can do.

여전히 “여전히” means still and shows that the requirement remains despite speed being the highest priority. In “여전히 필요하다고”, the advanced feature is still needed. Use it when a condition continues even after another fact has been considered.

필요하다고 “필요하다고” means “that it is needed” or “that it is required”. It combines 필요하다 with the indirect-quotation ending -다고 in “여전히 필요하다고 적혀 있어요”. This pattern is useful when reporting a requirement written in notes or stated by someone.

적혀 “적혀” means written or recorded and connects with “있어요” in “필요하다고 적혀 있어요”. It is related to 적히다 and describes information as being recorded in the notes. This construction is useful when referring to documented requirements or instructions.

있어요 In “적혀 있어요”, “있어요” indicates that the written state remains in place, rather than simply saying that something exists. It is the polite form related to 있다. The pattern verb + 어 있다 is useful for describing a continuing resulting state.

그 “그” means that or the aforementioned and points back to the advanced feature already discussed. In “그 기능이 들어간”, it identifies the specific feature shared in the conversation. Use it before a noun when both speakers know which item is meant.

더 “더” means more and modifies “간단한” in “더 간단한 버전”. It indicates a greater degree of simplicity compared with the version previously considered. It is commonly placed before an adjective in a comparison.

버전이 “버전이” means version, with 이 marking it as the subject of the evaluation. In “버전이 적절한 타협안 같아요”, the version is judged to seem like a suitable compromise. This pattern is useful when assessing a proposed option.

적절한 “적절한” means appropriate or suitable and describes “타협안”. It is the noun-modifying form related to 적절하다. Use it before a noun when evaluating whether a proposal fits the situation.

타협안 “타협안” means a compromise proposal or middle solution. Here, the simpler version that keeps the required feature is presented as “적절한 타협안”. This noun is useful when agreeing on a practical solution between different positions.

타협의 “타협의” means “of the compromise”, with 의 showing the relationship between the compromise and its pros and cons. In “타협의 장단점을”, it introduces what is gained and lost by the compromise. This pattern is useful when explaining the effects of an agreed solution.

장단점을 “장단점을” means the pros and cons and marks them as the object of explaining. In “타협의 장단점을 분명하게 설명한다면”, the speakers will clearly explain the compromise’s benefits and drawbacks. This expression is useful when evaluating an option fairly.

분명하게 “분명하게” means clearly and modifies “설명한다면”. It is the adverbial form related to 분명하다. Use it when emphasizing that information, reasons, or trade-offs should be communicated without ambiguity.

설명한다면 “설명한다면” means “if we explain” and sets a condition for accepting the compromise. It combines 설명하다 with the conditional ending -다면. This form is useful when connecting a proposed action with its expected result.

받아들일 “받아들일” means accept in “받아들일 수 있어요”, referring to accepting the proposed compromise. It is the noun-modifying form related to 받아들이다 before the dependent noun 수. The construction is useful for saying that someone can accept an idea or decision.

수 In “받아들일 수 있어요”, “수” is a dependent noun used with the preceding verb form to express ability or possibility. The whole phrase means “can accept that”. The pattern verb + 을 수 있다 is useful when stating what is possible or what someone is able to do.

고객의 “고객의” means the client’s, with 의 marking possession or relationship. In “고객의 우선순위를”, it identifies whose priorities should guide the explanation. This pattern is useful when referring to a client’s needs, goals, or preferences.

우선순위를 “우선순위를” means priorities and marks them as the focus of “중심으로”. In “고객의 우선순위를 중심으로”, the explanation is organized around what matters most to the client. This expression is useful when shaping a proposal around a customer’s priorities.

중심으로 “중심으로” means with something as the center or around something. In “우선순위를 중심으로 설명할 수 있어요”, it shows that the explanation is organized around the client’s priorities. The pattern noun + 을 중심으로 is useful for describing the main focus of a discussion.

설명할 “설명할” means explain and appears before “수 있어요” in “설명할 수 있어요”. It is the noun-modifying form related to 설명하다 used in the ability construction. This pattern is useful when saying that someone can explain a plan or decision.

결정한 “결정한” means decided and describes “내용”. It is the noun-modifying form related to 결정하다, so “결정한 내용” means the content or result that was decided. This form is useful when referring to a completed decision.

내용에 “내용에” means “to the content” or “to what was decided” in “결정한 내용에 맞게”. The particle 에 marks the standard that something should match. This expression is useful when updating material according to an agreed decision.

맞게 “맞게” means in a way that matches or in accordance with. In “결정한 내용에 맞게”, it shows that the task description will be revised to fit the decision. The pattern noun + 에 맞게 is useful when adapting something to a requirement or standard.

작업 “작업” means task or work and forms the compound noun “작업 설명”. Here it identifies which description will be updated. This noun is useful in workplace discussions about an assigned task or piece of work.

설명을 “설명을” means the description and marks it as the object of revising. In “작업 설명을 수정할게요”, it refers specifically to the written description of the task. This form is useful when talking about updating project documentation.

수정할게요 “수정할게요” means “I’ll revise” or “I’ll update” and expresses the speaker’s commitment to take the action. It is related to 수정하다 and uses the ending -ㄹ게요. This ending is useful when promising or volunteering to do something for the other person.

그러면 “그러면” means then or in that case and introduces the consequence of the agreement just reached. Here it leads to the expected result that the project will not be delayed. Use it after a condition, decision, or shared conclusion.

의견 “의견” means opinion or view. In “의견 차이”, it is part of the expression “difference in opinions”, rather than meaning disagreement by itself. This noun is useful for discussing people’s views in a neutral workplace tone.

차이 “차이” means difference and completes “의견 차이”, meaning a difference in opinions. It presents the disagreement as a gap between views rather than as a personal conflict. This expression is useful when describing a small difference between teammates’ positions.

때문에 “때문에” means because of and marks the cause in “의견 차이 때문에”. The phrase says that the difference in opinions could cause the project to slow down. The pattern noun + 때문에 + result is useful for explaining a reason.

프로젝트 “프로젝트” means project. In “프로젝트 진행이”, it identifies the work whose progress might be affected by the disagreement. This noun is useful in workplace conversations about schedules, tasks, and deliverables.

진행이 “진행이” means progress or proceeding, with 이 marking it as the subject of “늦어지다”. In “프로젝트 진행이 늦어지지는 않을 거예요”, it is the project’s progress that is expected not to be delayed. This phrasing is useful when discussing whether work will stay on schedule.

늦어지지는 “늦어지지는” means “be delayed” with 는 adding emphasis to the possibility that is being denied. In “늦어지지는 않을 거예요”, the speaker reassures the teammate that the project will not be delayed. This form is useful when explicitly denying an unwanted outcome.

않을 “않을” means will not or not be in “늦어지지는 않을 거예요”. It is the noun-modifying form of 않다 used before “거예요” to form a negative expected result. This construction is useful when predicting that an action or state will not happen.

거예요 In “않을 거예요”, “거예요” expresses an expected or predicted future result. Together with “않을”, it means that the project is expected not to be delayed. The pattern verb or adjective + 을 거예요 is useful when stating a prediction or expectation.

Grammar Points

-다고

모든 기능이 필요하다고

MOH-deun gee-NEUNG-ee pee-RYOH-hah-dah-go

that every feature is necessary

한국어에서는 생각이나 기대의 내용을 인용할 때 형용사·동사 뒤에 -다고를 붙입니다.

-지만

속도가 가장 중요하지만 여전히 필요하다

SOHK-doh-gah gah-JAHNG joong-YOH-hah-jee-man yuh-JUN-hee pee-RYOH-hah-dah

Although speed is the most important, it is still necessary.

-지만은 앞뒤 내용이 반대되거나 대조될 때 사용하는 연결 어미입니다.

Korean Vocabulary

가정 noun

gah-JUNG assumption 가정을

서로 다른 가정을 해서 의견이 다른 것 같아요.

간단하다 adj

gan-DAHN-hah-dah to be simple 간단한

고객이 먼저 간단한 버전을 원한다고 생각했어요.

고객 noun

goh-GAEK client; customer 고객이

고객이 먼저 간단한 버전을 원한다고 생각했어요.

기능 noun

gee-NEUNG feature; function

저는 고객이 모든 기능이 들어간 완성된 버전을 기대한다고 생각했어요.

기대하다 verb

gee-DAE-hah-dah to expect 기대한다고

저는 고객이 모든 기능이 들어간 완성된 버전을 기대한다고 생각했어요.

기억 noun

gee-UHK memory 기억에

기억에 의존해서 논쟁하는 대신 메모를 확인해 봐요.

다르다 adj

dah-REU-dah to be different 다른

서로 다른 가정을 해서 의견이 다른 것 같아요.

먼저 adv

MUN-juh first

고객이 먼저 간단한 버전을 원한다고 생각했어요.

모든 det

MOH-deun every; all

저는 고객이 모든 기능이 들어간 완성된 버전을 기대한다고 생각했어요.

서로 adv

suh-ROH each other; mutually

서로 다른 가정을 해서 의견이 다른 것 같아요.

완성되다 verb

wan-SUNG-dweh-dah to be complete 완성된

저는 고객이 모든 기능이 들어간 완성된 버전을 기대한다고 생각했어요.

원하다 verb

WON-hah-dah to want 원한다고

고객이 먼저 간단한 버전을 원한다고 생각했어요.

Quiz

Word Order

Arrange the words in the correct order.

I thought the client wanted a simple version first.

Show Answer

고객이 먼저 간단한 버전을 원한다고 생각했어요.

We can frame it around the client's priorities.

Show Answer

고객의 우선순위를 중심으로 설명할 수 있어요.

I'll update the task description to match the decision.

Show Answer

결정한 내용에 맞게 작업 설명을 수정할게요.

Spelling

Tap the letters to spell the word.

to want

Show Answer

원한다고

to expect

Show Answer

기대한다고

to be simple

Show Answer

간단한

each other; mutually

Show Answer

서로