12 Common Keigo Mistakes Learners Make

Many learners feel “safe” once they use polite です/ます forms. In Japanese workplace contexts, though, a small Keigo error can reverse the direction of respect. The sentence may sound polite to you, yet sound odd, overdone, or wrongly aimed to a Japanese listener.

This article covers the 12 most common Keigo mistakes among learners, with fixes framed by the official five categories in the 敬語けいごの指針ししん. The goal is not term memorization—it is function: who is raised, who is lowered, and who the sentence is for.

Why Keigo Mistakes Happen So Often

Four causes show up again and again:

1. Treating every “longer” form as automatically more polite.
2. Mixing the functions of 尊敬語そんけいご and 謙譲語けんじょうご.
3. Forgetting uchi-soto (in-group vs out-group).
4. Translating word-for-word from the learner’s first language.

Keigo is a system of functions. Two forms can both sound polite while aiming respect at different people. If the target is wrong, the sentence is still wrong.

Quick Map of the 5 Categories (Keep Them Straight)

If you keep these functions open while you speak or write, most errors never start.

12 Common Mistakes and How to Fix Them

1) Using 尊敬語そんけいご for yourself

This is the most basic error. 尊敬語そんけいご is for the person you respect—not for you or your in-group.

2) Using 謙譲語けんじょうごI for your own boss when speaking to a client

When you speak to outsiders, your boss still belongs to your in-group (uchi). Do not raise your own boss in front of a client.

3) Swapping 謙譲語けんじょうごI and II

Classic case: 先生せんせいが参まいりました. Wrong, because 参まいる is KII from the speaker’s side—not for elevating 先生せんせい.

4) Treating 二重敬語にじゅうけいご as always more polite

Not every doubled form is accepted. Some sound excessive or unnatural. Respect must match function—not just stack.

5) Mixing categories without a clear respect target

The line looks polite, but if the subject and the respect target do not match, listeners feel something is off. Common in meetings and email.

6) Overusing させていただく

Official guidance lists two main conditions:

1. Permission from someone else.
2. A sense of benefit or gratitude for that permission.

Without both, a simpler form such as いたします is usually better.

7) Choosing the wrong お / ご prefix

Not every word takes お or ご freely. Prefix choice depends on word type and fixed usage.

8) Full Keigo with close friends

Keigo is not always wrong, but with close friends overuse creates an unnatural social distance.

9) Forgetting uchi-soto when introducing in-group people

Many speakers still add さん or high honorifics for their own colleagues when speaking to a client. In Japanese business culture, that is incorrect.

10) Literal translation from the first language

Phrases such as “I am waiting for you,” if translated raw, often sound blunt or unnatural in Japanese service and business settings.

11) Using ordinary ability forms for formal service speech

Common case: 御乗車ごじょうしゃできません. In formal announcements, a more appropriate honorific service pattern keeps the right register.

12) Mixing copula levels (だ / です / でございます)

Starting casual and ending highly formal breaks the register. Pick one level for the context and keep it to the end.

12 Wrong vs Right Examples (3 Layers + Blue Marker)

Mistake 1: Sonkeigo for yourself

Wrong: 私わたしがいらっしゃいます。

Right: 私わたしがおります。 Watashi ga orimasu. I am here.

Mistake 2: Raising your own boss to a client

Wrong: 部長ぶちょうが伺うかがいます。

Right: 部長ぶちょうが参まいります。 Buchou ga mairimasu. Our manager will come.

Mistake 3: KI–KII swapped (先生せんせいが参まいる)

Wrong: 先生せんせいが参まいりました。

Right: 先生せんせいがいらっしゃいました。 Sensei ga irasshaimashita. The teacher has arrived.

Mistake 4: Excessive 二重敬語にじゅうけいご

Wrong: 先生せんせいがお読よみになられました。

Right: 先生せんせいがお読よみになりました。 Sensei ga o-yomi ni narimashita. The teacher has read it.

Mistake 5: Mixed categories with no clear direction

Wrong: 私わたしがお待まちになっております。

Right: 私わたしがお待まちしております。 Watashi ga o-machi shite orimasu. I am waiting.

Mistake 6: させていただく for everything

Wrong: 資料しりょうを送付そうふさせていただきます。

Right: 資料しりょうを送付そうふいたします。 Shiryou o soufu itashimasu. We will send the documents.

Mistake 7: Wrong お / ご prefix

Wrong: お確認かくにんください。

Right: ご確認かくにんください。 Go-kakunin kudasai. Please check.

Mistake 8: Too much Keigo with a close friend

Wrong: 昨日きのうはいかがでしたか。

Right (friend context): 昨日きのうはどうだった？ Kinou wa dou datta? How was yesterday?

Mistake 9: Uchi-soto when introducing a colleague

Wrong: 弊社へいしゃの田中たなかさんがご説明せつめいします。

