Why studying keigo does not produce keigo
The standard way to learn keigo is as a transformation system: take a verb, apply a rule, produce the honorific or humble form. This is how it is taught and tested, and it builds the ability to perform the transformation when asked.
Real use does not ask. It requires the finished form to arrive while you are also parsing what a customer said, deciding what to tell them, and managing the rest of the sentence. A transformation you can perform in four seconds is not available at all in that moment.
This is why keigo is the first thing to collapse when a learner is tired or under pressure. It is not that the knowledge went; it is that it was never automatic enough to survive competition for attention.
Drill sentences, not transformations
The fastest route to usable keigo is to bypass the transformation entirely and learn whole sentences. Real keigo use is heavily formulaic: the same phrases recur constantly, and native speakers are largely retrieving rather than generating them too.
Twenty set sentences that fit your actual situations will outperform a complete understanding of the system, because they are available in the moment where the system is not.
| Japanese | Romaji | Meaning |
|---|---|---|
| 少々お待ちください。 | Shōshō omachi kudasai. | Please wait a moment. |
| かしこまりました。 | Kashikomarimashita. | Certainly. (accepting an instruction) |
| 確認いたします。 | Kakunin itashimasu. | I will check. |
| 申し訳ございません。 | Mōshiwake gozaimasen. | I am very sorry. |
| お伺いしてもよろしいでしょうか。 | Oukagai shite mo yoroshii deshō ka. | May I ask you something? |
| 承知いたしました。 | Shōchi itashimashita. | Understood. |
These six alone cover an enormous proportion of workplace and customer interaction. Learn them as fixed units, with their rhythm, rather than analysing them.
The forms worth automating first
Beyond set phrases, a small number of irregular verbs do most of the work, because they are the verbs that come up constantly: to go, to come, to be, to do, to say, to see. Automating these six in both directions covers most of what you will need to generate yourself.
Learn them as pairs against the plain form rather than as a table to recite. What you need is the finished form on demand, not the ability to reconstruct the table.
| Plain | Humble (your action) | Honorific (their action) |
|---|---|---|
| する | いたします | なさいます |
| 行く | 参ります | いらっしゃいます |
| 来る | 参ります | いらっしゃいます |
| いる | おります | いらっしゃいます |
| 言う | 申します | おっしゃいます |
| 見る | 拝見します | ご覧になります |
| 聞く | 伺います | お聞きになります |
Drill down the humble column first. You describe your own actions far more often than you describe a superior's, so that column is what a workplace demands immediately.
A drill routine that builds speed
The routine has one rule: everything is said aloud, at speed, with the finished form as the target rather than the transformation. Written exercises build the wrong skill for this purpose.
Keep sessions short and frequent. Keigo drilling is fatiguing and fifteen minutes a day for two weeks does far more than a long weekend session.
- Five minutes: say the six irregular verbs in humble form, aloud, until instant.
- Five minutes: ten set sentences for your own situations, aloud, at speed.
- Five minutes: answer prompts in role, not as an exercise but as a reply.
- Add a time limit; if the form takes more than two seconds it is not ready.
- Repeat the same twenty items for two weeks before adding anything.
Common errors that are not worth worrying about
Learners often avoid using keigo at all for fear of getting it wrong, which is the worse outcome. Most keigo errors are minor and are read as inexperience rather than as rudeness, and the alternative of using none at all is more noticeable than any of them.
Two errors are worth knowing about because they are extremely common and easy to fix, but neither causes offence.
| Japanese | Romaji | Meaning |
|---|---|---|
| ご覧になられますか。 | Goran ni naremasu ka. | Doubled honorific, common and tolerated |
| ご覧になりますか。 | Goran ni narimasu ka. | The standard form |
| 伺わせていただきます。 | Ukagawasete itadakimasu. | Over-humble, very common |
| 伺います。 | Ukagaimasu. | The standard form |
| 部長は今おりません。 | Buchō wa ima orimasen. | Humble form used for a superior, an error |
| 部長は今おりません。（社外の人に対して） | Buchō wa ima orimasen. (shagai no hito ni taishite) | Correct when speaking to someone outside the company |
The last pair is the genuinely tricky part of keigo: inside your company a superior is honoured, and to an outside party your own superior is spoken of humbly. Nobody expects a learner to get this right quickly.
Testing it under pressure
The final step is the one that decides whether any of the drilling worked, and it cannot be done alone: producing keigo while simultaneously handling an unpredictable conversation. Rehearsed keigo and available keigo look identical until that moment.
Roleplaying the actual situations with an AI Sensei in Unihongo's immersive 3D classroom supplies the missing condition. The customer asks something you did not script, the answer has to arrive now, and it has to arrive in the right register, which is exactly where drilled forms either hold or vanish. Typing this into a chatbot proves nothing, because there is time to assemble the form.
The session report is unusually useful for keigo, because register slips are precisely what a human listener will not mention. Plain forms appearing in a polite conversation show up there even though nobody at the counter would ever have told you.
Expect keigo to be the first thing that fails when a conversation gets difficult, for a long time. That is normal, and the margin builds with repetition rather than with more study.