차곡 문형첩

No. 006 · 2026.09.04 Fri

문형 해설

PATTERNS
TOPIK 1-2

N한테 [께]

to (someone)

Marks who an action is directed at, attaching to people and animals. 한테 is the spoken form; 에게 is used in writing and formal settings, and 께 is the honorific for someone senior. With 께 the verb rises to match — 주다 becomes 드리다.

접속 conjugation
  • person or animal + 한테: 친구한테 물어봤어요
  • honorific 께, with the verb raised too: 부장님께 보고드렸습니다
  • not for inanimate things — use 에: 회사에 연락했습니다 (✗ 회사한테)
이 자료는 제가 팀장님께 직접 전달하겠습니다.
I'll hand this document to the team leader myself.

한테 leans colloquial; business writing and reports take 에게 or 께. And "from someone" is 한테서 / 에게서: 친구한테서 들었어요.

TOPIK 3-4

누구나

anyone, everyone

누구 (who) plus 나, meaning everyone without exception. It usually stands as the subject on its own, with no subject particle. The same shape gives 언제나, 어디나 and 무엇이나.

접속 conjugation
  • 누구 + 나, used directly as the subject: 누구나 실수할 수 있습니다
  • often followed by what is possible or to be expected: 누구나 알 수 있는 방법이에요
  • same shape: 언제나 (any time), 어디나 (anywhere), 무엇이나 (anything)
처음에는 누구나 실수하니까 너무 걱정하지 마세요.
Everyone makes mistakes at first, so try not to worry.

누구나 means everyone, no exceptions; 아무나 means just anyone will do — a different tone: 이 일은 누구나 할 수 있어요 (anyone can do this) / 아무나 들어오면 안 돼요 (not just anyone may come in).

TOPIK 5-6

N(으)로 인해

due to, owing to

Names what caused a result. It belongs to news, reports and official notices. The cause is normally an event or a situation rather than something a person chose to do. Before a noun it becomes -로 인한.

접속 conjugation
  • noun without a final consonant + 로 인해: 폭우로 인해 행사가 연기됐습니다
  • noun with a final consonant + 으로 인해: 정전으로 인해 작업이 중단됐습니다
  • before a noun, -로 인한: 지연으로 인한 손실
폭우로 인해 이번 주 행사가 다음 달로 연기되었습니다.
Owing to heavy rain, this week's event has been put back to next month.

This is formal written Korean; in speech 때문에 does the job. The cause is normally an event or condition, not a person's own action — "because I forgot" is 제가 잊어버려서, not 제가 잊어버린 것으로 인해.

비즈니스 회화

BUSINESS

외주 비용 피드백과 개선안 Outsourcing costs: feedback and a fix——Team Leader Cho points out that last month's outsourcing costs ran over, partly through work that had to be redone. Seoyun accepts the scheduling mistake and proposes weekly progress reports and a look at automation.조 팀장=Team Leader Cho (manager) / 서윤=Seoyun (team member)

조 팀장서윤 씨, 지난달 외주 비용 보고서 봤어요. 금액이 예상보다 많이 올라갔네요.
Seoyun, I've looked at last month's outsourcing costs. The figure came in well above what we projected.
서윤네, 급하게 인력을 추가하면서 늘어났습니다. 제가 일정을 잘못 잡은 탓입니다.
Yes — we brought people in at short notice and that pushed it up. The scheduling was my mistake.
조 팀장일정 문제는 누구나 겪어요. 다만 같은 작업을 두 번 시킨 부분은 낭비였어요.
Scheduling goes wrong for everyone. But having the same work done twice — that part was waste.
서윤맞습니다. 중간 확인을 건너뛴 것으로 인해 작업을 처음부터 다시 하게 됐습니다.
You're right. Skipping the mid-point check meant the work had to be redone from the start.
조 팀장그럼 다음 달부터는 어떻게 할 생각이에요?
So what's your plan from next month?
서윤주 단위로 진행 상황을 정리해서 팀장님께 먼저 보고드리겠습니다. 그러면 더 경제적으로 운영할 수 있습니다.
I'll pull the progress together week by week and report to you first. That should make it run more economically.
조 팀장좋아요. 단순 노동에 가까운 작업은 자동화를 먼저 검토해 봐요. 팀 발전에도 도움이 될 거예요.
Good. For anything close to routine labour, look at automating it first. It'll help the team grow, too.
서윤네, 이번 주 안에 비교해서 정리하겠습니다. 같은 소득이면 비용을 줄이는 쪽으로 가겠습니다.
Understood. I'll compare the options and write it up this week. Same income, lower cost — that's the direction.