Right: 弊社へいしゃの田中たなかが説明せつめいいたします。 Heisha no Tanaka ga setsumei itashimasu. Tanaka from our company will explain.

Mistake 10: Literal translation from the first language

Wrong: 私わたしはあなたを待まっています。

Right: 到着とうちゃくをお待まちしております。 Touchaku o o-machi shite orimasu. We await your arrival.

Mistake 11: Weak service wording

Wrong: 御乗車ごじょうしゃできません。

Right: 御乗車ごじょうしゃになれません。 Go-jousha ni naremasen. You cannot board.

Mistake 12: Inconsistent copula level

Wrong: こちらが資料しりょうだ。よろしくお願ねがいいたします。

Right: こちらが資料しりょうです。よろしくお願ねがいいたします。 Kochira ga shiryou desu. Yoroshiku onegai itashimasu. This is the document. Thank you for your cooperation.

When させていただく Is Truly Correct

Before you use that form, answer these two questions:

1. Is there permission or approval from someone else?
2. Am I expressing benefit or gratitude for that permission?

If both answers are “yes,” させていただく is usually right. If not, prefer a shorter form such as いたします.

Correct example:

• 本日ほんじつは皆様みなさまのご了承りょうしょうをいただき、発表はっぴょうさせていただきます。

Overdone example:

• 資料しりょうを共有きょうゆうさせていただきます。 (routine action with no permission context)

Lighter form:

• 資料しりょうを共有きょうゆういたします。

Fast Diagnosis When You Hesitate Mid-Conversation

In a meeting or on a call, you do not have time for a long grammar analysis. Use this three-step check:

1. Check the subject of the action: who is doing this?
2. Check the direction of the action: does it move toward an outsider, or only describe your own action?
3. Check the politeness goal: raise the other person, lower yourself, or keep a neutral formal tone?

With those three steps, the category choice usually becomes clear:

• Respected person as actor: lean 尊敬語そんけいご.
• You as actor, action toward the respected person: lean 謙譲語けんじょうごI.
• You as actor, action only described politely: lean 謙譲語けんじょうごII.
• Goal is only neutral formality: 丁寧語ていねいご.

Quick decision examples:

• “I will send the file” to a client: actor = me, direction = to the client, goal = professional politeness. Safe choice: a KI/KII combination such as 送付そうふいたします.

• “Our director will attend” to a partner: actor = in-group person, context = speaking to outsiders. Do not raise in-group people. Choose a form that places them neutrally or humbly.

This approach blocks the two biggest failures: using the same form in every situation, and panicking into forms that are too high.

7-Day Practice Plan to Clear the 12 Errors

Practice needs structure, not theory alone. Use this 20–30 minute daily format:

1. Day 1: Focus on errors #1–#3 (basic respect direction). Convert 20 simple sentences into correct forms.
2. Day 2: Focus on errors #4–#6 (overlong forms). Strike every form that is too long; replace with the best fit.
3. Day 3: Focus on errors #7–#8 (prefixes and social context). Build a fixed お/ご word list and when each is used.
4. Day 4: Focus on errors #9–#10 (uchi-soto + naturalness). Practice introducing in-group colleagues to clients.
5. Day 5: Focus on errors #11–#12 (service register + copula consistency). Write a short formal announcement script.
6. Day 6: Mixed simulation. Role-play a 5-minute meeting and check every error against the checklist.
7. Day 7: Full review. Record yourself, transcribe, and mark lines still at risk for the wrong category.

Repeat the 7-day cycle two or three times. Wrong patterns drop fast when you train the selection process—not phrase memory alone.

Anti-Error Checklist Before You Send Email or Speak

• Who is the subject: you, a superior, or a client?
• Who is this sentence raising?
• If you use KI, is there an “action direction” toward the respected person?
• If you use KII, is this purely a polite description of your own action?
• Is casual and formal mixed in the same block?
• Does させていただく meet both conditions?
• Is uchi-soto consistent for everyone named?

The checklist is simple, and it stops the same errors from repeating.

New Vocabulary

Conclusion

The most dangerous Keigo mistake is not the “impolite” one—it is the line that sounds polite on the surface but has the wrong function. The fix is not more complex forms. It is the right direction of respect and social context.

In short:

1. Master the five-category map and each function.
2. Check KI vs KII every time you write a formal sentence.
3. Break automatic habits such as overusing させていただく.
4. Keep uchi-soto and register level consistent from start to finish.

Once these 12 traps are under control, your workplace Keigo rises quickly.

Practical Navigation:

• Previous: Keigo for Meetings & Presentations
• Next: Everyday Keigo

Also Read:

• Kenjougo I (Directed Humble Language)
• Kenjougo II / Teichougo (Polite Humble Language)
• Comparison of the 5 Keigo Types
• Keigo for Business Email
• Complete Keigo Guide