그래서: So / That's Why (Everyday Cause)

그래서 is the first "so" every learner meets, and the one you'll reach for most: it presents the previous sentence as the reason for this one. 비가 왔어요. 그래서 집에 있었어요 — "it rained; so I stayed home." Simple enough. But 그래서 hides a restriction that trips up nearly every English speaker, and it comes from where the word is built: 그래서 states a neutral, objective cause-and-effect, and because of that, it flatly refuses to lead into a command or a suggestion. Understanding why turns an arbitrary-looking rule into something you can predict.

그래서: the everyday cause-and-effect

The pattern is: [clause A, a fact]. 그래서 [clause B, what follows from it]. A is the cause; B is the result. The relationship is presented as plain and objective — A simply led to B, the way rain leads to a wet street.

Where it comes from: 그렇다 + -아서

그래서 is 그렇다 ("to be so") + -아/어서, the everyday cause/sequence ending. 그렇다 is ㅎ-irregular, so 그렇- + -아서 contracts to 그래서 — "it being so, …". In other words, 그래서 is simply the clause-connecting ending -아/어서 lifted to the front of a new sentence: instead of joining "it rained so I stayed home" into 비가 와서 집에 있었어요, you split it and open the second sentence with 그래서. Same causal logic, one sentence break.

The constraint it inherits: no command, no suggestion

Here's the catch. Because 그래서 is built on -아/어서, it inherits that ending's signature restriction: the clause after 그래서 cannot be a command (imperative) or a suggestion (propositive "let's"). This is ungrammatical in the way a native speaker feels instantly:

Why? Because 그래서 frames its cause as an impersonal, objective fact — and an impersonal fact has no standing to tell someone what to do. A command or a suggestion is an act of the speaker's will, and it needs a reason rooted in the speaker's own judgment. 그래서 deliberately leaves that judgment out, so it can only lead into a neutral statement of result, never into "so do this" or "so let's do this." When you want a reason that supports a command or a suggestion, you switch to 그러니까.

그래서 vs 그러니까: the split English hides

English "so" is one flat, neutral word. Korean forces a choice that English never makes you make:

• 그래서 — objective, neutral cause → result. The world caused this; here's the outcome.
• 그러니까 — the speaker's own reasoning, foregrounded — and because it's the speaker's reasoning, it can precede a command or a suggestion.

This is the single most-tested "so / because" distinction in Korean, and the deciding factor is what the second clause does. If it states an outcome, 그래서 is natural. If it tells or invites someone to act, you need 그러니까 (full treatment on 그러니까 · 따라서, and the head-to-head at -아/어서 vs. -(으)니까).

그래서 as a conversational continuer

In conversation, 그래서 also works as a prompt to keep going — "so? and then?" — inviting the speaker to finish their story. On its own with a rising tone (그래서요? / 그래서?) it means "so what happened next?"

This is 그래서 doing pure discourse work — you're not stating a cause, you're pushing the narrative forward. (For the broader family of these spoken "so" pivots, see 그래서 · 그러니까 as discourse markers.)

Prefer fusing with -아서 when you can

Just as with 하지만 and its ending -지만, native speech often fuses a 그래서 sentence back into a single clause with -아/어서, rather than splitting it. Two sentences joined by 그래서 can feel choppy where one flowing clause would do.

Use 그래서 when you genuinely want a fresh sentence — for emphasis, or after a longer first clause — and reach for the fused -아/어서 when the two ideas are tight enough to live in one breath.

Common Mistakes

1. Putting 그래서 before a command. An imperative can't follow it; switch to 그러니까.

2. Putting 그래서 before a suggestion. Same block with a "let's" clause.

3. Splitting with 그래서 where -아서 flows better. Grammatical, but often choppy — fuse it.

4. Using 그래서 for a formal, written "therefore." In academic or official prose, the elevated "therefore" is 따라서, not the conversational 그래서.

Key Takeaways

• 그래서 = the everyday "so / that's why" — it presents A as a neutral, objective cause of B.
• It's 그렇다 + -아/어서, so it's frozen (no tense, no honorific) and inherits that ending's rules.
• No command or suggestion after 그래서 — for those, use 그러니까, which foregrounds the speaker's reasoning.
• English "so" hides this split; Korean makes you choose 그래서 (objective) vs. 그러니까 (reasoned) before the second clause — the most-tested "so" distinction.
• 그래서? / 그래서요? also works as a conversational continuer ("so then what?").
• For tight cause-and-effect in one breath, fuse with -아/어서 instead of splitting; for formal written "therefore," use 따라서.